Jump to content
Smegzor

Botman server manager official support thread

Recommended Posts

I have released several small updates recently and have also updated the github repo so you can see what's new.

 

Here's the changelog..

 

Fixed map permissions which were too high.

Fixed typo in inventory scanner that prevented banning for certain items. It was sending players to timeout instead.

Added auto fix for when the IRC alerts channel and watch channel get accidentally swapped (happened in panel).

Added terrainFiller and terrainRemove to the bad items list set to ban if found in player inventory.  It is a favourite tool of hackers lately.

The bot now reads the anticheat report every minute as a fallback method to catch hackers if live reporting fails for some reason.

Bans were not being loaded into the lua table bans after reading bans from the server which caused disagreement between the bans table and the in-memory lua table.

Improved handling of the anticheat report when the bot reads it.  It wasn't catching them all.  Do not invite the bot to play Pokemon.

 

 

Share this post


Link to post
Share on other sites

I have updated the command help on the botman website.

 

To save you trying to guess what's changed, here are all of the changes..

 

/set map colour FF0000 (red is the default colour)
Set the colour of reset regions on Alloc's web map.
Restricted to owners and admins in-game and IRC
 

/enable/disable anticheat
Enable or disable the anticheat feature in the Botman mod.  Default is disabled.
Restricted to server owners in-game and IRC
 

/enable/disable mapping
Enable or disable plotting reset regions on Alloc's web map.
Restricted to server owners in-game and IRC
 

/make maze (default maze 20 x 20)
/make maze wall {block name} fill {air block} width {number} length {number} height {number} x {x coord} y {y coord} z {z coord}
The bot also accepts wide, long, and tall instead of width, length, and height.
The maze will generate with no roof.  If you want a roof add the word roof.
If you want a multi-level maze add levels {number}. Note: it will include a floor.
You will need to cut holes or make rooms yourself.
Generate and build a random maze.  Someone must stay there until the maze completes or it will fail to spawn fully.
Default values: wall steelBlock fill air width 20 length 20 height 3. It uses your current position for x, y and z if not given.
Note: width and length are multiplied by 2.
Restricted to owners, admins and mods in-game only
 

/enable (or /disable) pvp visit (default disabled)
Normally players cannot visit friends in pvp. They can if you enable this.
Restricted to owners, admins and mods in-game and IRC
 

/set p2p access {access level}
Restrict the /visit command to players at and above a bot access level.
Levels are 99 (everyone), 90 (everyone except new players), 10 (donors), 2 (mods), 1 (admins), 0 (owners).
Restricted to server owners in-game and IRC
 

/enable/disable linked waypoints (default enabled)
If disabled, players will not be able to link waypoints.  Also any non-admin existing linked waypoints will be unlinked.
Restricted to owners and admins in-game and IRC
 

/enable/disable waypoints
Donors will be able to create, use and share waypoints.  To enable them for other players, set waypoints public.
Restricted to server owners in-game and IRC
 

/enable/disable bot colours (default enabled)
If you want something else managing chat colours you can stop the bot replacing them by disabling that feature with this command.
Restricted to server owners in-game and IRC
 

/set pvp temp ban {minutes}
Set how long to temporarily ban a player after a pvp kill.
This is only used in PVE when there is no prison location.
Restricted to owners and admins in-game and IRC
 

/setup map
Optional extras after setup map: no hostiles, no animals, show players, show claims, show inventory
eg. /setup map no hostiles no animals show players show claims show inventory
The bot can fix your server map's permissions with some nice settings.  If you use this command, the following permissions are set:
web.map 2000
webapi.getlandclaims 1000
webapi.viewallplayers 2
webapi.viewallclaims 2
webapi.getplayerinventory 2
webapi.getplayerslocation 2
webapi.getplayersOnline 1000
webapi.getstats 1000
webapi.gethostilelocation 2000
webapi.getanimalslocation 2000
If setting no hostiles and/or no animals:
webapi.gethostilelocation 2
webapi.getanimalslocation 2
If setting show players, show claims, show inventory:
webapi.viewallplayers 1000
webapi.viewallclaims 1000
webapi.getplayerinventory 1000
Restricted to server owners in-game and IRC

 

Share this post


Link to post
Share on other sites

I have released a bugfix update that fixes a bug where the bot would sometimes spawn traders or other wrong entities.  This had previously been fixed but there were still 2 occasions where that fix wasn't being applied.  It could spawn wrong for some gimme prizes and for the admin command /hordeme.

 

To test it I had it randomly select 20,000 entities and sorted that in Excel.  I was able to confirm that it was not selecting traders and other entities that are flagged as do not spawn or that were not even on the bot's zombie entities list.

 

Share this post


Link to post
Share on other sites

