Jump to content

kennumen

Members
  • Posts

    105
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

About kennumen

  • Birthday 01/01/1

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

kennumen's Achievements

Advanced Member

Advanced Member (3/3)

0

Reputation

  1. *cough* *choke* say what now? I don't understand what you're saying... It simply does not compute. Anyway isn't that what playerbotai.conf's PlayerbotAI.DisableBots = 1 or in the worst case PlayerbotAI.MaxNumBots = 0 are for? Alright, alright, I'll stop heckling you Good on you to provide gmguy as a standalone patch.
  2. color me confused - had the gmguy code not been merged into the playerbot master branch?
  3. https://github.com/blueboy/portal/blob/master/sql/playerbotai/FULL_playerbotai_characters_r7.sql there's currently three tables: 16. ) ENGINE=MyISAM DEFAULT CHARSET=utf8 ROW_FORMAT=FIXED COMMENT='Used DB version notes'; 115. ) ENGINE=MyISAM DEFAULT CHARSET=utf8 ROW_FORMAT=FIXED COMMENT='PlayerbotAI TalentSpec system'; 208. ) ENGINE=MyISAM DEFAULT CHARSET=utf8 ROW_FORMAT=FIXED COMMENT='Persistent Playerbot settings per alt'; I know you can't run it with an old version (table 1) but apparently you can without? However the TalentSpec system (table 2) will not have any 'auto'-allocation talent trees although you will still be able to manually grant your bots one talent at a time. There will also be no option to have some bot data persist (table 3) in between logouts, which could be countered by using macros or just plain giving the commands each time you log in your bots. You can play without (if you say so) but you'll be missing a few things of convenience.
  4. Playerbot forums are a cool place but I've noticed they have issues from time to time. Feel free to post your bug report there, here, or (perhaps the best option) make an issue out of it. Thanks for the kind words but blueboy keeps playerbot alive. I just fix what annoys me, when I have the time to play.
  5. Nice. I've been dropping non-essential quests (haven't run across a quest series so far - that I know of) and completing essential ones (just the druid bear quest so far) with the mangos admin command ".quest complete [Quest Hlink]" (notice the dot). GMGuy would be super interesting if it wasn't just me on the server Plus it's one less branch to maintain. Woot!
  6. can't really see anything changed other than the merge so... it was a merge conflict with master? Or was my compile fine because I haven't updated SD2 in a while?
  7. Okay I lied. The best way to keep track of 'pull' and other code progress is not any issue but the network page where all commits are shown. My favorite and most-used github/MaNGOS page by far. Hover over the commit points/balls/bullets/... to see each commit's comments and click it if you're interested in the code changes.
  8. The pull command is an on-going item (only started it a few weeks ago). Progress can be followed here, I'm generally (too) good at updating my progress. As you've discovered and stated, at this point there is no function in it for the end-user (or anyone, really). PBAI mounts is not my area of expertise. I could see flying mounts being a problem. E.g. on the flying mount bombing run quest you get shortly after getting the flying mount. Used to be a staple daily for me You would like to have them along (in case you get dismounted). Do they 'go missing' or just follow you slowly on the ground. If the latter I would consider that a problem since they would go around aggroing tons of mobs. Anyway, log an issue on github and hopefully Blueboy will find some time for it eventually or I'll cave and take a look at it. My bots are level 14 parked before RFC until pull is working so level 70 (or did they change it to 60?) is still far off for me to get annoyed by it As for the huntress - log an issue and one of us will get around to it. If hunters really aren't working that's a big issue, but as I recall I myself couldn't reproduce this bug. Anyway, log an issue and we'll see.
  9. Glad you got talent spec working. Meanwhile blueboy's pushed his fix to the new-ai branch so the combat orders should be working as well.
  10. FULL is basically a reinstall. You'll be 100% certain it's right but you'll lose any saved settings (PBAI DB only) and any modifications you may have made to the DB structure. Combat orders have been fixed but not pushed. See this issue. Talents do not, of course, get magically reset if you use the character as a player bot. There might be a command to do so if you're near a trainer (see "help talent"). If talents have been set that aren't in the talent spec you've chosen, that could be causing issues. I don't recall how I coded it but that certainly raises a flag. At least I made it so that doesn't crash the server
  11. There's no need for you to check out a getspec function, I meant that internally it should get the spec dynamically from the way your bot's talent tree is built rather than check it's talent spec (which may or may not be set; not in your case). In other words, the internal workings were designed specifically to rely on information always present rather than the (possibly un-)set 'talent spec'. Long winded way of saying "don't worry, be happy". I think the manual way to add talents is "[whisper] talent add (TALENT)" but just use "help talent" to get a full explanation. If that is the (sub)command and you require it, "help talent add" may give an even more detailed explanation. Really? When I look I see two files related to r6: https://github.com/blueboy/portal/tree/new-ai/sql/playerbotai Okay, they weren't there and I was the culprit. Apparently 'git commit -a -m "comment"' does automatically add changed files, does automatically remove deleted files, but does not automatically add new files. My bad.
  12. The combat orders command appears to be broken. It does look like you used it correctly. I've made an issue for it. Manually applying talents is just fine. The GetSpec() function was intentionally designed to allow for this eventuality. The only difference is more micro-management but some people have the knowledge and desire to manually talent all their bots. Go ahead and avoid 'talent spec' in this case. The latest PBAI is required_6, but that shouldn't account for the symptoms you're having. In all likelihood.
  13. Yea, that's not the command. Try 'help' if you're stuck, or in this specific case 'help orders'. The correct command is thus '[whisper] orders combat tank'. As for the bots inventory, I believe starting a trade is the easiest way. Eating/Drinking is very dysfunctional right now and as such I have opened an issue for this. I should really put this on the wiki instead (or certainly not in anonymous post #49), but here's a quickstart tutorial as to how I use my playerbot party: // Macro1 - logon /s .bot add Beefcake /s .bot add Celestius /s .bot add Succubus /s .bot add Healbot // Macro2 - group invite, combat orders - right after logon - give them a second to log on /invite Beefcake /invite Celestius /invite Succubus /invite Healbot /w Beefcake orders combat tank /w Celestius orders combat assist Beefcake /w Succubus orders combat assist Beefcake /w Healbot orders combat heal // Macro3 - talent specs - right after combat orders /w Beefcake talent spec 9 /w Celestius talent spec 8 /w Succubus talent spec 5 /w Healbot talent spec 3 // Macro4 - logoff - in case you want to do it explicitly for some reason /s .bot remove Beefcake /s .bot remove Celestius /s .bot remove Succubus /s .bot remove Healbot // Macro Utility - quest /p quest // Macro Utility - quest report /p quest report I also have a 'tank attack' and 'party attack' macro in case I don't want to pull. Hope to soon have a 'tank pull' replacing the tank attack This is not a cure-all, just my most frequently used commands (put into macros for ease-of-frequent-use). Don't forget the "help" command and that it also works as "help command". @Edit 2: bots should drink when under 30% mana, but again, it's bugged and drinking will only last a few seconds.
  14. I did a test (admittedly a short one - 10 minutes or so) with a hunter and saw no problems. The hunter was always in melee attack posture but correctly shot arrows while out-of-range and never moved to within melee range but did switch to melee when he pulled aggro off of me and the mobs moved out of his ranged range into his melee range. Again, this is the WotLK new-ai branch. Frankly portalone has it's own forum here and should be discussed in said topic.
×
×
  • 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