Search the Community

Hey guys, I had to implement my mangos-one to my new Ubuntu 14.04-machine. Last thing to do is to convert my existing databases to the new versions. I realized I was running a pretty old version: Characters: s1699_xxxxx_01_characters_characters Realmd: s1706_xxxxx_01_warden_data_result The required Versions are: Characters: 20001_02_dbdocs-Update Realmd: 20150409_Playerbot_and_Warden The Update-folders on the github-content AND the archived server here on getmangos don't reach enough back to help me. They only go back to: Characters: 19000_Release_019_Initial Realmd: z2424_sxxxx_xxxxx_01_realm_db_version Can anyone tell me where I can find older updates? Or can you just copy the files content here?? That would be great! Thanks in advance!

Experienced by building the 32-bit project on Win7 x64 with Cmake 3.4.3, mysql 5.1.55 (community server), openssl 1.0.1g, MS VS 2013 12.0.31101.00 Upd4. The whole setup went as usual. I did not use EasyBuild and did not drop my old realmd DB. Then I decided to check DB versions. The world DB has strange enough records: 21,1,0,'revision_refactor','' 21,1,11,'Fix last startup errors','server - fix last startup errors' Well, I wasn't interested in the fate of 21-1-{1..10} updates concentrating on the possibility to start the server, since the revision.h file required 21-2-3. Applying the updates manually with SQLyog one-by-one, I got no further than 21-1-21. For a reason unknown to me, the SQL client fails to apply long updates through "Execute SQL file..." interface option, while the same update copypasted into the client command window runs fine. Note the similar behaviour of Navicat too. When an update is applied through the interface command, there is no diagnostic output at all. From the command window, I see only `description` output value which is useless (see for example a lot of recent dbdocs updates with - wow! - the same description field). I say constantly that the transactional updates are evil... Checking the two other DB versions, I got an issue with older realm DB about dbdocs table structure. It will not be encountered at a full fresh install. I doubt that a user can solve this DB mess on his own. Anyway, I have the following propositions: The full update history must be kept in the db_version tables since the latest major release. In our case it would be 21-1-0 to 21-1-11. Rethink what the scheme is better for a user: either to apply all DB updates from the Updates/Relxx/ folder, or to find the missing ones by unsuccesfully starting mangosd. Note that he also can miss some minor (content) updates in the latter case. Keep an eye on other projects (One, Two) when updating realmd submodule and especially realmd DB. It is a waste work, but the whole repo structure implies necessity of it. It is barely needed to change the `db_version`.`structure` field for dbdoc structrure updates since the tables are not used by the core. The users are not interested in these tables, but they are interested in the starting server. The hosting service must support the "Downloads" section for any project. Since github does not, it will be excellent to have the binaries required by EasyBuild (btw why do not use network install?) as well as EasyBuild itself as a submodule. This will greatly reduce the core repo size, and the most of devs are not meant to change anything under win/ folder. (Also I will be happy to drop that submodule locally ). (Optional) Remember me why we are keeping transactional DB updates after finished transition to the new (Foe's) update numbering system. Also think about reapplicability of introduced SQL updates. No need to repeat that the admins have to enforce the accepted policies checking the PRs before merges. Despite that would mean rejecting 50 to 80% of the commits (well, may be this statistics was improved a bit lately).

Hello, I'm a .NET developer at a software company and would like to contribute in the long run. It's been a long while since I wrote anything in c++ but we'll see how it goes. I just started last night with downloading all the required files by using two guides. I started with the first one but finished with the other. I had several issues: mangosd.conf not anywhere to be found realmd.conf not anywhere to be found server/bin does not exist like mentioned in the guide InstallDatabases.bat did not create all tables it should have for me It's my hope the guide could be a little outdated, either that or I suck pretty bad. No biggie, I got it running after a couple of hours searching. Right now I'm trying to see how everything works together. And I have stumbled upon some questions. I'm assuming not every creature has scripts, but where are they? So far the only thing I've been able to change in the database and that actually changed inside the game is the creature_template.maxlevel. I'm assuming the base AI just casts creature_template.spell1 over and over until out of mana. I tried changing that but the creature does not cast the other spell. It's like the change wasn't there. I tried changing the modelid1 to see if the in-game model would change but it didn't. I changed the subname to see if it would pop up somewhere, nothing. I restarted realmd and mangosd inbetween changes. SELECT * FROM creature_template_spells WHERE entry = 2953; UPDATE creature_template_spells SET spell1 = 116, spell2 = 0 WHERE entry = 2953; UPDATE creature_template_spells SET spell1 = 9532, spell2 = 0 WHERE entry = 2953; SELECT * FROM creature_template WHERE entry = 2953; UPDATE creature_template SET maxlevel = 10 WHERE entry = 2953; UPDATE creature_template SET maxlevel = 4 WHERE entry = 2953; UPDATE creature_template SET modelid1 = 15115 WHERE entry = 2953; UPDATE creature_template SET modelid1 = 6090 WHERE entry = 2953; UPDATE creature_template SET subname = 'Bristlurbucks' WHERE entry = 2953; UPDATE creature_template SET subname = '' WHERE entry = 2953; Kind regards, bdebaere

