I wanted to give an update on my most recent working within the Dragonblight before I go away on my much needed vacation.
My most recent endeavour to correct the spawn locations of the many Arctic Hare has been a very slow and daunting one. What started in the Dragonblight spilled into the Borean Tundra and Zul'Drak. But I am happy to say that this portion is about 75% complete.
In addition to the ever troublesome dust bunn..I mean Arctic Hare, I have poked around wi
Today I bring you a quick update on the Rabbid Grizzly and the Blighted Elk that roam the Dragonsblight. Reworked all spawn locations and removed a huge amount of duplicates.
I have added a before and after picture of an area that showed the most obvious improvement.
Although it has only been one day from my opening post, I have been working on the Arctic grizzly and Arctic cubs for about two weeks now. I am happy to say 647 waypoints with a total of 776 lines later, they now are working correctly. (As of this writing they still require some scripting)
The Arctic Grizzly and cubs now have the following corrections Spawn locations.
Linking - slave/master/flags.
21 duplicates removed between the two.
Hello everyone, I thought the work I have been doing on Dragonblight would be a great opportunity to start my first blog. This is the largest and most complex undertaking I have ever taken on here at MaNGOS and wanted you all to be a part of its progress.
As a side note and something I would like every reader to keep in mind is that the when I speak of "progress" or "percent completed" it is based on the personal end goals I set for myself when the thought of doing an overhaul on the zone
We have had two branches: Release20 and develop21. develop21 was supposed to be a temporary dev branch, but has been in use for over a year.
Well, as of today they are now merged as a single master branch !!
I have updated Appveyor and Travis (our test tools) to point to the new branch.
@Unkle Nuke has completed the merging of the various branches of Mangos Zero server and database repos and I'd like to express my gratitude for his work on that as it was not an easy task.
You might want to re-clone your repos to ensure that you now have the latest changes !!
He is now turning his attention to Mangos One and Two to perform his magic there too !!
With Mangos Zero (and too a lesser degree Mangos One and Two) we have been developing on the develop21 branch, while the master branch has remained untouched.
This was only supposed to be a short term thing and has ended up being continued for over 2 years.
Part of the changes will be to merge the two branches into a single branch again (master) and we will only use another branch when adding special development tasks which require group input.
@Unkle Nuke has volunteered to help
It's been a long long time since we last did a full release of Mangos (any of the cores) and it's long overdue.
This is a blog to explain what we're doing and why, plus should hopefully act as a guide for when we do this next time.
Been awhile since my last blog entry!
So it was back in 2015 we added the "LoadAllGridsOnMaps" option, those of you that have played with it will know it loads all NPCs on whatever map ID you put into the .conf so for example you could put 530 and always have NPCs loaded, pathing and reacting as if players were nearby.
Now have I have tested with this the past few months over on Covenant-WoW.com and noticed that while NPCs do path and react to one and another, there is a
I have put the final touches to the DBC wiki exporter and if you look at the wiki section for DBC files (for Zero Only ATM) you will see the results.
The DBC databases will end up in a github repo soon and I'll post the URL here.
Any comments or suggestions, please let me know.
The next stage of this project is a dbcDocs editor. I have the skeleton of this designed and just need to find the time to complete it.
It will have two modes of operation: local and remote
The Wiki is the one area where a majority of information is cross core applicable.
- During my testing a came across a few problems.
in the dbcField table we recorded the dbc File, fieldname, description and field position but this hid a more fundamental problem.
- Different cores have the same field with the same meaning, but in a different position. The current DB design would mean that the description information would have to be entered multiple times - each time the field was in
Now that we had the data in the DB it was time for the next step.
I wrote a quick app to read through the DBC table entries and add an entry to dbcFile, I also wrote a helper function to calculate the client masks based on the selected core.
Worked like a dream
I then extended it to use the second query to populate the dbcField table with the fields from each dbc file.
Next I also added a function to read the DBC_definition.xml from mangos extractor to populate any additional
Now that we have a majority of the data already in the Database, we now need to work out how to get meaningful information back out !
Thankfully MySQL does provide us with a way of doing this. In the following example my main database containing the DBC data and we are going to query for records for MangosZero - so tables beginning dbc0_
SELECT DISTINCT TABLE_NAME AS DBCFilename FROM information_schema.columns
WHERE table_schema = 'dbc' AND table_name LIKE 'dbc0_%'
This returns a ni
Lets start with the basics...
For each DBC File we want to store the following information
A unique Id for this file (primary key and autonumber).
A short description of what the File is/does.
Some notes about the File.
Which client(s) it's present in.
Whether MaNGOS actually uses the file.
Whether to show the contents of the file in the wiki.
so the SQL table definition will be:
/*Table structure for table `dbcfile` */
CREATE TABLE `dbcfile` (
Using the tool Mangos Extractor, I have extracted the DBC's from MangosZero, MangosOne, MangosTwo and MangosThree
- I made a slight change to each of the files to change the tablenames from dbc_xxxx to dbc0_xxx - which 0 is the core number
I then loaded then all into a new database a created called DBC (imaginative I know :D)
The next part is mainly for use with the Wiki part of the proje
For many many years now I have found the DBC handling in MaNGOS odd in that (to me at least) it is a perfect candidate for moving the data into a database, but has always been shunned
Using the Mangos Extractor (found in the MangosTools github repo), the data can be extracted into sql files which can then be loaded into the db.
Why bother you may ask ?
1) Having the data in a db and mangos access it from there mean
Well welcome to the new getMaNGOS website!
It was 2013 when I last performed a big change here at getMaNGOS, that is when I setup the old site that was running on vbulletin. Myself and @antz agreed several months ago that getMaNGOS needed a new site and here it is!
You will notice most of the new site is fully integrated, this is because most of the site is designed by me in the Invision Power Board suite which is the software powering this new site.
Few new things: