Jump to content

Syenet

Members
  • Posts

    32
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Syenet's Achievements

Advanced Member

Advanced Member (3/3)

0

Reputation

  1. Hello kennumen: Here's my system info: OS: Vista x64 SP2 IDE: VS2010 SP1 mangos: portal[new-ai] db: UDB 0.12.2.403 I'm really curious about how you manage to debug it with break points in VS2010. When I'm trying to start debug, it always tells me something previously built is outdated, and when rebuilding is done, it tells me 'game.lib' can't be opened. The starting project in the solution is 'game', so I suppose when I start debugging the 'mangosd.exe' should run, am I right? or are there configs of debug I missed? I really wish I could find precisely where the problem is directly in VS, because looking at logs is way too difficult. Exactly. The call stack in the log is quite confusing. I searched the entire call hierarchy of PlayerbotAI::_HandleCommandSkill for Creature::SetLevitate, it in fact doesn't exist there. That's why I want to be able to debug it in runtime to see which line of code causes it. BTW, what I'm testing is your latest portal[new-ai], absolutely clean and I haven't changed a single line. Edit: Account's gmlevel seems irrelevant to this issue, I changed it to 0 and the server still crashed.
  2. I think these are the creating procedures: and then these are called in sequence every few seconds: EDIT: I found a new issue: Command 'skill learn [LINK]' will cause the server to crash, tested several times and confirmed in both 'playerbot/mangos' & 'portal_new-ai'. This is the log file: This is the crash info: In addition, am I supposed to debug the code only by examining logs? I tried debugging directly in VS2010 and it told me it couldn't open program 'game.lib'. Can I debug it line by line using break points?
  3. Thanks for the info. I made a patch of core-portal to get what have been modified on the basis of the original core, but I can't find how exactly a bot is actually created. I think some codes in 'CharacterHandler.cpp', 'Player.cpp', 'WorldSession.cpp' might do the trick. I searched for '.bot add' in order to take a tour through the creating & initializing process, but no result. Could you spare some time to give me a little description of it? Edit: OK, I find '.bot add' in 'ChatHandler::HandlePlayerbotCommand(char* args)', I'll trace the call stack, sorry for my hasty request.
  4. Hello blueboy: It's been a year since I came here last time, and very glad to see the efforts and progress all you guys have made, especially about the ai part. I see the branches changed, are the new ai scripts merged into 'master' or only stored in 'new-ai'? cause I checked the last-2-month updates committed of each branch and found them almost the same. Besides, I tested 'playerbot/mangos', the most stable one, commands like 'report', 'orders' don't work, neither do some shortcuts like 's', 'skill l'. Is there any place where I can get what you're currently working on? I take a glance at 'bot_todo.txt', it seems outdated. I think you can make a list of both accomplished and upcoming features on the very 1st post of this thread, also suggest you open another thread to seperate discussions about basic functions from those about PvE/PvP ai scripts. Thanks for the brilliant work, wish I could help. Edit: Sorry, I see the changes ahead of 'master' in 'new-ai', I'll check the code.
  5. problem resolved. After sleeping last night, I recompiled mangos and everything goes smoothly now.
  6. mangos: mangos-mangos-v0.16-1810-ga9a9715.zip (from github) SD2: scriptdev2-scriptdev2-1d33dfd (from github) UDB: 0.12.2.403 (from svn 402Full->403Core->403UpdatePack) Compiler: VS2010 SP1 System: Windows Vista x64 Carefully proceed according to the installation guide, but when I try to run mangosd.exe, it crashed instantly. Here's the DBErrors.log: Having searched the entire google with no useful info, I'm really confused about it. I've setup my server quite a few times before, often came out errors due to outdated db with explicit explainations in the log files, and I never came across such issue. The table's name should be "realmd_db_version" instead of the one displayed above. What on earth happened? Please help me.
  7. Hello LordPsyan Thanks for your suggestion, I'm using git to fetch updates from remotes and merge them into my mangos. I've never asked anyone to push commits for me, what I'm doing here is reporting bugs and providing my concerns, I'm learning the code and I wish I could help. blueboy is real kind, he always gives me examples and explainations even if I bring up my minimum doubts, and I never ask him to do that much, I really appreciate it. The reason I submit posts here is that I think it may be playerbot issues, and probably it may be not, I'm not sure, after all I'm not professional. If any of my behaviors makes anyone feel uncomfortable, I'm sorry for that. I don't know it's annoying and this is what I can help with at this stage. To blueboy: I think the boss issue is because of sd2, while the bots keep attaking, they strangely don't have a target, or say it they have an invisible target. I noticed that some npc or creatures are unselectable under certain circumstances, maybe this is the reason.
  8. I have seen that post and I'll try /reload next time. In my case, pet's name is normal. I almost forgot to tell you, if 'Unknown' issue occurs, the social panel of client is totally crashed. All tabs will be displayed as the 1st tab 'friendlist'. (I can switch to other tabs but the panel keeps displaying the 1st tab). Is it related to cache as well?
  9. Yes, but I have no choice but to leave the instance and reform the group. I said I can entirely close the client to resolve the 'Unknown' issue, but I want to find another more convenient way to fix it, and try to find out the reason to fix it in the code. So I tried reforming the group, but always fatality. Since you questioned, I also think it might be a cache issue, so I'm not sure if it's fixable in your code.
  10. hello blueboy, here is the detail: I've been testing the sd2 raid scripts recently, and I add 9 bots of each class, so we make up a 10-player raid group. I notice that sometimes bots will keep attacking the boss or mobs even if it's dead, I think it might be errors of sd2 scripts. Well this bug includes two different types: 1. Bots will keep the attacking pose (casting, aiming)after the target is down. This one occurs real OFTEN in any scenario and I guess it's because there might be no "cancel" command for bots so they just can't stop their last action. I see that sometimes bots are able to finish the casting, like casting frostbolt against the corpse of DEAD target, well this maybe what it's supposed to be, but unfortunately this errors still occurs now and then. Honestly this one isn't that annoying cause bots can still follow your command, and this one could be fixed when bots begin to attack the next target(I don't know why, but it truly can be fixed automatically). The only thing makes me feel uncomfortable is that occasionally the casting SOUND is being repeated over and over, and the VOLUME is real high. To make it quiet, I simply logoff and relogin, this trick works perfectly. 2. Bots will be attacking the boss(in an instance), AFTER it's down and looted, LIKE CRAZY. OMG I don't know why bots hate the boss that much, they just really enjoy torturing the corpse. They won't follow my command, and to continue the raid, I have to get out of the instance and reenter it. I think this error may have nothing to do with your code, it's more likely to be sd2 error(not sure). So, when the 1st error occurs, I play the logoffin trick to resolve it. Well, this sound good, but SOMETIMES(I really don't like this word cause it makes me unable to confirm the reason), when I log back in the server, MY NAME AND MY PARTY MEMBERS' NAMES APPEAR TO BE UNKNOWN, look, I mean the member of my team, not everyone of the raid group. If I'm in team1, then every member of team1 encounters this error, including myself, but team2 remains the same as normal. Actually each member of team1 is existing in the world but 'Unknown' makes the server unable to find them, so any command that covers the name of team1 member will not work.(such as 'co' commands). This time I come up with the idea of quiting and reforming the raid group. Instead of solving this issue, this solution SOMETIMES happens to kill the 'mangosd.exe'. There're several crash dumps of this error, and some parts of these dumps are the same, so I posted these parts above. If you'd like to see the entire file, I'd better upload it somewhere for you. BTW these files are almost the same. I know 'SOMETIMES' is the most annoying crap, and I will try to figure out how to reappear this error and find the direct reason. I'm using your latest 'portal/training' merged with 'cyberium/new_ahbot'. The merging is done by your helping me resolve the conflicts. But I disable the ahbot everytime I fire up the server, so i'm sure ahbot has nothing to do with this issue.
  11. If I log off in a raid instance, me and my party members' names will appear to be "Unknown" when I log back in. And if I quit the raid group, the server may crash sometimes. this is the crash info: Call stack: Address Frame Function SourceFile 004FD8E6 00000000 std::_Tree<std::_Tset_traits<Player *,std::less<Player *>,std::allocator<Player *>,0> >::_Eqrange+6 004FFEBA 00000000 Group::RemoveInvite+1A 00536EE3 00000000 Player::UninviteFromGroup+13 0060E791 00000000 WorldSession::LogoutPlayer+791 007B754C 00000000 WorldSession::HandleLogoutRequestOpcode+1EC 0060A5D1 00000000 WorldSession::ExecuteOpcode+21 0060EDBD 00000000 WorldSession::Update+BD 004851B8 00000000 World::UpdateSessions+98 0048798C 00000000 World::Update+1AC 00457662 00000000 WorldRunnable::run+52 00465EE0 00000000 ACE_Based::Thread::ThreadTask+10 67BE7064 00000000 ACE_OS_Thread_Adapter::invoke+74 6B40C6DE 00000000 _endthreadex+3A 6B40C788 00000000 _endthreadex+E4 7692ECCB 00000000 BaseThreadInitThunk+E 772FD24D 00000000 RtlCreateUserProcess+8C 772FD45F 00000000 RtlCreateProcessParameters+4E ======================== Local Variables And Parameters Call stack: Address Frame Function SourceFile 004FD8E6 00000000 std::_Tree<std::_Tset_traits<Player *,std::less<Player *>,std::allocator<Player *>,0> >::_Eqrange+6 Local <user defined> '_Keyval' 004FFEBA 00000000 Group::RemoveInvite+1A Local <user defined> 'player' 00536EE3 00000000 Player::UninviteFromGroup+13 0060E791 00000000 WorldSession::LogoutPlayer+791 punting on symbol Save Local <user defined> 'data' Local <user defined> 'aset' Local <user defined> 'itr' Local <user defined> 'guild' 007B754C 00000000 WorldSession::HandleLogoutRequestOpcode+1EC Local <user defined> '__formal' Local <user defined> 'data' Local <user defined> 'data' Local <user defined> 'data' 0060A5D1 00000000 WorldSession::ExecuteOpcode+21 Local <user defined> 'opHandle' Local <user defined> 'packet' 0060EDBD 00000000 WorldSession::Update+BD punting on symbol diff Local <user defined> 'updater' Local <user defined> 'packet' Local <user defined> 'itr' Local <user defined> 'pBotWorldSession' Local <user defined> 'packet' 004851B8 00000000 World::UpdateSessions+98 punting on symbol diff Local <user defined> 'sess' Local <user defined> 'next' Local <user defined> 'updater' 0048798C 00000000 World::Update+1AC punting on symbol diff punting on symbol maxClientsNum 00457662 00000000 WorldRunnable::run+52 00465EE0 00000000 ACE_Based::Thread::ThreadTask+10 punting on symbol param 67BE7064 00000000 ACE_OS_Thread_Adapter::invoke+74 punting on symbol status 6B40C6DE 00000000 _endthreadex+3A 6B40C788 00000000 _endthreadex+E4 7692ECCB 00000000 BaseThreadInitThunk+E 772FD24D 00000000 RtlCreateUserProcess+8C 772FD45F 00000000 RtlCreateProcessParameters+4E ======================== Global Variables I can resolve the "Unknown" issue by completely eliminating the "wow.exe", but I don't know what's causing this, it is sort of annoying.
  12. Yes, action queue, priority, event handling...this structure is much better than the original version which runs the whole iteration again and again, and this is exactly what we need to improve AI to a new level. I'll try it out and see the detail of those features, terrific work dude!
  13. Everything's fine now, thanks for the help. I just figured out how the "loot" part works, bots will skin only if "collect skin" is set true, otherwise they won't. And if bots meet a failed attempt, they'll keep the gathering pose untill next "get".
  14. Sorry, what is 3 line pattern? which 3 line? Do you mean this: line 1: line 2: line 3: line 4: Modification........ line 5: line 6: line 7: And I need to ensure lines 1~3 and 5~7 in patch are exactly the same with the ones in code?
  15. The server crashes everytime after it's set up, to be specific, everytime after a line of SQL query shows up in "mangosd.exe". That SQL query seems about reading character infos from db where guid = 0, then I try disabling ahbot, then the server is fine. So your "ahbot" is the version that requires an existing character to be the "AuctionHouseBot" right? And I need to specify the account and guid of this character in "mangosd.conf". I remember there's version of ahbot which doesn't need a character, maybe new_ahbot. Which version is the latest and stable? I create a patch from branch "new_ahbot" of "..cyberium/mangos.git", when I'm trying to apply it to branch "master" of "..blueboy/portal.git", I get these errors: error: patch failed: configure.ac:363 error: patch failed: src/game/Makefile.am:17 error: patch failed: src/game/World.cpp:1329 error: patch failed: win/VC100/game.vcxproj.filters:448 I think these are small problems but I don't know how to fix.
×
×
  • 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