Additional user accounts can be made via the Account Registration page or a console command. Please do not try to do this manually via the database. It will not work. Database users are maintained via the MySQL. (Edit the root user password.)
- Username: admins
- Password: admins
- Host: localhost
- Username: root
- Password: ascent
Making the repack public:
Please follow this guide if you wish to get your repack public.
It has been tested and confirmed working. So do read it.
If you are getting any 'missing .dll' errors, please download and install this fix.
Worldserver closing immediately?:
If the worldserver is closing near instantly, you can check the error in the logs folder. (Found in the core folder.) A common error is missing map, vmap, mmap or dbc files. Please ensure that your core folder is set up like this.
Issues with account permissions?:
Can't figure out the new account permissions? As of revision 9.7.7 the old account permission system got replaced with a Role based Access Control system. (RBAC) This may seem very confusing but it is much more advanced than the old system. If you'd like to learn more about RBAC you can read the wiki page here or read through MyLilSuccy's in-depth tutorial on how to use it. Once you get the hang of it, it is rather easy to use.
Can't find the MySQL.bat?:
The old way of starting the MySQL server, via the MySQL.bat file, has been ditched for a new and improved control panel. You simply start the "Jeutie's Repack Control" application provided with the repack, set the correct paths and use the buttons to start and stop all necessary services. This application will also automatically restart both world and auth servers when a crash occurs if you want it to do so. - If you cannot figure out how the application works, Redeemer has made a tutorial about it which you can find here. Additionally, Anthony made a video about the very same thing. You can find that here.
Update your previous build:
Updating from one revision to another is fairly simple. First you'll want to launch your old MySQL server, and access the databases via Navicat. Right click the 'auth' database, and click 'dump SQL'. Once finished, do the same for the 'characters' database. Proceed by shutting down the service, and launch the new MySQL server. Go into the database with HeidiSQL, right click the 'auth' database and click 'drop'. Do the same with the 'characters' database. Proceed by right clicking the connection ('root') and creating a new database named 'auth' and another named 'characters'. Right click 'auth' and click 'Load SQL', insert your old 'auth' database you've extracted. Do the same for the 'characters' database. Last but not least, you'll want to 'load' the update files from the 'Updates' folder that have the same revision number as the old one. For example, if you want to update from rev. 8.1.1 to 9.0.0, and there is a file named 'rev_8.1.1_characters_db_1.sql', you want to insert that into the 'characters' database. If you're skipping a revision, you'll still need all updates in between. (e.g: You're updating from revision 8.1.1 and there is a file called rev_9.0.0_characters_db_1.sql, you'll still need to load it.) Once finished, you should be done. Launch the server and you should still have your old characters in tact. Be sure to always use the 'Server' folder from the new repack to prevent any version mismatches. These will cause data corruption and will generally make your server unstable. Normally the server will not start up if anything went wrong.
Warning: I am not responsible if the above method would fail due to any kind of errors.
For the safety of your server I advise you to backup all necessary files and databases.
Advise: Use this useful tool by Redeemer to make backing up your databases easier.
Enable multiple realms:
Some people want to have multiple realms on their server. Enabling multiple realms is very easy. You can do it in a few steps; First of all you need to copy all the content of the repack folder into a new folder (e.g: Realm 2) Second, you'll want to delete the 'authserver.exe' ; 'authserver.config' and Server folder from the new folder. After that you'll need to open the worldserver.config in the second folder, and search '8085' and change this to '8086', search 'characters' (Regarding databases.) and change it to 'characters2', search 'world' and change it to 'world2'. Once done you can proceed by launching the MySQL.bat from the original folder. You'll want to dump the SQL from the 'characters' database and 'world' database, and make two new databases; 'characters2' and 'world2' Once done, insert the dumped SQL's into those empty databases. Last but not least you'll want to go into the 'auth' database, open the 'realmlist' table, and add a new line, You can copy all of the line above, except that the realm port will be '8086' instead of '8085'. If all went well your second realm will be ready to go. Launch the authserver.exe and worldserver.exe from the original folder, and then the worldserver.exe from the second folder. Players will now be able to choose realms upon login. Updating multiple realms with the new repack is about the same procedure as mentioned above, with the exception you'll need to update your characters databases twice. Alternatively, you can find an extended guide regarding this topic (Including screenshots.) here.
Warning: I do not give support on creating or maintaining this repack whilst using multiple realms. Please do not ask for any help regarding this, thank you.