Unkle Nuke

I've read in other threads that the Blizz icon appearing next to your name is also limited by the client to GM levels 1 - 3. Custom levels above 3 (not including the security level for the MaNGOS CONSOLE) may not be able to display the icon. As Diablox has said, using the .gm chat on command is the way you turn on the icon, to chat as a GM. Otherwise, even GM levels will chat the same as regular players. If I had a dime for every bozo that did not read the manual/guide/tutorial/FAQ ......

That's a bit unrealistic to ask at this point, since Vehicle is still very much under development, with many incomplete and broken features. You're likely to crash your server with this patch, even if it was up to date. Unless traponinet or some other skilled MaNGOS programmer, who is familiar with the Vehicle code, posts a fixed patch, things are at a dead stop. Then again, Wotja might surprise everyone and pop up with a fresh commit to his repo. He's done that a few times in the past. I'm beginning to wonder if all the Core Mods devs have decided to wait until the MaNGOS devs finish overhauling the core for the new client. Cataclysm is going to change a lot of things, and it would make any current work pointless or in need of a huge rewrite. Of course, that means anyone planning to stick with WoTLK is going to be screwed when all these patches are rewritten for 4.0.

Aside from changing isInFlight to IsTaxiFlying, the function GetObjectSize has changed to GetObjectBoundingRadius as of several revisions past in the MaNGOS core. That's two changes that need to be made to the Vehicle patch that I've found so far, with help from DaViper and his brother (thanks guys!).

I'd actually like a Diablo MMO. I still play Diablo II. It would seem to be a no-brainer, since all they'd need to do is revamp the interface and switch from 3rd-person 2-D view to a 3-D view like WoW. Just so long as they don't add in some lame achievement system!! Bet you it's going to be some sci-fi virtual world thing, like James Cameron's Avatar.

"A whole new franchise", you say? I rarely keep up with game company press releases due to all the hype they're loaded with. Whatever they do, it will not be another fantasy setting. WWII has been done to death, so it will probably be some type of sci-fi game.

Game companies these days tend to be fairly predictable. I'll go with "World Of Starcraft" as my guess, but they'll probably give it a dramatic title, like "Starcraft:Empires". Unless they rip off Guild Wars, it very likely would be a FPS/MMO hybrid since the whole military combat theme might be difficult to pull off as a RPG.

I'll add this one to my core, but testing won't be easy since I'm the sole user of my server. Thank you very much for another great fix, Toinan!

The Firebomb Script is very outdated and needs fixes. I don't use YTDB. Someone else will need to step up to add fixes for it. Until that happens, the SQLs will be developed for UDB simply because that is what I use and am familiar with its structure. You're more than welcome to contribute YTDB compatible updates, Kirix.

If any of you have some phobia of using git mergetool, or you do not have a merge-diff utility installed that works with Git, you can also apply a patch in this manner: This will cause Git to create a .rej file, named for the source file, which contains the failed hunk of code that you can then open with an editor and hand edit that portion into the source. So let us say you applied Auctionhouse Bot as a .diff or .patch file, using the git apply command with the reject flag, and you have two failed parts. For example, the first failed part, or hunk, is located in AuctionHouseMgr.cpp and the second failed hunk is in Chat.cpp. If you look in the proper source folder (directory for you Linux geeks), you will notice that right next to those two files are additional files, named AuctionHouseMgr.rej and Chat.rej. Inside those files are the code sections that could not be added by Git. Simply open each .rej file and its associated source file with your editor, add those code sections where they belong, then save the source file. After you're finished editing and saving, just use git commit -a to commit all your changes to your repo and you're done!

Thank you for giving prompt attention and a courteous response to my issue, TheLuda. I've been a moderator and administrator in other community forums, over the years. Keeping things straight is nearly a full-time job, which you must somehow fit into the rest of your day. You have my sincerest gratitude for sparing some precious few minutes from more pressing matters to take care of this one, good sir.

I've looked through the Core Mods section, and even checked patches...under review, but could not find the [Not Working] Outdoor PvP topic. Your reasons for hiding or deleting this thread are not in question, rather, I am wondering now where those who do wish to try and continue development of Outdoor PvP can post their contributions. The topic titled [Working] OutdoorPvP r10049+ was started to just post a working patch. Would there be any objections to starting a new Outdoor PvP thread with the [dev] tag?

