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

Flags: Do not hardcode one Flag field per class #492

Draft
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

Ghabry
Copy link
Member

@Ghabry Ghabry commented Feb 12, 2025

This is an alternative approach for #491

Instead of a single variable it uses our Flag feature to provide bool variables. This reduces the need for bitmasking.

Problem was that our code always hardcoded StructName_Flags for Flags. This restriction is now lifted and multiple Structs can have the same flags and a struct can have multiple flags.

Don't merge, Player build failure because classes are renamed

Ghabry and others added 10 commits February 12, 2025 12:41
This was hardcoded to one Flag per struct.
The generator is now smarter and you can specify multiple flags which are resolved by their flag name.
…ify which enum names are considered to be "scoped" ('class' enums in C++)
… determine if an event has been created by EasyRPGs new "CloneMapEvent" command
…preter related SaveState structures (SaveEventExecState, SaveEventExecFrame & SaveMapEventBase)
@Ghabry Ghabry added this to the 0.8.1 milestone Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants