Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm experimenting ways to get around the fact that you can access
bpy.context
(which I need to get the game editor mode for MM), here's what this branch does:fast64_internal/oot/data
tofast64_internal/data
so other games can take advantage of thatTo do this I had to use the annotation trick we used before for the detailed actor panel as some enums are requiring
game_data
, and there's some issues with leaving them in the class, so far I only had to do this foractor_id
but on the other hand I didn't removeootData
yet so maybe there's moreAdvantages:
Drawbacks:
game_data
when registering props underscene.fast64.oot
andobject.fast64.oot
as this needs to be registered with the addonalso I deleted
fast64_internal/__init__.py
because this file is completely useless and caused issues with thisstill experimenting so draft for now but feel free if there's any suggestions