Where I would like to see EQ2Emu go
Posted: Sat Feb 24, 2018 7:32 am
i have been developing(what i can) and some content design for a little over a year, and enjoy it a lot, I like the fact that admins can customize to there liking, but most admins will want to just install and have people play on there server. we have a server pack for that
i am not sure what the goals of the server should be but what i would like to see is
1. all or most customization that are large scale be added to the server and have a rule the enables that server type for the 3 main types
a. regular server EQ2emu--- would get content updates from updater like now. DB would be the master for new servers, but include structure for other server types
b. PVP server(peak) have a rule that enables PvP, and specific PVP content etc would be manually download form SVN and imported to the db( remember main db structure should be the same for all server type although all db data may not be applicable.
c Classic (ememjr) same thing have a rule and have classic content availalbe to be imported into current db, that includes zones ha are classic only, quests and scripts that are classic only.
But the EQ2emu server would support all this as long as the code is commited and a rule invoked if something is classic or pvp specific, an example of that is if the rule says classic server then the code whoul zone you into the starter boat as a commoner instead of the class you choose, and off the bout you go to isle of refuge that has specific content for a classic server
what i do not think should have to be done is if 3 admin decide to make a classic server that, they should have to learn C++ and code the changes themselves and have to write there own quests, and scripts etc
thoughts any one
i already put most of my changes to code in commit or on Forums for others so not really extra work for me except creating those rules
i am not sure what the goals of the server should be but what i would like to see is
1. all or most customization that are large scale be added to the server and have a rule the enables that server type for the 3 main types
a. regular server EQ2emu--- would get content updates from updater like now. DB would be the master for new servers, but include structure for other server types
b. PVP server(peak) have a rule that enables PvP, and specific PVP content etc would be manually download form SVN and imported to the db( remember main db structure should be the same for all server type although all db data may not be applicable.
c Classic (ememjr) same thing have a rule and have classic content availalbe to be imported into current db, that includes zones ha are classic only, quests and scripts that are classic only.
But the EQ2emu server would support all this as long as the code is commited and a rule invoked if something is classic or pvp specific, an example of that is if the rule says classic server then the code whoul zone you into the starter boat as a commoner instead of the class you choose, and off the bout you go to isle of refuge that has specific content for a classic server
what i do not think should have to be done is if 3 admin decide to make a classic server that, they should have to learn C++ and code the changes themselves and have to write there own quests, and scripts etc
thoughts any one
i already put most of my changes to code in commit or on Forums for others so not really extra work for me except creating those rules