I have a serious issue, I'm guessing the updates arent working correctly, i went through every single update and appiled each sql with sqlyog. I still receive this issue!!! WHY?!?!

Hi Team! I am trying to run mangos two on debian but keep running into this problem. when executing the command ./realmd i get the following. [email protected]:~/wow/bin$ ./realmd 21000 [realm-daemon] <Ctrl-C> to stop. Using configuration file ../etc/realmd.conf. Login Database total connections: 2 MySQL client library: 5.6.27 MySQL server ver: 5.6.27-2 MySQL client library: 5.6.27 MySQL server ver: 5.6.27-2 The table `db_version` indicates that your [Realmd] database does not match the expected version! [A] You have database Version: 21 Structure: 1 Content: 0 Description: revision_refactor [b] You need database Version: 21 Structure: 1 Content: 2 Description: dbdocs update You are missing content updates or you have content updates beyond the expected core version. It is recommended to run ALL database updates up to the required core version. These updates are included in the database/Realmd/Updates folder. No valid realms specified. I understand there should be an update I have tried all updates from rel18 to rel21, nothing works. Any help would be appreciated!:cool:

Well I don't know how you guys got it working because I followed everything to the mark and it still goes and checks for new updates and trying to load the blizzard launcher I am running 4.3.4 client and the right build but did not see realmlist.wtf so had to add it but things are still trying to update. God I will pay someone to help me lol. I am rerunning the file WoW Regeneration.exe

Hi Mangos team i was trying the new dev build out because of the playerbots ;D and i updated the databases and the world and char database works! but then a update the realm database, i get no error messages. but when i tryed to open the mangosd or realmd i comes with the classic "you need to update message" SQL: SELECT required_20150412_auth_realmlist FROM realmd_db_version LIMIT 1 query ERROR: Unknown column 'required_20150412_auth_realmlist' in 'field list' The table `realmd_db_version` in your [REALMD] database indicates that this database is out of date! [A] You have: --> `20150420_warden_db_log.sql` You need: --> `20150412_auth_realmlist.sql` You must apply all updates after [A] to to use mangos with this database. These updates are included in the sql/updates folder. Please read the included [README] in sql/updates for instructions on updating. but i have applyed the updates and i don't know how to fix this and i has something to do wi 20150409_Playerbot_and_Warden 20150412_01_warden_db_log 20150412_02_auth_realmlist 20150420_03_warden_db_log

Hi guys, I'm sorry to come back for questions, but I was wondering if it was possible to update my MangOS database (3.3.5 server) from the program easy mangos, with the database form your great work. And if it was possible, could it be explain by a little tutorial, as I'm a great noob in MySQL? Thank you very much and great great great work !!!

Hi all, is their a way to update honor manually instead of waiting for honor flush day? Since i doubt the honor system is functioning after 2 weeks of running my PvP server :rolleyes: UPDATE: somehow this evening the flush processed 400 of the 1500+ rows of my characters_honor_cp and no one gained a ranking. Also when booting mangosd.exe it does "loading honor standing lists = 0%" and then continues.

Using the latest revision of MangosOne, from the git. And here is i'm encountered a problem...that there is no _certain_ sql files in git repository, described in the console exception. Here is example of realmd output: The table `realmd_db_version` in your [REALMD] database indicates that this data base is out of date! [A] You have: --> `10008_01_realmd_realmd_db_version.sql` [b] You need: --> `z2426_01_realmd_relations.sql` You must apply all updates after [A] to [b] to use mangos with this database. These updates are included in the sql/updates folder. There are NO sql file with a name like this one "z2426_01_realmd_relations.sql", (synced from the git repo: https://github.com/mangosone/server/tree/master/sql ) Second example: Output from mangosd [A] You have: --> `11785_01_mangos_instance_encounters.sql` [b] You need: --> `s2054_mangos_command.sql` There is no sql file with name "11785_01_mangos_instance_encounters.sql". So i even cannot a build a chain for sql files, because i don't even know from where to start... Where can i get those files, and (maybe) another ones, that possibly missed? Beforehand thank you.

hi im setting up the world database but i got some errors then im trying to setup the world database. First i make the database "mangos" then i import the mangos.sql and then i update with 210_corepatch:mangos.sql and then i update the last with 210_updatepack.sql but with the last i got a lot of errors you can se them in the Attachments files can any explain why i got these errors and how can i fix them??? error.txt