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

For Review: First pass at weenies as code objects. #335

Closed

Conversation

LtRipley36706
Copy link
Member

This is a sample of how I see setting up weenies in ACE.

It still pulls a lot of the data from the DB which in some of the cases I would think would actually by coded in the object itself and not in the DB.

Copy link
Contributor

@ogmage78 ogmage78 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this looks really clean. I still have a major concern if we use this pattern we are closing the door on having any type of future world builder. Unless I am missing something - nothing or very little new can be introduced without coding. I think while this might give us a very clean and maintainable project - it will be very slow to implement. There are over 29k unique weenie classes that would need to be implemented. I would love this approach if we could do it it larger groups - maybe item type is too narrow - but weenie class is way way too broad I think. If you can explain how this will not cripple a database driven world builder for future content creators - I am all in.

@LtRipley36706 LtRipley36706 deleted the dev-WeenieWork-v2 branch June 17, 2017 04:04
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

Successfully merging this pull request may close these issues.

None yet

2 participants