-
Notifications
You must be signed in to change notification settings - Fork 36
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
[BUG]LogObjectNotFound not implemented correctly #184
Comments
Known issue, unfortunately. I am still to find a way to implement it properly. I'll try and look into it this month |
Thanks for looking into it. As Is said above...if you define a class called AdvancedOptions it works here. |
I have done half the Job... i think 😅 now test, then just to make the output work again 😭 |
Are there news On this @jupster ? Dont want to stress...just asking. With the Mission Overwrite like in the Screenshot it works. So it should be doable. |
Sorry disappeared for a little as life got pretty crazy. I have implemented it but the output is a little annoying as it doesn't update and save probably. I'll see if I can't put a test build on my repo in the next day or two |
@
Great...thanks for the respond. I hope you will get it working....Keep up the good work but remember real life is more important. ;-) |
@Holgerhollebolle Don't blame me if something breaks https://github.com/jupster/FASTER1.9/releases/tag/1.9e.4 back up your files just in-case, if you want to test it. But let me know how it goes if you do. |
Describe the bug
I was happy to see you implemented the LogObjectNotFound option in Faster.
Unfortunatly it does not work. You need to implement it as a class called AdvancedOptions. In the Server.cfg needs to be:
To Reproduce
You can reproduce it by running any mission on a server and check the log. There should be no Object not found messeges...but there still are these messages.
Screenshots
This is how it does work when you enter the code in the Mission selecto overwrite
OS Version (required):
The text was updated successfully, but these errors were encountered: