erazare

did you happen to look on the actual repo the last commit it matches to mangos? vehicles on tasssadar needs to updated considerably posting compile errors here is kinda pointless since Tasss has not bothered to even poke its face in here for some time. i suggest you check with Sajla or Bizkut... although be warned Salja's EVO repo *may* not always be compat with mangos thanks tot eh odd hybrid they are building over there hey Sajla.. you ever manage to get acherus to work right on your repo? how did you fix the minecarts?

the gossip enum can be easily solved... I can pack some gossip up for you if you like but you need to populate gossip_menu table in your db

with the exception of ahbot of course.. another thing you need to keep in mind is that the Vehicles repo hasnt been updated in quite some time and still has the unit.cpp errors in it

well i am running our private server using your new code changes and it works beautiful I am ready to see people dev deeper in this.. like... they never loot corpses (my bots havent... they go stand next to them but they dont take anything) would also like to see them pick up quest items when they need them and oh... what would be super is if they would farm mines and other trade items so that when i login I can make metals and shit... even better if they could be doing that too... maybe if there is a long pause or no near threat or something

yeah... if it makes you feel better, change the txt extension to .patch... it goes right in smooth as a babys ass

if this is going to be one of those LINUX ONLY builds like Tasssadar's ScriptDev2 project you can count my assistance out... I dont have time to play with that crap.. I am running Win7

i havent tried updating to 9202 yet (nor shall i just yet) but they may have even further fuxored movement... check http://github.com/mangos/mangos/commit/824451aea4b8e87ddac4aa6501b30afb1d8ab098 just letting you know before it comes up blue

blueboy do you have this in your repo or is it still dev-ving? nevermind just checked your repo... no updates *lol* lets see if i can apply this

well the reason I am saying this is I am running a server with 9197, mangchat, playerbot, and ahbot as well as the vehicle mod, and the new ShadowFangKeep from SD2 (still in the dev section) oh and the Eye of Acherus mod... and your error is not in the mix... I am not running a repack either.. i built my repo.

its has to be one of your modifications affecting the code. older revs of mangchat aside from my repo will do this to you... what code modifications are you running aside from the main mangos core?

sure blueboy not a problem will get on that asap edit someone beat me to it... ok yeah just waking up kids... a little bit lost on what has transpired..

one thing i like about core modifications as opposed to mangos proper, is that when you write these it doesnt matter how you do it so long as it works and is easy enough to build off of (like comments and shit) not a bunch of predefined BS... make it work and we're all happy =)

excellent progress XEQT I am getting ready to crash now as its 2:25AM EST... but I will check this thread when i get up and if no one has it solved yet I will work on it... blueboy, whattya think?

thank you blueboy I look forward to your results... currently on my private server community I told the players that the bots are suffering from a rare case of radiation poisoning and may act irregular

actually... an even more interesting thought: on playerbot the bots follow using MOVEMENT_FOLLOW instead of MONSTER_MOVE_ maybe it can be adapted this way instead?

note: this error occurs in 9175 as well... I am tracing it back through the mangos releases to find out which rev it stopped working with.

Windows 7 Ultimate Visual Studio 2008 Team Edition I dont know what going on... if you clone YOUR repo then pull say 9193 (or wherever they are at now) directly from mangos, this error will occur for grouping

so far as I can see... and i am very likely wrong.. the code for playerbot to accept group is here // Handle Group invites (auto accept if master is in group, otherwise decline & send message case SMSG_GROUP_INVITE: { if (m_bot->GetGroupInvite()) { const Group* const grp = m_bot->GetGroupInvite(); if (!grp) return; Player* const inviter = sObjectMgr.GetPlayer(grp->GetLeaderGUID()); if (!inviter) return; WorldPacket p; if (!canObeyCommandFrom(*inviter)) { std::string buf = "I can't accept your invite unless you first invite my master "; buf += GetMaster()->GetName(); buf += "."; SendWhisper(buf, *inviter); m_bot->GetSession()->HandleGroupDeclineOpcode(p); // packet not used } else m_bot->GetSession()->HandleGroupAcceptOpcode(p); // packet not used } return; } My only guess is that something in the newer cores is altered not allowing the server to comprehend the data its looking for. is it sObjectMgr? beats me..really dont know.. just trying to find the source of the problem XEQT > this has been happening with every rev i find from 9178 and up... it works fine with the build it was built for so blueboy isnt at any fault, but time for progress people =)

would love to help but i need to figure out how to fix the playerbot repo first... then I will testdev your repo for you happily

you go ahead and try that buddy... might be interesting. listen bigger issue at hand.. I just built 919+ with playerbot and the stupid error that imentioned still exists.. it was ONLY playerbot and a recent rev of mangos... now... I am going to pull ***ONLY*** your blueboy repo and then build it but I am going to put a MAJOR fail expectancy sure the bot builds, sure you can call the bot into world... but you CANNOT group them P.S. this is on ALL repos of playerbot except the main playerbot repo which i do not even mess with i.e. the original playerbot repo, not blue's ok update >> playerbot on blue's repo works just fine... but merge it with anything recent and it does not... something has changed in mangos code to cause this issue

here is a thought... change MONSTER_MOVE_WALK to MONSTER_MOVE_UNK7 IDK.. worth a shot.. UNK7, 9,10,11, & 12 are all labeled run... maybe one of those will solve it

out of curiousity if the code in causing this issue is + else if (owner.isInCombat()) why not just edit it back out? it doesnt look much like it would harm anything being removed... I am going to try it on my next build just for kicks but... this simple fix has worked before...

ok for the record, it is NOT vehicle that is doing this to cause the end result of the bots behaving badly... I just compiled tiamat without the vehicle branch and it still returns the errors I listed earlier.. all branches in my build are mangos based not Tasssadar's

I'll check this out on my next dev build... i have been compiling the server roughly 15x a day so it wont be long til i try this out

cool thanks blueboy... I am checking out bizkut's repo see if i can use it to jump off from update : I compiled bizkuts and the same error occurs in the CLI and same bot behaviour on world