Original behavior in Fred was accidentally removed when upgrading the FSO mission parser to keep it from crashing FSO from a bad sexp.  But returning false is only necessary in FSO since in FRED, we can fix the error once we know about it.
This commit is contained in:
FSCyborg committed 2019-07-27 21:21:33 -04:00
1 parent 6df9c73a4c
commit 0e10100aad
1 file changed
+4 -2
+4 -2
View File
@@ -5852,8 +5852,10 @@ bool post_process_mission()
sprintf(error_msg, "%s.\n\nIn sexpression: %s\n(Error appears to be: %s)", sexp_error_message(result), sexp_str.c_str(), Sexp_nodes[bad_node].text);
Warning(LOCATION, "%s", error_msg.c_str());
// syntax errors are unrecoverable, so abort
return false;
// syntax errors are recoverable in Fred but not FS
if (!Fred_running) {
return false;
}
}
}
}