Skip to content
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

automatically apply certain flags based on metadata in the map #44

Open
zzlk opened this issue Feb 10, 2025 · 1 comment
Open

automatically apply certain flags based on metadata in the map #44

zzlk opened this issue Feb 10, 2025 · 1 comment
Labels

Comments

@zzlk
Copy link
Contributor

zzlk commented Feb 10, 2025

see #42 for previous discussion

what is the best way to do this?

@zzlk zzlk added the idea label Feb 10, 2025
@zzlk
Copy link
Contributor Author

zzlk commented Feb 10, 2025

Comment actions in input map are removed in output map:
an existed way used in CTrigAsm is putting magic numbers in triggers, and walking over triggers to find it
euddraft output map only includes chk sections used in game:
it removes other sections not required in-game

Seems like currently the best way is to either put in one of the unused force names or never-to-be-executed triggers

euddraft doesn't detect nor specially treat unused/unreferenced strings (it would require global analysis or be impossible to know whether the string is referenced and modified in runtime)
euddraft trims unused TRIG condition/action and migrates TRIG triggers to STRx triggers to reduce map size (can be turned off with PRT_SetInliningRate(0);)

you could use invisible character to hide it, and also mission objectives is an option
color codes are ignored in the description

Could just throw a string into the strings section that isn’t referenced by anything. Can still be found by any 3rd party tool but don’t have to worry about it being displayed or anything

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant