apgrobocop / foxbot Goto Github PK

Hi, sorry for submitting this issue on the foxbot, the rcbot2 repo just doesn't have an issues section.

Players "0" => Bots "2"
Players "1" => Bots "1"
Players "2" => Bots "0"
.. and so on ..

Will still add like 8-9 bots on the server. Can you please check? Thanks!

This is not an issue but a doubt. Foxbot doesn't have any issues with VAC?

It will crash after tens of minutes of operation

The latest Foxbot crashes the Windows dedicated server (via SteamCMD) shortly after a player joins a team. Spectator mode seems okay.

I was just wondering if a waypoint menu, similar to the latest sturmbot, or all versions of pod bot including yapb have, this would make waypointing for unsupported maps a breeze and would honestly make this mod much nicer to use, in fact, a vgui menu system in general would be fantastic here.

getting quite a bit of this when starting or changing map, was fine with 0.77

L 09/30/2020 - 17:16:41: [META] ERROR: Plugin didn't set meta_result: foxbot_mm.dll:RegUserMsg_Post()

let me know if you need more info

How to install a new version ? FoxBot 0.793-beta

The maxplayers on the server is 24, I set a max of 23 bots to spawn. 23 bots + me, there should be 12 players on each team, but there's only 11 on my team. Is this a bug or am I doing something wrong?

settings arent working, settings like allowing bots to chat dont seem to work at all for some reason

The latest Foxbot 0.792 release is extremely unstable. There's a note about it crashing listen servers, it crashes ALL servers, no matter if dedicated or listen, Linux or Windows.

I can't get my server to run more than 30 seconds or so before foxbot_mm.dll / foxbot.so causes the server to crash.

Tested with both official and unofficial maps in both version 0.793 and 0.801 of Foxbot, watching bots as a spectator.

In the latest version, bots always tend to wander around rather than prioritize capturing the flags they carry. However, in 0.793 they work fine and often go straight to capturing as they should.

In the game, the bot kills a spy, even when he's in disguise.

bot_use_grenades - # 1 = Concussion jumping is allowed. - bots still use all grenades

defensive_chatter -
offensive_chatter -

not sure which one but setting both to 0 I still get chat regarding sentry down

I'm not back, but soon will be! ;) ,Ive been running a few dedicated servers for practice and getting the feel again for bunny hopping etc, but i cant seem to get any version of the current available foxbot to run without crashing server on windows 64bit.

Any ideas?

Cheer fella, btw i asked Pizza and he had no idea also :P

Hello. Thank's for making the best bots for TFC.

1. Near the Church where the Demoman should destroy the passage to the Church (on the waypoint bomb) bots are always stuck and sit there until the map changes or until it is killed. Can you imagine what will happen if the bot stucks there with a flag? Yes, it happened many times.
2. Medics hardly ever heal teammates, even if you call them.
   Sorry for my bad English

Noticing bots will grab the flag and hold it until they die in 0.801 beta1.

Can I get a link to a new version of the bot?

The commanders feature doesn't work on RV (Linux server), unless I downgrade the binary to 0.791.
The bug applies to all versions from 0.792 to 0.801.
Maybe someone else could confirm, to make sure it's not an RV specific issue.

Bug description:
FoxBot loads the commanders fine, they are logged.
When trying to give a command, access is denied.

Work-around:
Downgrade (the binary) to FoxBot 0.791.

I can only play well or BEYEUX for a certain time before the game decides to CTD, these sessions usually last around five minutes, with any amount of bots on either team.

Thank you for the new patch !

Foxbot used to better support NeoTF, but somewhere after the last official 0.701 build, it was mostly broken. Foxbot didn't support all NeoTF features to begin with, but it used to support more features than it does now.

Engineers in 0.701 used to occasionally build multiguns, and team bots would actively seek them out to upgrade them, enemy bots would also try to destroy or capture them if they weren't upgraded. Currently 0.8xx, the bots almost entirely ignore them and will be mowed down in perpetuity. The only class that will try to do anything with them is Snipers. Snipers will attack any multigun, regardless if it is enemy or friendly. This is a problem because multiguns are damaged by friendly fire and can't be repaired.

Medics used to both spawn medpods and snarks. Now they only spawn medpods. Medics also used to try and upgrade dispensers to medic dispensers by touching them, now it's just chance whether a medic touches it by accident.

Pyros used to use freeze spray, now they don't at all.

The other classes don't use any of the NeoTF features as far as I'm aware. The Spy will inadvertently use aqualung if it is enabled.

I've recently updated from AMXX v1.10 build 5406 to build 5414 because they did some "connect" related bug fixes. But this bug fix (or something they did in the versions in between) seems to be incompatible with FoxBot, and the dev says it's a bot issue, not an AMXX one.

They're making a work-around for it, but still if this is a bug in FoxBot, might be worth looking into it.

alliedmodders/amxmodx#938

The latest update seems to break the ability of bots being added automatically without needing to manually type "addbot" or adding it into the config file. Adding it into the issues so it can be tracked.

Thank you for FoxBot 0.800-beta2

In version 0.801-beta1 I noticed a bot entering respawn while infected and repeatedly going back to respawn to collect med packs. At one point the bot was just sitting on the med pack while infected not moving, infecting spawned players of course.

then we gotta focus on 0.791
and i might have found something interesting regarding that
Syntax error, unrecognised command

on_start
{
blue_attack
red_attack
blue_available_only_point3
red_available_only_point1
}
on_msg(RED SECURITY IS DOWN

ACCESS TO RED FLAG IS AVAILABLE!)
{
blue_available_only_point4
}
on_msg(BLUE SECURITY IS DOWN

ACCESS TO BLUE FLAG IS AVAILABLE!)
{
red_available_only_point2
}
on_msg(RED FLAG ACCESS:

DENIED!)
{
blue_available_only_point3
}

on_msg(BLUE FLAG ACCESS:

DENIED!)
{
red_available_only_point1
}

on_msg(RED FLAG ACCESS:

10 SECONDS REMAINING...)
{
blue_available_point3
}

on_msg(BLUE FLAG ACCESS:

10 SECONDS REMAINING...)
{
red_available_point1
}
something here went wrong on 0.791 beta 2
it might be our hint to figuring out what's wrong with A/D and other maps that stopped working properly on 0.79

Reported by [APG]BLACKiE

Hi, i'm running the latest version of FoxBot and i've noticed that after playing a certain amount of time(1-15 minutes), the game crashes and i get this error: