-
-
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
Trigger error messages should be improved #340
Comments
This debug message is completely unnecessary for the client anyway. It gets also triggered when the server tries to trigger a client side event when the client has not even started its resources, it is not even harmful. I would like to get rid of it entirely without creating hackfixes in Lua for it. |
The debug messages are useful indeed. Crosroad suggested that setDevelopmentMode could be used to enable more specific error messages that might be a bit heavy for events. Do you think this is worth investigating? |
Yes, I could try that. |
Is your feature request related to a problem? Please describe.
error that appear while event isn't added should contain source from where was triggered. Now i see only that random event was triggered, nothing else. If server have a lot of events, search can take forever.
Describe the solution you'd like
Add information about source of error ( resource, file, line ).
Describe alternatives you've considered
add event
onEvent
which first argument is event name and rest of arguments are from trigger.Additional context
mtasa-blue/Server/mods/deathmatch/logic/CGame.cpp
Line 2437 in 0cffa92
The text was updated successfully, but these errors were encountered: