Junior Spellweaver
- Joined
- Feb 6, 2013
- Messages
- 196
- Reaction score
- 25
Hi,
Something I've been thinking about is the database structure for new emulators.
This might be a thread that people will hate as it might sound like I want you to spoon feed the community.
New emulators want their database structure to be so "unique" or whatever, it's understandable but I think you should look to make it more adaptable to releases out there. Let me explain.
E.g Arcturus (I like that emulator don't get me wrong). However, they have catalog_items, catalog_pages and items_base? why not furniture? Like 90% of all furniture releases out there is using the table "furniture" and not items_base, yes it is easy to change by yourself, but for all the newbies, they want things to be easily made. It's ofcourse good for them to learn how to change queries and whatever, but it is quite annoying change the queries every single time. I guess you could use a furni adder of some sort to make the queries adaptable to the furniture but still.
And Comet, why Ducking "players" instead of "users"? (I also like Comet dw). It's just so annoying to have to change queries all the time when chaning CMS, adding cms addons or whatever. Maybe stick to what the community has already built?
I know that there is updates that forces columns and poop to be added, but you get my point.
Yes it is a big problem that people want to get spoonfed in this community, but the easier it is to make, adjust and add features to your retro the more people will be making retros, and the community might grow, who knows?
What's your thoughts about this, do you think I am just lazy or is it actually a good idea to stick to what's already built by the community?
Something I've been thinking about is the database structure for new emulators.
This might be a thread that people will hate as it might sound like I want you to spoon feed the community.
New emulators want their database structure to be so "unique" or whatever, it's understandable but I think you should look to make it more adaptable to releases out there. Let me explain.
E.g Arcturus (I like that emulator don't get me wrong). However, they have catalog_items, catalog_pages and items_base? why not furniture? Like 90% of all furniture releases out there is using the table "furniture" and not items_base, yes it is easy to change by yourself, but for all the newbies, they want things to be easily made. It's ofcourse good for them to learn how to change queries and whatever, but it is quite annoying change the queries every single time. I guess you could use a furni adder of some sort to make the queries adaptable to the furniture but still.
And Comet, why Ducking "players" instead of "users"? (I also like Comet dw). It's just so annoying to have to change queries all the time when chaning CMS, adding cms addons or whatever. Maybe stick to what the community has already built?
I know that there is updates that forces columns and poop to be added, but you get my point.
Yes it is a big problem that people want to get spoonfed in this community, but the easier it is to make, adjust and add features to your retro the more people will be making retros, and the community might grow, who knows?
What's your thoughts about this, do you think I am just lazy or is it actually a good idea to stick to what's already built by the community?
Last edited: