Generate script source data in scenario when decompiling scripts. #26
Comments
MosesofEgypt
added a commit
that referenced
this issue
Jan 19, 2025
Issues closed: #36 #31 #28 #27 #26 #11 Fixes: exception thrown when extracting stubbs models Additions: setting to control using open-sauce definitions for regular CE maps setting to control showing tag ids/metadata offsets in base 16 or 10 sound playback in tag window(requires pyogg and simpleaudio) Changes: reduced stacktrace when tag extraction fails better descriptions of what disabling safe-mode settings will do Heuristic deprotection changes: significant speed increase(most maps deprotect in 15 seconds or less) renaming logic improved to select better names added ability to configure a root directory to put all renamed tags in added ability to prioritize model names over weapon/vehicle strings underscore appended to shader names to allow permutations to be used spaces in tag names replaced with underscores in most cases
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Explanation I've gotten:
"You should have refinery decompile scripts and save it into the script source data block when extracting a scenario tag. Scenario tags without source data are undefined and can break when built with tool.exe again. For example reference a child scenario and compile it again, the scripts will now be gone because tool will try to recompile the scripts and see that there are no scripts because there is no source data."
The text was updated successfully, but these errors were encountered: