Jump to content

ColColonCleaner

Plugin Developer
  • Content Count

    165
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by ColColonCleaner

  1. I looked at camos but I believe it was a mess categorizing them in a meaningful way in the json download from battlelog. There was some reason i didn't add that functionality but i don't remember why specifically.
  2. Keep in mind the plugin has no knowledge of where the player spawns, only that they spawned somewhere. The 'on kill' option is there for jets because if some random player goes about their business on the ground we don't want the plugin caring about their jet loadout. However, if a player spawns then kills with a jet, it will scrutinize their jet loadout until they change it. It classifies them as a jet player whenever they kill with the jet. There isn't really a way around this either because if you just admin kill a person when they kill with an invalid loadout in a jet, they just spawn in the jet again and kill with the invalid loadout again. Admin kills don't give deaths on player stats so there isn't a punishment there.
  3. Firstly, swapnuke is a VERY aggressive command, i'd take caution when using it. It also doesn't work when the server is full. In general all commands need a source, a target, and a message. so you should include those values. source could be insanelimits, target could be server, and message could be whatever you want to be logged. The protocol is mentioned here: https://github.com/AdKats/AdKats#issuecommand
  4. Not at this time, I've looked into it in the past but haven't made the time to add that support in.
  5. Check your tbl_server table, make sure it has an entry for this server.
  6. I am not planning to add any new features to LRT at this time.
  7. AdKats supports BFHL, LRT does not, they are separate plugins. Proconrulz should be fine on BFHL, it just operates based on the same events BF4 has.
  8. They killed several people with a radio beacon during a round, it's a rare script/hack but it is a thing.
  9. There are no events for shooting or locking on with missiles. Only spawning and killing. So there is no way to do this via the plugin or any other plugin without modifying the actual server code somehow.
  10. There is currently not a setting to control that. However, you could remove the following line from the plugin to stop that from displaying.
  11. You'll likely have a lot of issues running stat logger/adkats on illegal servers. I haven't tested anything on an illegal setup like that.
  12. I would expect procon running AdKats on a full 64 man server to take much more than 19MB of memory, up in the hundreds of MB is standard, where did you get that 19mb number from? (I'm not talking about your client, i'm talking about your procon layer, if you're running it that way.)
  13. Check your memory usage on procon.
  14. There is a password lock for AdKats settings if you want to use it lol
  15. There are also automatic settings for admins. Look for settings like 'Automatic spectator whitelist for admins'. You might have that enabled.
  16. Looks correct. Could you please screenshot the procon chat while a nuke is active? Make sure you can see the starting message, all the countdown messages, and the ending message.
  17. You probably changed the wrong setting, there are multiple nuke durations based on population. Please for all future questions provide screenshots of the settings and responses to commands.
  18. Ah you fixed it, great! Was it not allowed on your admin role?
  19. What role did you assign to your player? Are you full admin? are you a guest? did you make a custom role? You've set this up before. Use !isadmin to see what role your player is. What error message is displayed when you try to use !wnuke?
  20. 1. Fill the 'Short Server Name' setting. 2. Add that command to your player's role.
  21. Okay you're just making it more and more suspicious that what is running on your server and what's in procon are not the same thing. You have command confirmation bypass enabled, so you should not have seen that confirmation message asking you to say !yes.
  22. We know it's caused issues in the past, but something this random is weird. I'm not sure what it could be. I'm most baffled by the !help command working but nothing else.
  23. Wait, hedius is right, that setting that allows commands via procon chat is enabled in the screenshots you sent us. If that setting was enabled you shouldn't be getting that message. Are you actually sure you're looking at the right server? Do you have multiple servers?
  24. Are you sure you're looking at the right server? I have no explanation for why these things aren't working. Something changed on your side. Try this. Issue the command from the procon chat window. Does it work then? /wnuke
  25. Also, look through that command list and check if wnuke is in there.
×
×
  • Create New...

Important Information

Please review our Terms of Use and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.