Jump to content

kuya1284

Members
  • Posts

    7
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

kuya1284's Achievements

Newbie

Newbie (1/3)

0

Reputation

  1. Try sudo apt-get install libcurl4-openssl-dev see if that does it for you...
  2. OK... I just got done doing a bit of research (had a bit of time to spare)... and basically, you're correct in regards to the characters and realmd scripts. I was really curious by various updates being performed in the 380, 381, and 382 character updates. I believe some of the updates being performed dealt with data formatting. In addition, I noticed modifications to a couple tables in regards to spells. 1. Spell/Action 64904 was changed to 64901 in table character_action. This can be explained from the following links (Read comments in first link): http://www.wowhead.com/?spell=64904 http://www.wowhead.com/?spell=64901 2. Spell 28734 was removed from the character_spell table, which was Mana Tap since it was removed as of 3.0.2: http://www.wowhead.com/?spell=28734#comments I'm really intrigued to see the correlation between the spell id's (all action, item, spell, etc for that matter) with the id's found on wowhead. I'm really curious where that information is stored. I wonder if it's stored in game, or if the Mangos or UDB team colaborated with Blizz/Wow. I'm really interested in know where the information comes from. Anyway, I modified my instructions to prevent confusion in case someone reads it. Thanks for helping me out Yip.
  3. Oh I see what you're saying. So the only 380, 381, and 382 updates that were necessary were the ones for mangos and the updatepack, correct? I didn't realize that the Mangos team incorporated the UDB character and realm info into their core. Is that a safe assumption? Thanks for clarifying, Yip. EDIT 1: OK... I went ahead and verified that the changes were incorporated. The only discrepancy that I found dealt with the character_spell table and some other table. Updates were made to a couple records that didn't even exist. So I'm not sure if that data was supposed to come from somewhere, or if the data is no longer needed. I'll look into this further when I get some free time.
  4. Yip, I just tested it out. Using the characters.sql that comes with Mangos core 8444 will cause 380_corepatch_characters_7682_to_7894.sql to fail right off the bat. I get the following error, due to core updates: ERROR 1054 (42S22) at line 2: Unknown column 'required_7644_01_characters_character_pet' in 'character_db_version' The same goes for realmd: ERROR 1054 (42S22) at line 2: Unknown column 'required_7546_02_realmd_uptime' in 'realmd_db_version' Thus, I can't proceed to importing 381 and 382. So it is necessary to import the characters.sql and realmd.sql files from the UDB ForCleanInstallOnly trunk. You can test this out by creating a new database (i.e. characters2) and importing 380_corepatch_characters_XXX.sql as follows: CREATE DATABASE `characters2` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci; CREATE DATABASE `realmd2` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci; GRANT ALL PRIVILEGES ON `characters2` . * TO 'mangos'@'localhost' WITH GRANT OPTION; GRANT ALL PRIVILEGES ON `realmd2` . * TO 'mangos'@'localhost' WITH GRANT OPTION; mysql -u mangos -p'password' characters2 < XXX.sql mysql -u mangos -p'password' realmd2 < XXX.sql Also, before doing this, you may want to backup your DB so you don't accidentally override something by mistyping... mysqldump -u root -p characters > 20090903_characters.dmp mysqldump -u root -p realmd > 20090903_realmd.dmp Your version probably will work for mangos/sql/characters.sql if your (original) core version is 7644 or older and/or for mangos/sql/realmd.sql if your (original) core version is 7546 or older.
  5. The only reason why I had to perform step 4 was because I was having trouble running the UDB 381 core patch for the characters DB. So I was forced to take it back by using the UDB clean install dump. So rather than figure out what was gonna break in 381 and 382 in terms of characters and realmd, I decided to just import everything in the clean install directory. Otherwise, I would have done exactly what you did.
  6. Thanks Yip... yeah... before even reading post 99, I did the same exact process you did. I started getting a better understanding of how everything marries up after reading this thread on the UDB forum: http://udbforums.org/index.php?topic=12622.0 I imported the data in a slightly different order, but ultimately, it should be exactly the same as yours (depending on which revision of Mangos you're using, of course) Anyway, I believe I got everything up to 8444 now. If anyone is having problems with a clean install, do exactly what Yip said. DO NOT import mangos.sql. Here is exactly what I did from a clean install (nothing in MySQL yet). Sorry Yip, but I have to reiterate since I didn't import characters.sql and realmd.sql from mangos/sql, but rather from the UDB (ForCleanInstallOnly) trunk. SETTING UP MANGOS from UDB_0.11.5_Core_7681_SD2_1012 to Mangos 8444 w/ ScriptDev2 1275, ACID 3.0.0, and UDB 382: All of this is assuming that you have successfully compiled Mangos with ScriptDev2 1. Download the prerequisite files: # First create directories in Mangos data dir (Note I didn't install in the default /opt/mangos, so change paths accordingly) cd /etc/mangos mkdir acid mkdir acid/sql mkdir udb mkdir udb/sql mkdir udb/sql/updates # Download via wget (I could have downloaded the tar ball, but it wasn't coming in correctly) cd acid/sql wget [url]http://sd2-acid.svn.sourceforge.net/viewvc/sd2-acid/trunk/wotlk/3.0.0/3.0.0_acid.sql[/url] cd /etc/mangos/udb/sql wget [url]http://unifieddb.svn.sourceforge.net/viewvc/unifieddb/trunk/Full_DB/UDB_0.11.5_Core_7681_SD2_1012.rar[/url] unrar e UDB_0.11.5_Core_7681_SD2_1012.rar rm UDB_0.11.5_Core_7681_SD2_1012.rar cd ../updates wget [url]http://unifieddb.svn.sourceforge.net/viewvc/unifieddb/trunk/Updates/0.11.5_additions/380_corepatch_mangos_7682_to_7894.sql[/url] wget [url]http://unifieddb.svn.sourceforge.net/viewvc/unifieddb/trunk/Updates/0.11.5_additions/380_updatepack_mangos.sql[/url] wget [url]http://unifieddb.svn.sourceforge.net/viewvc/unifieddb/trunk/Updates/0.11.5_additions/381_corepatch_mangos_7895_to_8029.sql[/url] wget [url]http://unifieddb.svn.sourceforge.net/viewvc/unifieddb/trunk/Updates/0.11.5_additions/381_updatepack_mangos.sql[/url] wget [url]http://unifieddb.svn.sourceforge.net/viewvc/unifieddb/trunk/Updates/0.11.5_additions/382_corepatch_mangos_8030_to_8280.sql[/url] wget [url]http://unifieddb.svn.sourceforge.net/viewvc/unifieddb/trunk/Updates/0.11.5_additions/382_updatepack_mangos.sql[/url] 2. Create the database structure cd /etc/mangos/mangos/sql mysql -u root -p'<password>' < create_mysql.sql 3. Populate the database cd /etc/mangos/udb/sql mysql -u root -p'<password>' mangos < UDB_0.11.5_Core_7681_SD2_1012.sql cd /etc/mangos/udb/sql/updates mysql -u root -p'<password>' mangos < 380_corepatch_mangos_7682_to_7894.sql mysql -u root -p'<password>' mangos < 380_updatepack_mangos.sql mysql -u root -p'<password>' mangos < 381_corepatch_mangos_7895_to_8029.sql mysql -u root -p'<password>' mangos < 381_updatepack_mangos.sql mysql -u root -p'<password>' mangos < 382_corepatch_mangos_8030_to_8280.sql mysql -u root -p'<password>' mangos < 382_updatepack_mangos.sql 4. Perform Mangos update # The latest UDB release was for Mangos 8280. So we need to patch from 8294 to current (as of this post, 8444) cd /etc/mangos/mangos/sql/updates mysql -u root -p'<password>' mangos < 8294_01_mangos_playercreateinfo_action.sql mysql -u root -p'<password>' mangos < 8310_01_mangos_spell_proc_event.sql mysql -u root -p'<password>' mangos < 8342_01_mangos_spell_proc_event.sql mysql -u root -p'<password>' mangos < 8361_01_mangos_spell_bonus_data.sql mysql -u root -p'<password>' mangos < 8364_01_mangos_db_version.sql mysql -u root -p'<password>' mangos < 8377_01_mangos_spell_area.sql mysql -u root -p'<password>' mangos < 8392_01_mangos_spell_proc_event.sql mysql -u root -p'<password>' mangos < 8392_02_mangos_spell_chain.sql mysql -u root -p'<password>' mangos < 8394_01_mangos_spell_proc_event.sql mysql -u root -p'<password>' mangos < 8397_01_mangos_spell_chain.sql mysql -u root -p'<password>' mangos < 8397_02_mangos_spell_threat.sql mysql -u root -p'<password>' mangos < 8399_01_mangos_spell_elixir.sql mysql -u root -p'<password>' mangos < 8412_01_mangos_mangos_string.sql mysql -u root -p'<password>' mangos < 8416_01_mangos_spell_learn_spell.sql mysql -u root -p'<password>' mangos < 8444_01_mangos_mangos_string.sql 5. Finalize database population cd /etc/mangos/mangos/sql mysql -u root -p'<password>' characters < characters.sql mysql -u root -p'<password>' realmd < realmd.sql cd /etc/mangos/acid/sql mysql -u root -p'<password>' mangos < 3.0.0_acid.sql cd /etc/mangos/scriptdev2/sql mysql -u root -p'<password>' < scriptdev2_create_database.sql mysql -u root -p'<password>' scriptdev2 < scriptdev2_create_structure_mysql.sql mysql -u root -p'<password>' scriptdev2 < scriptdev2_script_full.sql mysql -u root -p'<password>' mangos < mangos_scriptname_full.sql 6. Update Realmlist table # This is needed otherwise you won't be able to login mysql -u root -p'mysql -u root -p'<password>' # Enter the following once logged into MySQL use realmd; UPDATE realmlist SET name='<Realm Name>', address='<Server IP Address>' WHERE id=1; # I used a static internal LAN IP assigned to Xubuntu 7. Launch the the Realm and World # Open 2 terminals # First terminal type (NOTE: Remember, your data dir may be different, such as /opt/mangos/bin) /etc/mangos/bin/mangos-realmd # Second terminal /etc/mangos/bin/mangos-worldd 8. Create an account # If everything launches without errors, you're good to go. In the 2nd term window, type: <Enter> account create <username> <password> account set addon <username> 2 # 0 = Classic, 1 = TBC, 2 = WotLK And that's it folks. Don't forget to set the account addon, otherwise you'll be limited to WoW Classic features only. Good luck! EDIT 1: Removed unnecessary steps per advice provided by yip328.
  7. I just wanted to know that I'm using Xubuntu 9.04 and I don't know if this will apply to a vanilla install of Ubuntu 9.x, but I was also receiving OPENSSL errors when running "configure". I discovered that I had to install libcurl4-openssl-dev with apt-get. Everything worked fine for me after that point; with the exception to the outdated URLs to the SVN, which I easily fixed on my own (I just now started reading this thread). Now my problem is UDB related. I'm not even going to bother asking how to resolve the problem because I know where the problem lies. After updating my database using the 380 core patches, I got to the 380 update pack and received the following error: I opened up the sql script to find that the table being affected is called npc_spellclick_spell, which starting with Mangos 8016, the table was updated with new fields (quest_id was removed). (NOTE: See 8016_01_mangos_npc_spellclick_spells.sql in mangos/sql/updates dir). So I guess I either need to start with an older version of mangos before updating using UDB, then repatch all the way up to the current version of Mangos (8444), or I'll need to ask on the UDB forums if it's even necessary for me to start patching from 380 and if I can just start with 381... I'll keep yall posted on my progress or if I run into any other snags...
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use