Register observable 2V0 gameplay stubs through RunApp

This commit is contained in:
shen
2026-09-22 20:05:22 -07:00
parent b221a9eaf5
commit 9c30f06083
8 changed files with 2014 additions and 14 deletions
File diff suppressed because one or more lines are too long
@@ -24,6 +24,8 @@ bool fail(std::string* error, const std::string& text)
}
}
void init_2v0_gameplay_stubs();
namespace PythonBoot
{
@@ -77,6 +79,7 @@ bool RunMainScript(const char* lpCmdLine, std::string* error)
initgrpText();
initwndMgr();
initapp();
init_2v0_gameplay_stubs();
ClearLogBoxMessage();
@@ -26,8 +26,8 @@ bool Start(const char* stdlib_path, std::string* error);
bool IsRunning();
// 40250: RunMainScript(CPythonLauncher&, const char*) — the module initializers, __DEBUG__,
// __COMMAND_LINE__ and RunFile("system.py"). Only the initializers that are ported are called; the rest
// arrive with the 2V slices, which is why system.py still stops at its first import.
// __COMMAND_LINE__ and RunFile("system.py"). 2V0-e registers temporary observable gameplay modules;
// they are replaced by the real modules in later 2V slices.
// False leaves *error set to what the launcher reported through LogBox (platform/EterBase/LogBox.h).
bool RunMainScript(const char* lpCmdLine, std::string* error);