Unkle Nuke

If you mean to use this feature to implement custom items on WoW clients newer than 3.2.2a, forget it. Blizz patched later client versions with hard-coded links to the items in the DBC files. You can still use custom items, but it requires reusing deprecated item IDs of the same type. So, if you wanted a custom dagger, you'd have to find an unused ID for a dagger that is no longer in the game. You'll still have the problem of custom items appearing in the game's UI with a large, red question mark as its icon. To my knowledge, there is no way to fix this except by using a UI add-on that overrides this behavior by forcing the client to use a specified icon.

The MaNGOS Zero project has their own database, which is the only DB available for Zero, to the best of my knowledge. You can download ZIP or G-Zipped TAR archives of all the MaNGOS sources at Github. Simply browse to the repository you wish to use, then click the Downloads link at the top in the heading that has links for Code, Files, Branches, Tags, and Downloads. This will take you to a new page with two buttons. One is for the ZIP and the other is TAR.GZ. Here's a direct link to that page for the Zero database... Downloads for mangos-zero's database. You can safely ignore the message below the buttons that there are no files. I just tested the links and it does indeed initiate a download for the database. In this way, you can acquire the latest commits for all parts of MaNGOS Zero without using Git.

Usually vmap extraction errors are due to an incorrect client version. Are you using 1.12, 1.12.1, or 1.12.2 for your client? MaNGOS Zero is only compatible with 1.12.1 and 1.12.2. Unless you're using a Spanish language client, you do not need 1.12.2 since it was a bugfix only for that particular client.

If you're running your server on the same machine you're playing WoW, then you must use the loopback address instead. That would be 127.0.0.1. Your machine's LAN IP is only used if you're running the server on a dedicated box. On the other hand, if you're allowing friends online to play, and you do not have a static IP assigned by your internet provider, I recommend using a free service like DynDNS to set a URL that is automatically forwarded. In that case, you would use the URL, which you can choose, in your realm DB. Also, don't forget to forward all the ports used by the server and client so your router's NAT and/or firewall allows those connections.

Well, you could learn to make patches out of your custom features, then re-apply them to the newest MaNGOS core so you have all kinds of fixes and improvements, NoHad.

Auctionhouse Bot, also called AHBot, is already included in the MaNGOS core, rmensen. With it, you can have the bot put random items up for auction, buy or bid on items from other players, and use the AHBot commands to put specific items up for auction. There is also a database table that allows you to configure price markup by item type and which types of items can be offered for auction. There is an alternative implementation of Auctionhouse Bot used by other forks of MaNGOS. It's based on the original version which requires setting up a player account with a character that is used as the bot. Some regard this one as more stable and it offers a little more flexibility in how auctions and buying are done, in part because you can log in as the character assigned as the bot to manually do bids and auctions. The version developed by cyberium is used in the official MaNGOS core and does not require using a player account to create the bot. It has seen a great many improvements and is already much more stable than the development version, so you may disregard rumors about instability. By reading the mangosd.conf file, you can see there are many other features also included for configuring and customizing your server. Just make sure you place all the conf files in your server directory, so MaNGOS will be able to use those features.

If you're dedicated to learning C++ and have the time to devote to it, why not be the one to finally fix the Eye of Archerus? Nothing to stop you from doing it except yourself.

Based on that statement, I think your trouble with bots isn't that they are actually invisible, they've fallen through the ground. Having vmaps enabled does help to prevent this, but you will encounter "holes" in the vmaps that will still let the bots fall through the ground. I do feel sorry for those using VS2010. From all that I've read online, Service Pack 1 caused more problems than it solved. It's still a buggy, half-broken mess if the avalanche of complaints against VS2010 are to be believed. Don't feel badly about using old hardware, blueboy. It's what you can do with your system that makes all the difference. You've done more with 32 bits that most people can ever dare to manage with the latest and greatest 64-bit hardware and software. :cool: Constructive criticism is a way of contributing. By giving feedback on how things work, it does make devs aware of areas that need improvement or implementation, which does make the software better in the long run. Although, blueboy doesn't seem to be lacking in imagination where new features are concerned! It would be nice if all of us who post in this community were also coders, bet it C++, SQL, or cranking out scripts for ScriptDev2. Unfortunately, it is a bit unreasonable to expect that. Some are content just learning about setting up and running a server while others only want a private world to play in. Programming requires a degree of dedication and time that a lot of people don't have or prefer to focus on other things. You can easily spend days just researching game features to make sure your project behaves like retail play, days more planning and writing the code, then many more days hunting bugs and fixing them. However, following blueboy's example would be a great benefit to this community. He seems to be incredibly knowledgeable and skilled now, but by his own words he was once just as clueless as the rest of us before making the choice to learn C++ and take up a project. Boy, am I ever glad he did! If you don't know how much he's done for Playerbot, take a look at the posts about the early days of Playerbot. Bots were basically useless dummies that you had to tell what to do for every little thing, when they managed to work at all!

It was my understanding that you could not equip a weapon without first learning that weapon proficiency from a trainer. Fist weapons have a separate proficiency from unarmed, so you should not be able to equip fist weapons unless your character starts with the proficiency for that weapon type or can learn it from a trainer. Aren't rogues the only class that starts with fist weapons as a proficiency? Maybe look into some sort of check to see if a character has the proper class and weapon proficiency before allowing a weapon type to be equipped?

Do you mean check if the Fist Weapon skill, spell id 15590, is in the 'playercreatinfo_spell' table for classes other than those allowed? Death Knight, Mage, Paladin, Priest, and Warlock are not allowed to learn Fist Weapons, if I recall correctly.

I'd say the current global financial crisis is something on which you should keep an eye.

Such a question would be answered more accurately by the people who created your database.

I have the GM setting in my mangosd.conf file set so GM mode is off when I log on. This way, if I forget to turn it off between sessions, I'm set back to being a normal player at my next login. In your mangosd.conf file, look for the section labeled [em]GAME MASTER SETTINGS[/em]. Set the value of [em]GM.LoginState[/em] to zero ( GM.LoginState = 0 ) to have GM mode turned off every time you log onto your server. This is a global setting and will affect [em]all[/em] GMs on your server. The default setting is two ( GM.LoginState = 2 ), which remembers the last state at log out. If you had GM mode turned on, then it will be on the next time you log in. If you had it off, then GM mode will be off next time you log in. One sure way to know if you have turned GM mode on for your character is all the names of the NPCs you encounter will appear in yellow-colored text, indicating they are regarded as neutral toward you. This is most easily noticed if you bump into an NPC or player from the opposing faction when you know they should be hostile. Green = Friendly, Red = Hostile, Orange = Unfriendly, Yellow = neutral. You can easily set GM mode with a simple chat command. By typing .gm on you will set yourself as GM. Typing .gm off will set you back to normal player status.

Are you sure the database you're using for your server does not have incorrect data for the weapon type?

You must be mindful that UI addons, like Carbonite, are developed for retail game play. I'm fairly certain the devs of Carbonite have never considered support for Playerbot, especially since doing so would likely be frowned upon by Blizz. In my years of running and tinkering with my server, the general rule has been that the more complex the addon the more likely it will conflict with the server core especially if you have core mods that use chat, like Playerbot and Auctionhouse Bot. Carbonite is infamous for conflicts both with MaNGOS and even other UI addons on retail. Titan Panel is another troublemaker. Just about any addon that makes use of the chat console or combat log will give you many headaches. In fact, Carbonite practically spams all sorts of status messages in the chat console. I know some guilds on retail will kick you if you do not disable certain functions in Carbonite because of the spamming. Sometimes the fix is as simple as disabling the features that use the chat console, like Carbonite's Punk detector. For more troublesome addons, you'll have to get your hands dirty and modify an addon's Lua code with compatibility fixes. I have always wished there was a group dedicated to making retail addons MaNGOS compatible.

I think MaNGOS will continue on, regardless of how many in the "old guard" remain. Personally, I wish Vlad would remain. He has been the tip of the spear in MaNGOS development. Regardless, we must respect Vladimir's choice and honor his long service to this community by honoring his freedom to pursue happiness where he finds it. MaNGOS was founded upon an ideal greater than just C++ code. It gives all who wish a way to learn about massive game object servers, founded upon the ideal that the freedom to learn is an inalienable human right. Thanks to those like Schmoozerd, Xfurry, Patman, SilverIce, and many others, the code does keep coming and they shine as an example for us all to follow. MaNGOS will not die so long as its people are willing to step forward and join the ranks of developers, hashing out code and suffering sleepless nights of bug hunting. This community has weathered far worse, and will remain strong so long as its members take an active part in keeping it alive. As for me, MaNGOS will never truly die, so long as I have a computer, compiler, and time to learn. I'm finally getting my hardware and software troubles sorted out, and soon plan to pick up my C++ books once more in the hopes that I may, someday, find my own patches in the "under review" section.

I certainly hope it is! Still haven't seen any working code from this brainstorm, but maybe a few neurons will connect in someone's gray matter and they'll hit upon a solution.

Is the bag you're trying to add a custom created item, like you would see on WoW-V, or is it an unused item like "Foror's Crate Of Endless Resist Gear" 36-slot? If it is an item you created, then you'll have to remap it to an unused item ID of the same type (bag). This is due to client modifications made after 3.2.2a which prevent simply adding custom items with new IDs to the database.

LOL I think nearly everyone has made that mistake at least once. :8 It's the simple things that really get you. 8)

Simple answer is yes. The long, technical answer is you can use any client version you want, but you must use a revision of MaNGOS that is compatible. Of course, you'll be using an older version of the core, an older vmaps, and enduring all the bugs that have since been fixed with newer revisions. You could backport all the fixes, but that requires a good working knowledge of the core files and C++.

Would localization of Playerbot be easier by adding a new database table for the bot responses, something like 'bot-chat' or 'bot-gossip'?

I'm sure it would be very helpful to others that encounter this problem if you would please share the solution that fixed your trouble.

A lot of your trouble is from rushing through setting up everything. Slow down! Take your time and make sure you are applying DB updates in the correct order. Read the MaNGOS, UDB, ACID, and ScriptDev2 guides carefully. When I was just beginning to learn how to compile and set up my server, I found that saving copies of the guides to my computer for quick and easy reference was a big help.

Thank you so very much for all the work you've done with Sunwell Plateau, Xfurry! It's still hard to believe there's so many original and TBC dungeons and raids that need the same attention. I can hardly wait to see what else you'll do for Sunwell. :cool:

The sharedbots branch in the portal repo is the official version for Playerbot. There are some security issues presented when using bots from other accounts. It's rather difficult to prevent other players from using the summon bot command to activate bots from other accounts, even if the account does not belong to that player. If you don't mind such "borrowing" bots from other accounts, or you're the only person playing on your server, then it's not a problem. Aside from that, the only other issue you may encounter is overloading your server by having too many active bots.