Botman server manager official support thread

I have released Botman mod 2.3.14 which fixes the issue where ghost claims are left on Alloc's live map after the mod removes a placed claim. The updated zip is here.. https://www.botman.nz/Botman_Mods_A19.zip and will already be available in the mod installer pages of game hosts that have it (Pingperfect, Hosthavoc, Logic Servers, and Serverblend, maybe others too).

 
Is there any way to have the bot periodically giving info throughout gamedays? ie: ''Don't forget to /sethome before leaving your base!'' ''Did you know that we have a /lobby? Go see for yourself!''

I've been using Botman for roughly a month and am so in love with its features. Excellent job on it! 

 
check the complete list of commands here
https://botman.nz/all-bot-commands

Best bet is using the botman panel

https://panel.botman.nz/auth

 
Hi there, this is a shot in the dark, but I'm curious if you know how the current server time is translated into the readable format of "Day X HH:MM"?

I've  been trying to build a tool that lets me see what the current server time is, and so far I've been able to get the 'Current Server Time' from pinging the server, but it comes back as a number that i cant figure out how to translate it.

For example, im getting 90219 which apparently is supposed to be "Day 3, 18:13"

 
Is there any way to have the bot periodically giving info throughout gamedays? ie: ''Don't forget to /sethome before leaving your base!'' ''Did you know that we have a /lobby? Go see for yourself!''

I've been using Botman for roughly a month and am so in love with its features. Excellent job on it! 


Thanks! :D

The bot supports timed public announcements.  Currently these are set in the general section in the panel or  via The Lounge (IRC) as in game the bot will strip colour codes.  Also note that to use the panel as server owner you should be logging in with the other login button that has the text 'Login Admin Dashboard'.  Let me know if you do not have or know your admin login.  Ideally message me via Discord as I am far more likely to notice a message there than anywhere else since I monitor Discord many times daily.  I am smegzor#9806

Hi there, this is a shot in the dark, but I'm curious if you know how the current server time is translated into the readable format of "Day X HH:MM"?

I've  been trying to build a tool that lets me see what the current server time is, and so far I've been able to get the 'Current Server Time' from pinging the server, but it comes back as a number that i cant figure out how to translate it.

For example, im getting 90219 which apparently is supposed to be "Day 3, 18:13"


It sounds like you actually want the console command gt which stands for game time.  This is the output I get from it on my server..  Day 3, 10:08

 
I'm having a very hard time adding items to the server shop. I'm using "MyBotPanel" and I'm lost. The server is a Undead Legacy Mod. Is that why I can't add items? Please help! I've searched all day for a tutorial or something on it and have found nothing.

 
Alloc recently released an update so I have released an updated botman mods zip.  The new Alloc's mod is the only change today.   https://botman.nz/Botman_Mods_A19.zip There are several changes to his webmap which is now version 38.  If your Mod Allocs MapRendering and Webinterface is already version 38 you do not need this update.  You should also be able to grab it via your game host and won't need to download the zip unless that is how you update normally.

 
A20 arrives in a few days.  I am expecting that the bot will be compatible with A20.  The Pimps don't release new alphas to server managers for advance testing so I will only be able to test when it lands.  If there are any breaking changes (and it doesn't look like there are), it will only take me an hour or so to test and fix them.  For my timezone, I am usually awake just a few hours after release, but regardless any updates from me will be released the same day as A20 and not long after it.  I will also release the Botman mod for A20 as it will need to be built using the updated server dlls.  Initially I probably won't include Alloc's mod in the Botman mod as he typically updates when new alphas go stable.

A20 will be experimental on Monday and from their release notes you will need to do the following or have a ton of issues..  Alpha 20 is not compatible with previous Alpha worlds or save game data. New Pregen-Maps have been created and can be used. We also advise that you delete the 7 Days save Game data folder before playing.

So if you try to keep maps etc and stuff breaks constantly, the bot isn't responsible for those issues

 
I mostly post in my Botmanhosting Discord group 

https://discord.gg/MUaHTjJ

For anyone who doesn't look there, the Botman mod is not yet compatible with A20.  The bot isn't either but I am well through the work converting the code.  Already the bot is working on my dev server and I am mainly tracking down and converting anything missed in the main sweeps.

