-
Notifications
You must be signed in to change notification settings - Fork 7
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
Standardized warning messages of terminate_this_script and terminate_… #174
Changes from all commits
5fc6864
da7f94c
dc22fcb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -863,11 +863,11 @@ namespace CLEO | |
CCustomScript *cs = reinterpret_cast<CCustomScript *>(thread); | ||
if (thread->IsMission() || !cs->IsCustom()) | ||
{ | ||
LOG_WARNING(0, "Incorrect usage of opcode [0A93] in script %s", ((CCustomScript*)thread)->GetInfoStr().c_str()); | ||
|
||
return OR_CONTINUE; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would keep it as is. Nobody asked for this change There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are we going to fix bugs only if somebody else spot and report them? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 0a93 never worked in custom missions and nobody used it here. Its been like this from day 1. No need to change the behavior There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok, added old behavior back. |
||
LOG_WARNING(0, "Incorrect usage of opcode [0A93] in script %s. Use [004E] instead.", ((CCustomScript*)thread)->GetInfoStr().c_str()); | ||
return OR_CONTINUE; // legacy behavior | ||
} | ||
GetInstance().ScriptEngine.RemoveCustomScript(cs); | ||
|
||
GetInstance().ScriptEngine.RemoveScript(thread); | ||
return OR_INTERRUPT; | ||
} | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why custom missions are forced to use 004E?