Jump to content

Making MaNGOS a bit more user friendly


antz

Recommended Posts

Everyone remembers the following message:-

Map file \'/home/hyp3r/mangos/data/maps/0004331.map\' is non-compatible version (outdated?). Please, create new using ad.exe program.
Correct *.map files not found in path \'/home/hyp3r/mangos/data/maps\' or *.vmtree/*.vmtile files in \'/home/hyp3r/mangos/data/vmaps\'. Please place *.map and vmap files in appropriate directories or correct the DataDir value in the mangosd.conf file.

The above error message is terrible as the error routine is written so that a multitude of errors are forced through the same routine rather than displaying the actual issue.

Seeing as the map version number is already contained in the file (see https://github.com/mangoswiki/Wiki/wiki/Map-files), surely it would make sense to change the above message to something like:-

Map file \'/home/hyp3r/mangos/data/maps/0004331.map\' is version z1.3 (Classic), this core requires s1.3 (TBC). Please, create new files using the program ad.exe.

and then have separate error lines for the other specific errors:-

Correct *.map files not found in path \'/home/hyp3r/mangos/data/maps\'. Please place *.map files in appropriate directories or correct the DataDir value in the mangosd.conf file.

and

Correct *.vmtree/*.vmtile files in \'/home/hyp3r/mangos/data/vmaps\'. Please place *.vmap files in appropriate directories or correct the DataDir value in the mangosd.conf file.

This shouldn't be a significant amount of work to implement either, but makes the setup of a server so much clearer

Link to comment
Share on other sites

I've had to much experience writing error codes that actually make sense. Try this one on for size for the wrong map version:

Map file \'/home/hyp3r/mangos/data/maps/0004331.map\' is for (Classic), this core requires a (TBC) map. Please use TBC ad.exe.

Or

Map file \'/home/hyp3r/mangos/data/maps/0004331.map\' is for (Classic), this core requires a (TBC) map. Please use ad.exe included with TBC core.

Also, sorry for being a pain here, but I'm tired of people feeling like they did something wrong when they didn't. Blame Turbine for this one. ;)

MaNGOS <core version> is having a hard time finding the proper map (*.map) files in the path \'/home/hyp3/mangos/data/maps\'. Please make sure the maps are in the proper directory and, if necessary, you have specified the proper datadir value in your mangosd.conf file.

Yes, I know. Sometimes proper error messages can get messy. The only other thing I can think of is go back to the old Macintosh way of doing things:

We at MaNGOS are sorry to inform you, however MaNGOS has encountered an error. CODE: 15

And then we can have a file included with the MaNGOS Distro that explains all of the error codes in plain english/french/russian, whatever... OR we could have a web page that explains all the error codes. And try, very hard, to keep the error codes uniform between all the cores.

Just ideas.

Link to comment
Share on other sites

That's the one thing I do hate about Errors-Not enough Documentation. Yes you could go back to the way Apple did it in OS 6.x to 7.x with Bomb Codes but I like the way they handled it in OS 9.x with an Error Code like Error 15 and it linked via a template to the Error which stated something like this to the Screen: Error 15 - Incorrect Maps files- you need to use the Current XXXX for this Program. I don't see the need to really though the Hard Error Name but the Error Code and a little Explanation would be a lot more helpful. Since the DB Connection could be started early in the start-up process a link to the MySQL DB and the template could be stored outside of the Core itself and referenced on a as needed biases plus an easier to update location.

Another problem I've seen in the past is on start-up of most of the Cores it throughs a lot of DB Errors and the Developers refuse to answer any questions as to how to fix with the old blurb of it will be fixed in the next update! but never gets fixed along with most people have no clue as to what to do to fix and end up giving up on the whole thing.

Link to comment
Share on other sites

There is actually no reason why an Error message table could not be created and directly pulled from for these errors and even set it up so that is can display localised message too based on the mangos.conf setting.

Link to comment
Share on other sites

  • 10 months later...

Well, I've been thinking, for a while now, about this thread. Why don't we just use a 3-dimensional array. You could have one array for the errors, another array to display the error code, and the third array could display the meaning of the code...? Or just do a 2-d array. Error itself and then the english version of the error.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • 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