![]() |
![]() |
der.zoomer |
![]()
Post
#1
|
Member ![]() ![]() Group: Members Posts: 35 Joined: 7-November 09 Member No.: 1,738 ![]() |
Hej there, I've been around here for a time as guest, and I really like RC Bot2 for TF2.
It works like a charm (most of the time tho...) And to improve this bot, I have some suggestions here: Arena Mode: - Bot check time until capture point is available else they would all rush to the capture point and stand there - on my dedicated server (same binaries) they dont seem to capture points, even theyre doing it on a listen server with SAME waypoints and scripts Snipers: - make them sound sensitive to visible players again, they just stand on their sniper pathnodes and dont move/shoot even if there are enemy guys all over the place Soldier: - he shouldn't use his shot gun so often Heavy: - fix this god damn heavy aiming, the heavy has like 0 recoil and can hit a target with 100% accuracy (every bullet hits, even if the minigun has a large spread fire cone) - heavy should check for distance to the nearest enemy (needs testing, because there are classes that you should take out in favour of others) Spy: - spies should try to melee attack enemies from behind with knife when possible - when spies try to cap (CP, CTF, PL) they should remove their disguise Medic: - make medics heal more, than attacking, make them sensitive to "call for a medic" event and let them stick with this guys as soon as he is healed or even buffed - let medics use their ubercharge when their current healing target is being attacked: event player_hurt waypointing: - let bots check for visibility between path nodes on calculating paths to the target ie. when a door is closed, this path is blocked and they'll choose another path or another target could be a problem with doors where you can see thru though... but that will eventually render setarea and givetype areaonly useless. (needs testing, because of defense points/sentry points/teleporter exit points) this is implemented by using the "givetype openslater" waypoint type, but bots can see through EVERY door! (even though they are closed) so it doesn't work, an engine bug maybe - a waypoint type for an alternate route would be nice, so the bots dont attack only by one path, maybe with priorities, so 1 is main path, 2 a good alternative and 3 an alternative, but less good than 2 or even 1 but possible.... I've implemented "route" waypoint types for next version, they are simple additions, so we'll see how they do after a lot of testing Misc: - gravity seem not to affect bots, they jump and fall like 4x faster than usual players this is an engine bug - when bots see a dispenser (and need supplies) they should use it this is implemented but happens rarely nice to have: - bot and equipment support (use hats, other inventory you usually earn with achievements/find items) - bot should learn how real players move around in that map |
![]() ![]() |
Root |
![]()
Post
#2
|
Member ![]() ![]() Group: Members Posts: 24 Joined: 20-July 13 Member No.: 2,291 ![]() |
Thanks for the tip about profiles!
I've changed both aimskill and visionticks. Seems like bots are react way faster than in previously, and they finally won a few rounds on dod_donner map, even when capturing last CP is hard. CPU usage was really increased! I guess its caused by visionticks. So I changed it to 73 and its working like a charm on full 32 slot server. Bots are working so far, but I found noticeable lag: On dod_jagd map (when axis are running out of spawn area and picking explosives automatically) server is having lag spikes until bots leaves dod_bomb_dispencer area. I have no idea why this is happening (maybe increased aimskill or visionticks or even amount of bots at all?). If RCBot is using any hook to check whether or not bot is having a TNT, I'd recommend to disable it at all. There are no better way to check TNT than checking 4th slot in player's inventory (next after grenade one). ![]() |
Cheeseh |
![]()
Post
#3
|
![]() Admin ![]() ![]() ![]() ![]() ![]() Group: Admin Posts: 3,066 Joined: 11-September 03 From: uk Member No.: 1 ![]() |
Thanks for the tip about profiles! I've changed both aimskill and visionticks. Seems like bots are react way faster than in previously, and they finally won a few rounds on dod_donner map, even when capturing last CP is hard. CPU usage was really increased! I guess its caused by visionticks. So I changed it to 73 and its working like a charm on full 32 slot server. Bots are working so far, but I found noticeable lag: On dod_jagd map (when axis are running out of spawn area and picking explosives automatically) server is having lag spikes until bots leaves dod_bomb_dispencer area. I have no idea why this is happening (maybe increased aimskill or visionticks or even amount of bots at all?). If RCBot is using any hook to check whether or not bot is having a TNT, I'd recommend to disable it at all. There are no better way to check TNT than checking 4th slot in player's inventory (next after grenade one). ![]() the bots check if they have tnt by checking the weapons they have, it's pretty quick |
![]() ![]() |
![]() |
Lo-Fi Version | Time is now: 20th August 2024 - 07:53 PM |