SWEET!  The bot finally supports international characters (foreign stuffs) in chat to and from IRC and will also display foreign hen scratchings in game correctly.  I won't be able to read it but that's tough xD  Beforehand it was a bunch of garbage anyway so its an improvement! :D

 

It requires the latest Mudlet and must be set to UTF8.  I am in the process of upgrading all hosted bots.

Share this post


Link to post
Share on other sites
Posted (edited)

The bot is working on A19.  I currently get an error from Alloc's web map and his map isn't working, but bot chat works and ingame commands work.  I have a lot of testing to do but I am able to teleport so yay!  To get the bot working I did have to restart it.  Other than that I have temporarily removed the harmony dll from the managed folder and the only mod I have is Alloc's mod for A19

 

I am waiting on an updated Botman mod and I have messaged Alloc with the error I am getting from his map.  Hopefully I'll be able to release an A19 mods zip later today.

 

Looking promising so far.

 

Oh yeah forgot, since Alloc's map is erroring and the API is also the map, I had to tell the bot to use telnet.  I did that via IRC with the command use telnet.  You can also do that via the panel if you have that. 

 

For the impatient the latest Alloc's mod can be downloaded here  http://illy.bz/fi/7dtd/server_fixes.tar.gz

Edited by Smegzor (see edit history)

Share this post


Link to post
Share on other sites
Posted (edited)

I have created an a19 code branch.  I am currently fixing stuff.  So far I have found that the admin list console command output has changed and the bot isn't reading it successfully atm.  Fixing that now.

 

I have already updated the new a19 code branch with its first fixes.

The bot correctly parses admin list again and also if Allocs mod produces the error I am seeing atm, the bot switches automatically from API mode to telnet mode.

Edited by Smegzor (see edit history)

Share this post


Link to post
Share on other sites
Posted (edited)

Thanks to SylenThunder I now have a working copy of Allocs mod.  I have created a zip for the A19 Botman mods which currently does not include the updated Botman mod 😮 but that will change as soon as I have it myself.  The new zip is here  https://botman.nz/Botman_Mods_A19.zip

 

The map is working again which means the bot can be in API mode again.  If yours is in telnet mode you can switch it by typing /use api or on IRC just type use api, or on the panel just switch it over.  The panel rocks! ^^

 

I have released a dummy update for a18 that checks the version of the server.  If it is 19 the bot switches to the a19 code branch.  A second update will be required to actually install the a19 code.  That happens automatically but might not happen early.  You can force it by typing update code.

Edited by Smegzor (see edit history)

Share this post


Link to post
Share on other sites

I have updated the Botman mods zip for A19 (see link above).  It now has the Botman mod back, fully working in A19.  The extra dll, 0harmony.dll works too.  That goes in a different folder (in managed).

 

Enjoy! ^^

Share this post


Link to post
Share on other sites

Hi guys!

 

I have released an important update to the a19 code branch and I am preparing to backport some of it to the a18 branch.  It fixes issues with the shop and also massively boosts bot performance when starting up, fixing the shop or doing any shop maintenance or use of the shop.  This is a significant improvement as it completely removes a major performance bottleneck that occurred when the bot read and then processed all items known to the server.  It no longer saves or reads them to/from the database.  It was using a memory table but it caused the bot to 'freeze' for several minutes.  Now there is no observable delay at all. WIN!

Share this post


Link to post
Share on other sites

I have updated the A19 Botman mods zip with important bug fixes.  Please update your Botman mod dll.  It fixes issues with some of the prefab commands such as resetting a prefab and fixes some default values for a few settings.  The fixed Botman mod is version 2.1  If you have 2.0 you need this update.

 

I have contacted a few game hosts so they can update it in their mod managers.  They are Pingperfect, Hosthavoc and LogicServers.  They should have the update available soon.

 

https://botman.nz/Botman_Mods_A19.zip

Share this post


Link to post
Share on other sites

I have released a bugfix update to the a18 and a19 code branches.  There was a minor issue with a 1 block wide line at 0,0 both north-south and east-west that was excluded when north of 0,0 is different pvp/pve rules from south of 0,0  (just one example).  Now that 1 block line is included with north of 0,0 and excluded from south (and included east but excluded west).

 

Another bug fix concerned some cooldown timers on locations.  It was reporting crazy long cooldowns to players when the real cooldown was 30 minutes or some other delay that definitely wasn't 18 hours for example.  Now it is reporting correctly.  The actual cooldown was working properly.  This was just a display bug which was causing some players to ragequit.

Share this post


Link to post
Share on other sites

I have released a bugfix update to the a18 and a19 code branches which should fix a desync issue that has been reported between the panel and the bot.  I confirmed that I fixed it for donor waypoints being set via the panel and I found about 4-5 other things that were potentially effected by the same issue and applied the same fix to them.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...