MantisBT - Zandronum
View Issue Details
0004463Zandronum[All Projects] Bugpublic2025-02-25 05:322025-03-02 02:57
LacedCase 
 
lowminoralways
confirmedopen 
WindowsWindows 1124H2
3.1 
 
0004463: Bots Added via ACS Don't Respect BOTINFO Color (Always Default Green)
If you use the in-game console to "AddBot", the bot is spawned normally and is the correct color defined by BOTINFO.

If you use ConsoleCommand("Addbot"); inside an ACS script, the bot will spawn but always as a default light-green color and not respect the BOTINFO>SKININFO color.

I'm not sure if this is intentional or not, or if there is a flag/variable that is modifiable but I could not find any after pouring over the documentation for 3 days.

This was happening to me in 3.1 and the latest 3.2 build.

I have attempted to test the new AddBot(); ACS function introduced in 3.2 betas but I cannot get the ACS to compile correctly in Ultimate Doom Builder so I've given up trying to see what it does because whoever sees this ticket will probably be smarter than me and be able to test it.
This was happening to me in 3.1 and the latest 3.2 build.

-Start a local (or server) deathmatch game
-Make a map with a switch that runs a script that executes ConsoleCommand("Addbot"); and notice the green color of their skin
-Immediately afterwards, use the AddBot console command and notice their BOTINFO>SKININFO color

I attached a test wad that will help quickly diagnose. The left switch runs ConsoleCommand("Addbot") and the right switch would run AddBot(); but I had to comment it out because it wasn't compiling, but you'll probably be able to uncomment it and test it out.
I really only cared about this because of a mod I found that fills your empty server with a few bots if someone joins with no other humans playing. I would enjoy it better if the BOTINFO>SKININFO color was working so you didn't have a bunch of green bots running around making it feel cheesey.
No tags attached.
zip bot_test.zip (4,776) 2025-02-25 05:32
/tracker/file_download.php?file_id=3188&type=bug
png Screenshot 2025-02-25 003550.png (1,084,827) 2025-02-25 05:38
/tracker/file_download.php?file_id=3189&type=bug
png Screenshot 2025-02-25 003631.png (1,136,591) 2025-02-25 05:38
/tracker/file_download.php?file_id=3190&type=bug
Issue History
2025-02-25 05:32LacedCaseNew Issue
2025-02-25 05:32LacedCaseFile Added: bot_test.zip
2025-02-25 05:38LacedCaseFile Added: Screenshot 2025-02-25 003550.png
2025-02-25 05:38LacedCaseFile Added: Screenshot 2025-02-25 003631.png
2025-02-25 05:38LacedCaseNote Added: 0024215
2025-02-25 05:44LacedCaseNote Edited: 0024215bug_revision_view_page.php?bugnote_id=24215#r14466
2025-02-25 05:44LacedCaseNote Added: 0024216
2025-02-25 05:44LacedCaseNote Deleted: 0024216
2025-02-27 20:49unknownnaStatusnew => confirmed
2025-03-02 02:57DrinkyBirdNote Added: 0024222

Notes
(0024215)
LacedCase   
2025-02-25 05:38   
(edited on: 2025-02-25 05:44)
I added two screenshots. The first one shows a bunch of green bots added via ACS. The second screenshots shows a bunch of normal bots added via console. Thank you :)

(0024222)
DrinkyBird   
2025-03-02 02:57   
It is broken, but it works with the AddBot function.
ConsoleCommand has this issue because it basically sets the 'color' userinfo CVar of the bot player that gets created, but there are some restrictions on setting CVars in a ConsoleCommand context, which are interfering here.
Since the AddBot function doesn't run in a ConsoleCommand context the bot code can set this CVar successfully, so the solution is to use that.