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

Could I treat Worlds as entities to encapsulate functionality? #31

Open
chexo3 opened this issue Feb 4, 2025 · 0 comments
Open

Could I treat Worlds as entities to encapsulate functionality? #31

chexo3 opened this issue Feb 4, 2025 · 0 comments

Comments

@chexo3
Copy link

chexo3 commented Feb 4, 2025

Hello! I’m looking to use this library to implement a virtual card game table in Minecraft in Computercraft, which runs Lua 5.1 with many backported features from later versions.

I’m wondering if it makes sense to treat a World as an entity so that I can encapsulate all the functionality of a specific feature in that one world and only run it’s systems when it’s relevant?

Like, say I have a computer acting as a server managing multiple tables. Would it be reasonable to have a setup where the game manager portion of the server starts up a “table” entity with a FSM, then lets it run independently with it’s own World managing all it’s logic until it ends up in a “finished” state?

Does that even make sense? Am I overcomplicating things?

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

No branches or pull requests

1 participant