Nessus
01-10-2008, 04:21 AM
Greetings.
Getting it public
By opening the ports that Ascent listens on and using a dynamic IP service like no-ip.com, I can give players a static servername that always points to my computer. I opened the ports mentioned in the Ascent .conf files and that was pretty much it. For those interested, these are the ports I opened (follow the guides on http://www.portforward.com:
80 Web server
8129 Ascent
8093 Logon server
3724 Realm list
Upgrade to Repack 7.4
When the 7.4 Repack was released, I wanted to upgrade without loosing any characters or setting. I have some experience with MySQL but needed to know what tables to keep. I found a guide that answered all my questions and now I will show you the steps I took to backup my database.
Here are the steps you will take:
Modifying the database due to changed table structure
Backup your characters from the MySQL server
Backup .conf files
Backup htdocs folder and additional databases
Install Repack 7.4
Clear the new database
Insert old data into new database
Change new .conf files
Restore your htdocs folder
Start by moving out the maps folder. Then make a copy of the Server folder.
Step 1:
By using HeidiSQL (http://www.heidisql.com), connect to your MySQL server and choose 'logon' from the databases in the left column. Double click the characters table and be sure the Table tab is selected. Find the following 4 items:
-publicNote
-officerNote
-guildid
-guildrank
Right click them one by one and choose Drop Fields. If we don't do this, we get errors when we try to import the database to the 7.4 Repack. Now all we need to do is to Export the tables.
Step 2:
What you need is the following 11 tables from the logon database:
logon
- accounts
- characters
- charters
- corpses
- guild_ranks
- guilds
- playeritems
- playerpets
- playerpetspells
- playersummonspells
- questlog
Now go to Export -> Export tables as SQL. First choose the logon database from the drop down list, then select the 11 tables mentioned above. Go to the Destination tab and from Structure choose Create if necessary in both Database and Tables. Then in Data select Insert and in Target compatability select Same as source server. Choose the folder to save the tables in Output - File and hit Export.
Keep this .sql file in a safe place as it holds your accounts and characters.
Step 3:
Next are the Ascent .conf files. I suggest you copy them to a safe place for now, because you don't want to just overwrite the new .conf files.
Step 4:
If you made changes to the Apache config file, keep it and just overwrite the new one. If you used the Joomla website and added some content, you also want to backup the htdocs folder and export the joomla database on your MySQL server. If you used the forum, export the forum database as well.
Step 5:
Now unpack the 7.4 Repack.
Step 6:
Now you need to clear the new tables before you insert the backup tables. To do this, click the logon database to the left and select the Query tab to the right. Insert this:
use logon;
delete from accounts;
delete from characters;
delete from charters;
delete from corpses;
delete from guild_ranks;
delete from guilds;
delete from playeritems;
delete from playerpets;
delete from playerpetspells;
delete from playersummonspells;
delete from questlog;
and click the blue play button. WARNING! This will delete all record from the tables mentioned. You only want to do this if you have unpacked the 7.4 Repack and are sure you are connected to the new MySQL database. To make sure, click the accounts table and go to the Data tab. It should only contain one account, admin.
Step 7:
After you have cleared the tables, you should Import the .SQL file again (As I mentioned, HeidiSQL is buggy and you might need to restart it.)
Now go to Import -> Load SQL File. Find the file we exported earlier and open. You will see it in the slim upper frame. Press the far left blue play button to run the query. If all goes well, it should display no problems.
Step 8:
Find your old Ascent .conf files and manually fill in the 7.4 config files with your old data. The config files are important and you should read them all before you start the server.
Step 9:
Overwrite the htdocs folder and joomla database if needed. If you do overwrite the new htdocs folder with your old one, you'll want to keep the 'stats' folder inside htdocs, as it may contain updates to the stats files.
If you get MySQL access denied errors when starting Ascent, you can use HeidiSQL to edit the MySQL users passwords and permissions. The user should have all permissions (Grant All Privileges.)
When the WoW 2.3.2 patch was released, the only thing I had to change was the logonserver.conf:
<Client MinBuild = "6739"
MaxBuild = "7741">
Version 7741 is of course the latest version. You only need to restart the logonserver.
Getting it public
By opening the ports that Ascent listens on and using a dynamic IP service like no-ip.com, I can give players a static servername that always points to my computer. I opened the ports mentioned in the Ascent .conf files and that was pretty much it. For those interested, these are the ports I opened (follow the guides on http://www.portforward.com:
80 Web server
8129 Ascent
8093 Logon server
3724 Realm list
Upgrade to Repack 7.4
When the 7.4 Repack was released, I wanted to upgrade without loosing any characters or setting. I have some experience with MySQL but needed to know what tables to keep. I found a guide that answered all my questions and now I will show you the steps I took to backup my database.
Here are the steps you will take:
Modifying the database due to changed table structure
Backup your characters from the MySQL server
Backup .conf files
Backup htdocs folder and additional databases
Install Repack 7.4
Clear the new database
Insert old data into new database
Change new .conf files
Restore your htdocs folder
Start by moving out the maps folder. Then make a copy of the Server folder.
Step 1:
By using HeidiSQL (http://www.heidisql.com), connect to your MySQL server and choose 'logon' from the databases in the left column. Double click the characters table and be sure the Table tab is selected. Find the following 4 items:
-publicNote
-officerNote
-guildid
-guildrank
Right click them one by one and choose Drop Fields. If we don't do this, we get errors when we try to import the database to the 7.4 Repack. Now all we need to do is to Export the tables.
Step 2:
What you need is the following 11 tables from the logon database:
logon
- accounts
- characters
- charters
- corpses
- guild_ranks
- guilds
- playeritems
- playerpets
- playerpetspells
- playersummonspells
- questlog
Now go to Export -> Export tables as SQL. First choose the logon database from the drop down list, then select the 11 tables mentioned above. Go to the Destination tab and from Structure choose Create if necessary in both Database and Tables. Then in Data select Insert and in Target compatability select Same as source server. Choose the folder to save the tables in Output - File and hit Export.
Keep this .sql file in a safe place as it holds your accounts and characters.
Step 3:
Next are the Ascent .conf files. I suggest you copy them to a safe place for now, because you don't want to just overwrite the new .conf files.
Step 4:
If you made changes to the Apache config file, keep it and just overwrite the new one. If you used the Joomla website and added some content, you also want to backup the htdocs folder and export the joomla database on your MySQL server. If you used the forum, export the forum database as well.
Step 5:
Now unpack the 7.4 Repack.
Step 6:
Now you need to clear the new tables before you insert the backup tables. To do this, click the logon database to the left and select the Query tab to the right. Insert this:
use logon;
delete from accounts;
delete from characters;
delete from charters;
delete from corpses;
delete from guild_ranks;
delete from guilds;
delete from playeritems;
delete from playerpets;
delete from playerpetspells;
delete from playersummonspells;
delete from questlog;
and click the blue play button. WARNING! This will delete all record from the tables mentioned. You only want to do this if you have unpacked the 7.4 Repack and are sure you are connected to the new MySQL database. To make sure, click the accounts table and go to the Data tab. It should only contain one account, admin.
Step 7:
After you have cleared the tables, you should Import the .SQL file again (As I mentioned, HeidiSQL is buggy and you might need to restart it.)
Now go to Import -> Load SQL File. Find the file we exported earlier and open. You will see it in the slim upper frame. Press the far left blue play button to run the query. If all goes well, it should display no problems.
Step 8:
Find your old Ascent .conf files and manually fill in the 7.4 config files with your old data. The config files are important and you should read them all before you start the server.
Step 9:
Overwrite the htdocs folder and joomla database if needed. If you do overwrite the new htdocs folder with your old one, you'll want to keep the 'stats' folder inside htdocs, as it may contain updates to the stats files.
If you get MySQL access denied errors when starting Ascent, you can use HeidiSQL to edit the MySQL users passwords and permissions. The user should have all permissions (Grant All Privileges.)
When the WoW 2.3.2 patch was released, the only thing I had to change was the logonserver.conf:
<Client MinBuild = "6739"
MaxBuild = "7741">
Version 7741 is of course the latest version. You only need to restart the logonserver.