-
-
Notifications
You must be signed in to change notification settings - Fork 423
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
[Feature Request] A method to catch entity lump parse failures #2198
Comments
What parsing failures have you run into that would have been recoverable? |
Without SM, some maps sometimes crash on map start with With SM, instead of crash on map start receive log Entity lump does write the changes but does not appear in the map. |
The entity lump is packed into the map file, so the general assumption is that a failure in parsing would only come from a malformed map file (which would not be a sometimes-issue that is fixed on a reload). In your case, you could probably check that
|
Sorry, meant error code 1. But I will try |
Position -1 would be end-of-file, so either the whole string was consumed (unlikely if you're hitting the parse failure) or the string was empty. Empty string would mean |
Unfortunately didn't work for my case. The map is tr_walkway. Stripper extension can make changes without issue. I am thinking maybe adding the success bool to OnMapInit. |
I have this error happen on only 1 map, at random (presumably after server has been running for some time).
Console
Stack
|
sourcemod/core/sourcemod.cpp
Lines 425 to 434 in 96727a7
Plugins like the SourcePawn plugin for Stripper will not be able to make changes if entity lump parsing fails. If there is a method to catch fails developers can find another work around such as reloading the map.
The text was updated successfully, but these errors were encountered: