New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Original configs are not supported without modifications #2
Comments
This is an error from the SMCParser, there is no easy way for me to fix this as sections are required to have a header when parsing a file using one. I would argue that its not great that the original stripper allows this as it can be ambiguous what the block is doing if you aren't aware that it defaults to filter and carries the previous mode over to the next block if undefined, which can make the config harder to read. I understand its not ideal that its not fully backwards compatible, but for 99% of configs this shouldn't be a problem and it can be easily fixed. I'm not going to fix this in the plugin, you can make the blocks without headers Using your example, the fixed version would be:
|
SMCParser requires section headers when parsing a config, see tilgep/stripper#2 for more info.
SMCParser requires section headers when parsing a config, see tilgep/stripper#2 for more info.
[stripper.smx] Section declared without header on line 109, col 1 of addons/sourcemod/configs/stripper/global_filters.cfg
taken from https://www.bailopan.net/stripper/
filter:
{
"prop1" "val1"
}
{
"prop3" "val3"
}
The text was updated successfully, but these errors were encountered: