kuzminsv_

Please note that with the recent commits the Random Bot feature has been changed. The main change is that random bots are now logged in on server start and remains logged in until the server is shut down. This means they are not dependend on any player and do not use master player anymore. Any player with the appropriate level and gear can invite random bots to a group and the player will be bot's master until bot is uninvited. Also, limited support is added to dungeon finder system so random bots should join dungeons if there are not enough non-bot players. Random bot feature is still experimental and available in R2 brach only at the moment. rndbot reset command is recommented to remove old bots from the system

Ai Playerbot makes no core changes that could affect script compilation. There are no DB restrictions as well. Everything that works with unmodified mangos core will work with Ai Playerbot. @Gadget2006 There is no support for Visual Studio Express for R2 branch (this is forced by R2 developers). Although you can compile Ai Playerbot with VS Express using solution files provided this is not true for ScriptDev2 R2. Please refer to R2 forum for more information about their compilation on Windows. The code is usually tested with: cmangos branch - UDB, ScriptDev2 R2 branch - YTDB+R2 mods, ScriptDev2R2 zero branch - mangos-zero DB, ScriptDev0 one branch - mangos-one DB, ScriptDev1

Just fixed mage issue in [ai-7] GenericMageNonCombatStrategy inheritance fix (preventing mage bot following master) in mangosr2-wotlk-ai branch. Cannot reproduce mount vendor issue (tried Orgrimmar and Stormwind ones with mangosr2-wotlk-ai branch). Are you sure there is no crash log. Can you try to debug the server in visual studio or gdb? It will stop at crash point.

Random bot feature is experimental, but it is working fine for me. Please set AiPlayerbot.RandomBotAutologin = 1 in aiplayerbot.conf (I'l make it default choice in future commits). If AiPlayerbot.RandomBotAutologin = 1 each player brings with him some bots online (the system chooses randomly a subset of characters available in random account list). They became randomized in race, class, level, equipment, talents, etc. and teleported to a random place in the wolrd where they start grinding (attack anything they see). Non-friendly bots will even ambush the master sometimes starting accident pvp attacks. The player can open "who" window and choose some bots iniviting them to the group, then teleport using a meeting stone or 'summon' command at the inn or city. The bots will ignore any command from player until invited to a group. The subset will be changed after some time (a week by default). A regular player is allowed to control only the subset of random bots the system gave to him (they also should be no more that +5 levels). Although GM can add/remove any bot from random account list but they will listen to him only. This is a limitation as bots share master's session so they can spy his packets. This can be configured by settings config parameters such as: randomBotAutologin = config.GetBoolDefault("AiPlayerbot.RandomBotAutologin", false); minRandomBots = config.GetIntDefault("AiPlayerbot.MinRandomBots", 1); maxRandomBots = config.GetIntDefault("AiPlayerbot.MaxRandomBots", 10); randomBotUpdateInterval = config.GetIntDefault("AiPlayerbot.RandomBotUpdateInterval", 60); randomBotCountChangeInterval = config.GetIntDefault("AiPlayerbot.RandomBotCountChangeInterval", 5 * 24 * 3600); minRandomBotInWorldTime = config.GetIntDefault("AiPlayerbot.MinRandomBotInWorldTime", 2 * 3600); maxRandomBotInWorldTime = config.GetIntDefault("AiPlayerbot.MaxRandomBotInWorldTime", 14 * 24 * 3600); minRandomBotRandomizeTime = config.GetIntDefault("AiPlayerbot.MinRandomBotRandomizeTime", 2 * 3600); maxRandomRandomizeTime = config.GetIntDefault("AiPlayerbot.MaxRandomRandomizeTime", 14 * 24 * 3600); minRandomBotPvpTime = config.GetIntDefault("AiPlayerbot.MinRandomBotPvpTime", 120); maxRandomBotPvpTime = config.GetIntDefault("AiPlayerbot.MaxRandomBotPvpTime", 3 * 3600); randomBotTeleportDistance = config.GetIntDefault("AiPlayerbot.RandomBotTeleportDistance", 400); minRandomBotsPerInterval = config.GetIntDefault("AiPlayerbot.MinRandomBotsPerInterval", 1); maxRandomBotsPerInterval = config.GetIntDefault("AiPlayerbot.MaxRandomBotsPerInterval", 5); randomBotEnemyPercent = config.GetIntDefault("AiPlayerbot.RandomBotEnemyPercent", 30); The idea is that the player uses a dungeon finder and random bots join player's group. This is not implemented yet The only way is to open 'who' window and try to speak with adequate level players hoping they answer "please invite me to your group first". Then player can go to a meeting stone or an inn and summon them.

It is very easy. Just change the text at PlayerbotAI:202 to any message you want. if (fromPlayer.GetObjectGuid() != GetMaster()->GetObjectGuid()) { WorldPacket data(SMSG_MESSAGECHAT, 1024); bot->BuildPlayerChat(&data, CHAT_MSG_WHISPER, "I speak to my master only", LANG_UNIVERSAL); GetMaster()->GetSession()->SendPacket(&data); return; }

Please note that the branch name has been changed on GitHub from ai to mangos-wotlk-ai - for 3.3.5a client mangos-one-ai - for 2.4.3 client mangos-zero-ai - for 1.12 client mangos-wotlk-ai is the main replacement branch of ai branch. Although basic Ai Playerbot features work for other mangos versions these branches are still experimental.

Playerbot AI is purely PVE, it is designed for leveling, performing quests, visiting dungeons and raids with bots so the master player MUST be in a party. Although bot AI is powerful enough to take out many high heroic dungeon bosses (In fact, a proper equipped party of one skilled player and 4 bots can go through a 5-man heroic dungeon with no single death making WoW a single-player game), bots still require master's control, he should tell them where to go, when to attack or so. PVP is something very new to AI Playerbot. It is under development at the moment and unexpected things can happen. There is no plans for battlegrounds and arenas other that players can bring some bots with them. I think bot will never be enough to take out a skilled player in pvp The main goal of this project is educational: an object-oriented approach to AI development (maybe including machine learning and neuron nets in future). The project goals are the same as Blueboy's playerbot has and I'll be happy to contribute my code but due to architectural reasons I see no way to merge there at the moment.

Hello there. I see a lot of people wants to try ai playerbot with mangos different versions. Unfortunately I have very little time I can spare on playerbot so maintaining multiple branches could be an issue. Ai Playerbot has very little modifications in the core (almost all logic is concentrated in playerbot directory). So in case if someone desides to try a simple merge my suggestion would be to make a diff between ai branch and mangos/master then apply this patch to the new codebase. If the API is similar to mangos/master there would be no big deal to make it compile.

In the original this projects was used just to enhance a single private server (having a lot of beginner players) so they could level and do some dungeons and raids even if no other is online for training purposes. As they had some positive feedback the code is become shared and development continued. So if somebody finds this useful please feel free to fork, create a patch or anything else as this is exactly what is open-source is for. The name "Playerbot AI" is just because this was the fork of "Playerbot" some years ago, but now it is almost completely rewritten and is not compatible with blueboy's branch (unfortunately the compatibility was lost in architecture: Ai Playerbot is object-oriented while blueboy one is functional-oriented). From player's point of view, the main difference from blueboy's playerbot is that this one is PvE-oriented, as blueboy's one is PvP-oriented.

Unfortunately there is no specific branch for BC or Mangos Zero, only WoTLK (3.3.5a) is currently supported, Regarding to talent specs, the bot on login determines which talent spec he has and switches to this strategy, so if a mage has 40 points in frost and less points in fire and arcane it won't use fire and arcane spells as they probably are not so efficient. Anyway the bot master can change his bot behaviour in any time whispering to him: /w botname co +strategy1,+strategy2,-strategy3,.... E.g. if you whisper /w botname co +fire the mage bot will switch to fire spells (which is dictated by fire strategy). The intention to do this is making bot support each other in party. So, if you have 3 druids in party (restoration, bear and balance) the bot ai should know this and bear will use threat-generating abilities, balance - dps and restoration will be healer). You can always change their roles though. You can whisper any invalid command and if bot do not understand what to do it will reply with a little help, such as: Unknown command: jkfjhgfg Whisper any of: ... Possible strategies are: fire, frost, arcane,.... Please feel free to command him to use any other strategy. Unfortunately is is not possible to specify custom