*Bump for update* Here's Outdoor PvP for MaNGOS rev. 10275... http://paste2.org/p/928790 Since the old topic seems to have disappeared, let me repeat that the C++ portion was put together by Berni and my heartfelt thanks to him for his work. The SQL part is a bit outdated, but I've been working on fixes. Current changes I've made to the SQL: * Firebomb script (Event AI OPvP) has been dropped. UDB has had this data since at least 0.10, with an update in 0.12. You do not need the Firebomb script if you're database is at least current with UDB 0.12 rev. 388. * Status announcements, found in 'mangos string', had incorrect IDs. Updated the DELETE statement to match the values in the INSERTS. If any of you are skilled with C++ or SQL, please lend a hand whenever you can. This is a community effort. Everyone is welcome to help. If you're not much of a programmer, then good ideas or even just an encouraging word is equally as important. Let's help make Outdoor PvP the best we can and make it ready for submission to the core!

You're right as far as xeross' Git repository is concerned, mrelfire, but there's nothing to stop anyone from creating their own AHBot repo and pushing fixes or simply posting diffs here for everyone to add to their local repos. @Zaranthos: Fixed correctly. Whether you know C++ or not, you can still make valuable contributions. Good ideas to improve AHBot, writing documentation, helping other AHBot users who have technical issues, or even just encouraging others by showing your appreciation and support are just a few examples of tasks anyone could do. With all the compilers, resources, tutorials, and books you can get for free, plus countless online communities dedicated to helping those who are learning, anyone can indeed learn C++ (or any other programming language), if they but have the time and will to learn. Those who always cry they do not know, have simply refused to try.

AHBot, like the rest of MaNGOS and all the patches, is open source. This means that anyone can modify or improve the code, so long as they comply with the MaNGOS license. xeross is the caretaker, but not the owner of AHBot. As EARTHWALKER said, YOU are the team.

I can't do much to help with code conflicts, but many of you have complaints that can be solved if you'd actually bother yourselves to read previous posts here and in the help sections of these forums. For configuring AHBot, it's all right there in the README. Follow it, exactly, step-by-step. Many complaints of having no items are due to forgetting the steps where you must add the proper data to the auctionhousebot database table. As for using Git, there are several ways you can apply AHBot to your master. One such method I've already described in an earlier post. For the rest of you, you're just going to have to dig in and actually learn Git. Putting it off is only going to cause more problems when you could be solving a lot of issues with just a few simple Git commands.

Just for the sake of clarity, are you referring to the patch offered by Most_Mangos or the patch authored by zergtmn, linked in RxCompiLe's post? If you did mean zergtmn's patch, am I correct in understanding that his code makes the original patch of Most_Mangos not needed?

This should be added to the core, as a GM command, level 2 or higher. Sure beats having to use .lookup creature to get the model ID and then apply it with .modify morph. What do you think, Vladimir?

If you have VC++ 2008 of any kind installed, you should already have the runtime installed as well. I think Vladimir was referring to VS 2008 users installing the VS 2010 C++ runtime for those components created using that version of VC++. Your other option is to install VS 2010.

Still more development for things like Liquid Types. faramir is currently busy with exams, but he will be back to continue mmaps.

Some code boxes are still showing as only one or two lines in my browser, Seamonkey 2.0.6. It seems to be SQL code that's affected.

It's not that anything has to be wrong with your code. Some patches have a higher priority for review than others. Please be more patient. It can sometimes take weeks for the core devs to review your work. There's few of them and a large number of patches to sort through. Thank you for your work. I'll definitely be adding this one to my server for testing. I like to have a "Week of Holidays" during the summer doldrums, where all the seasonal events get at least one day to run.

If you mean, "Don't bother unless all features are at least implemented.", then you're right. Vehicles mostly work, but not necessarily Blizz-like, and there are still several issues to be resolved such as multi-seat mounts, vehicles in battlegrounds, and vehicle bosses. Development is spotty and you have several versions of this patch floating around since there's no unified effort. That is the state of things to the best of my knowledge. A status update would be greatly appreciated.

I sincerely hope people have enough wits to indicate when a fix applies to a custom core or the official, standard core. I'm not even sure if it's permitted to post fixes for custom cores, since MaNGOS does not support them and has instructed custom core users to take up any issues with the maintainers of those cores. Assuming you can, state if a fix is only for a custom core. Please do not confuse everyone and make more problems.

Thanks for letting us know you're still breathing, xeross. lol We'll try to limp along as best we can until you've taken care of those other matters. Best of luck.

Thank you for helping those who prefer to use a patch/diff, mnocz.