I think I am more than 80% finished and hope to have an A20 bot available for live testing today.

 
I have released the a20 bot to the a20testing code branch.  I have a few more bugs at the moment and you will need my help to update your bot.  After I have fixed the remaining bugs, the update process will run a lot smoother.  The main issue is the reset bot command isn't working properly so information from the previous world is sticking around.  I will fix that bug today along with a few other important bugs.  The bot is working on A20 but the Botman mod is not compatible yet.  I will work on updating that once these bot bugs are sorted as the bot will work perfectly fine with Alloc's mod and no Botman mod, but you will not be able to hide commands from the chat.

 
The conversion of the bot for compatibility with A20 is now complete.  If there are any bugs or bits missed in the conversion, they are most likely minor.  Currently all commands and features in the bot are working except for any that require the Botman mod as that has yet to be made compatible.  I will be starting that work in a day or two after I have mostly finished assisting people with updating their bot, and some new bots.

To update your bot to a20 you need to tell the bot to use the a20 code branch.  You can do that 3 ways. 

In game you can tell it /set update branch a20 then tell the bot /update code.

From the panel you can click on the dashboard, click on your server, then from the Server Setup dropdown, click on Bot Connection.  Edit the update branch to a20 and click Submit.

From The Lounge type cmd /set update branch a20, then type update code.

If you are unable to get your bot to update for some reason, or you encounter other issues such as not being able to reset the bot you can message me directly on Discord and I am happy to take a look at it for you.  I am smegzor#9806  If you join my Botmanhosting Discord group, you will not need to send me a friend request.

https://discord.gg/MUaHTjJ

 
I have released another bugfix update to the A20 bot which fixes several annoyances.  Here is a changelog from the last several bot updates..

Fixed bug in function that tells the bot who is an admin.
 

Changed command permissions on the various bot reset commands to allow them to be used from The Lounge.  Also improved the command feedback and changed the permissions of the /yes command to allow its use from The Lounge.

Resetting the bot is working again.

Fixed 'bug' that was preventing the bot's reboot countdowns and some other in game messages from being seen from The Lounge.

Extended the effects of the command '/set bot quiet' so that it also stops the bot giving pvp commentaries.

Added a new Easter Egg somewhere.

Fixed issue where the bot would fail to recognise that you are an admin when commanding the bot from The Lounge.

Removed an annoying automatic bot restart that would trigger after map corruption which caused the bot to restart itself endlessly.  On the plus side that fault confirmed that the bot can detect when Alloc's API is non-functional and the bot will automatically switch to telnet if available.

If the server reports a corrupt region file, the bot sends that information to the alerts channel in The Lounge.

Fixed an issue in the bot's core that would cause some broken in game commands due to wrongly cast numeric.

The bot is much better at processing the admin list regardless of Steam ID or EOS ID.  If an admin is recorded in the XML with only an EOS ID and the admin has never joined the server, they won't yet have a Steam ID.  In this case the bot records them but when asked who the admins are, it will only list admins that have a Steam ID recorded.

 
I have released a bugfix update to the A20 bot.  Here is the changelog..

Minor code changes to ensure the crossplatform id (which I call userID) is always present even if it is an empty string as it causes problems if it is completely missing since it is used everywhere.
 

Alloc's API currently does not include the crossplatform id so the bot sends the lp console command every minute as well as when the bot starts up to ensure that the bot has the id for all players currently on the server.
 

Fixed some potential faults in some of the lounge commands when data is missing that the bot tries to report on.
 

Fixed the claims command in The Lounge.
 

Fixed the lounge command list bases and also added a new variant, list bases {x} {z} range {distance} eg list bases -100 50 range 20.  It will list only the bases within the defined area.
 

Added a new lounge command 'whos' which is a much more compact version of the who command.  It just lists the steam id, name and crossplatform id of the players currently on the server.
 

Also added the new lounge command 'whom' which is a customisable version of the who command.  Here is it's command help.

whom
Custom who command help:
List players online right now and specify what you want included.
eg. whom level score zeds.
Game id, steam, name, and EOS id are always included.
To use, type whom followed by any of the following list..
group, rank, level, score, zombies, playerkills, deaths, region, ping, hacker, location, coords
 

Fixed an issue that caused the bot to fail to properly install the new scripts from bot updates.  
 

Fixed the code that records and reports when a player leaves the server.  It is properly reporting them to The Lounge again.
 

Fixed an issue in the chat command /claims.  It wasn't able to report any that had no known owner.
 

Fixed the /setbase command so that specifying a base number is honoured by the bot.  Now you can totally have a base number 7 even if you are only allowed 1 base.  This is mainly useful for filling holes in your list of bases if you delete one in the middle.

 
Back
Top