i was thinking of getting a team together to revive wowemu. i used it long ago. it is a very easy server to run. thereby making it ideal for people that are running their first server.
i was thinking of getting a team together to revive wowemu. i used it long ago. it is a very easy server to run. thereby making it ideal for people that are running their first server.
I used to use WoWEmu. It sucked. It was extremely unstable, buggy and incomplete.
There are many much better vanilla emulators out there than WoWEmu. When was the last time WoWEmu was even updated? 2004?
It's not that much different from how today's servers run, it just doesn't use an SQL database. Really the only difference is you don't need to compile it yourself and you don't need to set up an SQL database. Both of which are very easy to do.
Last edited by Darkicon; 12-01-11 at 11:27 AM.
wowemu sure had its flaws but, it was easy to use. it didnt require much setup, unlike the modern emulators. it have potential. though my intention is to make it compatible with cataclysm.
I doubt you could. You don't even know how to compile a core...
my plan was to get a team together to work on wowemu. if you dont want to be a part of it please leave the topic alone.
So basically what you want is to get a bunch of people together to make you an easy-to-use server that supports Cataclysm, of which you will not help whatsoever?
Yeah, good luck with that.
i will do what i can but, there isnt much i can do on the server itself. i can test it though. testing is important to find bugs.
Essentially you are asking for people to update/fix an old buggy emulator because it's "easy to use".
ie. Since you can't use any emulators that requires the smallest bit of effort on your part going by all your other posts.
Crash
i can use emulators that require me to use an sql database. the problem is that it is a lot of trouble to keep updated. therefore i want something easier. wowemu is easy. wowwow is also easy.
It's not hard to keep the databases updated. Most databases don't get updated very often and when they do, it's as simple as executing the full DB dump overtop of the old or just executing the few updates.
They even make getting the databases quick and easy with subversion repositories and/or GIT repositories.
every core comes with a lot of updates. finding the right update takes time. then lots of small updates have to be installed. that is a lot of trouble just to keep the database updated. though that is the developer`s fault for changing so much all the time. i want a project where the database structure isnt changing.
OK. . . 1. Finding the right update does NOT take a lot of time, especially if you're using Trinity Core. 2. It only takes a LOT OF TIME if you don't occasionally update. 3. So it's the developer's fault for improving the core, fixing bugs, and the like? 4. You want a project where the database structure isn't changing. . . ok umm so you want a completely out-dated core? I see. . .
/fail & /wrist -.-
i believe that the core can be updated without changing the database structure. that is what i want. a core that is updated without changing the database structure. if you dont want to help me please leave the topic alone.
Umm, there's no such thing. Granted you can, try, and get away with leaving the db the way it is, however eventually after you update your core, you're going to have to update your database. And I'm trying to help you, but you just never seem to follow anyone's help.
P.S. now you're being rude.
Last edited by Noaru; 13-01-11 at 01:54 AM.