Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Smegzor

  1. 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.
  2. Thanks! 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 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
  3. 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).
  4. Alloc has released an update to his mod for compatibility with A19.5 so I have released an update to my Botman mod since it includes Alloc's mod. The updated zip is here https://www.botman.nz/Botman_Mods_A19.zip
  5. I have released an updated Botman mod (2.3.13) which has been built against A19.5 If you are still running 19.4 you should instead use https://www.botman.nz/Botman_Mods_A194.zip or do nothing if you already have it. The updated version for 19.5 is on the same url and zip I have used throughout A19 which is https://www.botman.nz/Botman_Mods_A19.zip Also it is using the latest release of 0harmony.dll which is version 2.0.4 released on Oct 31, 2020
  6. I have released Botman mod 2.3.12 which fixes bm-lcbprefabrule so it accepts the distance option now. I also built it using current versions of game dlls instead of the older A19 versions. I don't know if using the newer dlls will make a difference but it won't do any harm either. https://botman.nz/Botman_Mods_A19.zip
  7. I have released Botman mod 2.3.11 which fixes the console command bm-rules color. https://botman.nz/Botman_Mods_A19.zip
  8. I have released Botman Mod 2.3.10 If you already have the testing version, you do not need to replace it with this version. https://botman.nz/Botman_Mods_A19.zip It fixes (so far anyway) ongoing issues with resets not happening. Also there is a new item, the botmanVoteCrate which is an item that is spawned directly into player inventory instead of hopefully spawning beside the player. It contains the normal air drop crate with random loots inside. Big thanks to Pipedream for creating the botmanVoteCrate! To tell your bot to use this item as your server's vote reward use the command /set server vote reward item botmanVoteCrate
  9. A very minor bot update has been released. It mainly fixes 2 issues, the /give {player] item command messed up if you used the steam id or game id, and the command /set server vote reward item command rejected all items as invalid. More updates will follow soon. This update is mainly about getting updates moving out again. An experimental update to the Botman mod is also available for testing (link in the Botmanhosting Discord group). I am not releasing it generally yet as it may need more work. It is an attempt to fix the issue of resets not happening. It also adds a special new item, the botmanVoteCrate which is an item not an entity so that the server vote reward can be given directly to players instead of getting blown up by turrets or otherwise lost in the ground or wherever they vanish off to.
  10. New bot update released! Note: This is NOT a Botman mod update and most/all bots should automatically get it. You can force it to with /update code Here is the changelog.. New variation added to /trader protect. Here's the updated command help. /trader protect/unprotect/remove {named area} /trader add/trader del {named area} /trader protect/unprotect north/south/east/west/ne/nw/se/sw length/long {number} width/wide {number} After marking out a named area with the /mark command, you can add or remove trader protection on it. When used with a compass direction you do not need to mark out the area first. Your current position is used instead. Also when a compass direction is used, do not give the area a name as it is not recorded. You can repeat the command by simply typing / The new part is the ability to specify a compass direction and width and length. If you only supply width or length the missing value gets the value you did provide eg. width. The old version of this command is still there and unchanged. The new variant works differently, not using markings or a name. A very simple way to use the new variant would be /trader add width 20 That will trader protect an area with you at its center and 20 blocks in all directions (but a square not a circle) So you'd get a 40 x 40 trader protected area with that. If you want to do that on a rectangular area add length (or long). The command accepts various ways of saying the same stuff and even accepts a typo, dell = del. It won't try to sell you a computer I promise. Other ways you can use the command.. /trader add nw wide 20 long 50 (note that width is ALWAYS east - west and length is ALWAYS north - south) if you want to unprotect an area and don't care to be precise about it, stand more or less in the middle of the protected area and type /trader del width 100. That will unprotect 100 blocks in all directions for a total of 200 x 200 You can also protect an area north, south, east or west of your current position. If you do for example, /trader add north wide 20 long 20 it will actually protect an area 20 to the west and 20 to the east and 20 north of you giving you an area 40 x 20. If you want it to be square set the width to 10 to get 20 x 20. It is the same for the other compass directions but not nw, ne, sw, se which won't double any number on you. The reason why I double one side is because I put you in the middle of that side and decided against doing division. Instead I am giving you some math homework Also once you have used this command, if you need to apply the same command to another area (eg you are wanting to protect a HUGE area) simply move to another spot and type / (or whatever your bot is using for commands) Unlike the dig and fill commands you can't currently turn this command around by typing for example / south If you didn't know the dig and fill commands could do that, now you know ^^
  11. Someone recently ordered a bot from me but the email is not valid so I am unable to reach them directly. In the interests of keeping things anonymous if you ordered a bot and do not have it yet, please contact me directly at smegzor@gmail.com or via Discord where I am smegzor#9806 Your server appears to be offline as well which prevents me from completing your bot. If I am unable to complete your order after 1 week I will refund it and cancel your order. To everyone else, if you order a bot from me please make sure the email address is correct and where possible provide 1 alternative contact (Steam or Discord). I don't mind fake details in other parts of the order but if you cannot be contacted or invoiced and subsequently don't pay future invoices I will cancel your bot after multiple attempts to contact you any way I can. Fake info can also make it impossible to contact you in the event that your server needs something (mods, telnet enabled etc).
  12. um.. what does payment have to do with help? I never use that as a barrier to assistance. To answer the other question, the bot requires a linux desktop to run due to the engine it runs on top of being a GUI application. While that app also runs on Windows and OSX, the bot uses a number of utilities on Linux that don't really have Windows equivalents and I wouldn't know about OSX. The easiest way to get the bot is to rent it from me. While yes that has a small cost, it saves you the considerable fuss and bother of setting up the environment that the bot requires plus you have me maintaining the bot, an active community on Discord + myself to turn to for help and advice. At some stage I would like to try making a Docker container for people who want to self host the bot as it would have an almost ready to run bot (just needing configuration setup for your server).
  13. I have released an important bugfix update to the bot. Here is the changelog.. Fixed bug in reset bot that prevented it resetting player records. Fixed double up of in game chat echoed to the lounge when chat from a non-player is seen that isn't from the bot. It was mainly the failure of /reset bot resetting players that I HAD to fix NAOW. It broke because I added a call to bm-resetregions clear and for whatever reason that call prevented the rest of the reset code executing. I fixed it by moving that call to the end. The other fix is really just a cosmetic fix for the lounge.
  14. The bot host that was knocked offline by a faulty switch is back and all bots should be running again. Sorry for the long wait as the replacement had to be flown in from another city overnight. A backup switch is being wired in so that there is redundancy there should this happen again.
  15. One of my bot hosts is experiencing a rare outage atm. The cause is as yet unknown and I have notified my host. Sorry for the inconvenience if your bot is among those effected. My other hosts are still operational.
  16. The Botman terms of service have been updated.. https://botmanhosting.com/tos.html I added part 6 to the refund policy and removed the word full from all mentions of refunds and added (see part 6).. Part 6. We will deduct the Paypal fee from your refund if you cancel within 72 hours. Our deduction will not exceed the fee that Paypal charged us when we received your payment. For most people this change doesn't mean you won't get a full refund of unused months if you cancel early. I plan to refund unused months in full. This change is to address the situation where someone orders then cancels immediately (or up to 3 days after ordering) and the only change is I will no longer eat the Paypal fee on that lost payment. Today that happened and I refunded in full which cost me $2 USD. I have cleared the new terms with Paypal who said so long as I don't exceed their fee I can do that.
  17. I have released a bot update to the a18 and a19 code branches that fixes some bugs. Here is the changelog.. Fixed a timestamp bug. The bot was getting the correct server timestamp but then was adding to it wrongly. Now it just grabs it from the server a lot and doesn't try to calculate it. Added an extra check before initialising a player as new. If the bot started less than 2 minutes ago, it will try to load the player record and will exit the rest of the code. That should give the bot time to get the player record loaded before it tries to check for it. If the player record doesn't exist, the bot will carry on an initialise the player as new after the bot has been running longer than 2 minutes. Resetting the bot now also clears all reset regions from the Botman mod (live map). Template and invisible zombies should be automatically removed from gimme zombies and otherEntities lists.
  18. This should be obvious but I am not the Server Tools dev so while I am happy that you figured out your issue with the Server Tools xml you are grumbling about it in the wrong thread. Also hand editing XML files only works if you edit it correctly according to the software that reads it. It won't be able to process it if your editing isn't spot on with what it expects. I have no idea if Server Tools provides commands to set those things without resorting to hand editing XML but I expect it does. I don't think the descriptions in my XML file are bogus or misleading. You are not supposed to edit it by hand and as above if you do and get it wrong it won't parse correctly.
  19. For milestones, how are you adding them? I added a test one using the console command.. bm-milestones add 2 "Woo! level 2!" drinkJarBeer 1 Now my config has this line.. <milestone lvl="2" message="Woo! level 2!" reward="drinkJarBeer" quantity="1" quality="1" /> I notice your config looks different. Are you editing it by hand? Use the console commands provided to ensure that the config is correct. One of your lines.. <milestone lvl="25" message="[playername] has reached [25]!! It has Begun! Mortal Kombat! LOL" item="casinoCoin" quantity="2500" /> Notice that mine says reward= while yours says item= and you are missing quality. Your line corrected.. bm-milestones add 25 "[playername] has reached [25]!! It has Begun! Mortal Kombat! LOL" casinoCoin 2500 1 ~Botman~ Added level 25 to milestones with message [playername] has reached [25]!! It has Begun! Mortal Kombat! LOL. casinoCoin 2500 1 Now in my config I see.. <Milestones> <milestone lvl="2" message="Woo! level 2!" reward="drinkJarBeer" quantity="1" quality="1" /> <milestone lvl="25" message="[playername] has reached [25]!! It has Begun! Mortal Kombat! LOL" reward="casinoCoin" quantity="2500" quality="1" /> </Milestones> For the zones thing I did this in game.. I stood where I wanted 1 corner of the zone to start and type the console command bm-sanctuary p1 Then I moved a distance away making sure there was a zombie in the zone and completed it with the console command bm-sanctuary p2 test The zombie immediately got despawned. My config now has.. <Zones> <zone name="test" corner1="-1751, 58, -912" corner2="-1696, 67, -888" /> </Zones>
  20. I can see your zones have bad coordinates. It looks like you are using regions like -2,1 but the zones want world coordinates like you get if you are in game and type lp in the console. eg -2173,35,500 not 1,2,3 For Server Tools I expect it will be the same issue, use real world coordinates not regions.
  21. Merry Christmas everyone! =D Don't forget, one day only there is the special command /santa. One use per player. This year I added a little extra Christmas chair.
  22. Last night a router died which knocked 55 hosted bots offline. The router was replaced early this morning and all bots are back online. Sorry for any inconvenience caused. The router was in a data centre an hours drive away from my host so it wasn't exactly a quick fix but I was expecting the downtime to be hours longer than it was so all good.
  23. I have released a bot update with more changes to stop the bot switching from API mode to telnet mode when it shouldn't. Here is the changelog.. Added gimme prizes and gimme zombies to the backup and added the ability to only import zombies or prizes from the backup. Changed some stuff in the reconnect timer so that the bot won't switch from API mode to telnet mode so quickly and also blocked it from doing so if the bot is not connected or the server is starting up.
  24. I have released a new bot update. It adds a new debug log to the daily logs and I have it logging the 6 places in the bot where it switches from api mode to telnet mode so I can identify exactly which code is responsible for regularly switching out of api mode and then work out why it is triggering and how to code it to not trigger unless it really needs to. I have also restored 2 lines of code in the /fix gimme command that makes the bot completely forget all of the gimme zombies and regenerate the list from the server. That was necessary because the table of zombies uses entity id as the key field so it was not able to correct issues where entity id was wrong.
  25. I have released a small bot update in an attempt to fix the issue where the bot will switch from API mode to telnet mode when it doesn't need to. I will monitor several bots over the next couple of days to see if any of them switch out of API mode. If that happens there are a couple of things I can do to establish exactly where in the bot's code it is doing that and I can add more code to prevent it happening.
  • Create New...