1. hey guys, its not working and guys with 2 or 3 vac bans can join us with this plugin... please fix and update this version, thanks.
     
  2. I set the amount of VAC bans allowed to zero in the config and now even people without a VAC ban can't join.
    I set it back to 1 and people can join again but I am afraid people with 1 VAC ban also can join.. The plugin seems to be bugged.
     
  3. Does this allow family share accounts? Otherwise it would allow VAC banned people to just make a family share account and join the server, right?
     
  4. fix please
    Code:
    (00:02:47) | [Oxide] 00:02 [Error] Failed to call hook 'OnUserApprove' on plugin 'VACKicker v1.0.0' (NullReferenceException: Object reference not set to an instance of an object)
    (00:02:47) | [Oxide] 00:02 [Debug]   at Oxide.Core.Event`2[T1,T2].Add (System.Action`2 callback) [0x00000] in <filename unknown>:0
      at Oxide.Core.Libraries.WebRequests+WebRequest..ctor (System.String url, System.Action`2 callback, Oxide.Core.Plugins.Plugin owner) [0x00000] in <filename unknown>:0
      at Oxide.Core.Libraries.WebRequests.EnqueueGet (System.String url, System.Action`2 callback, Oxide.Core.Plugins.Plugin owner, System.Collections.Generic.Dictionary`2 headers, Single timeout) [0x00000] in <filename unknown>:0
      at Oxide.Plugins.VACKicker.OnUserApprove (Network.Connection connection) [0x00000] in <filename unknown>:0
      at Oxide.Plugins.VACKicker.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00000] in <filename unknown>:0
      at Oxide.Plugins.CSharpPlugin.InvokeMethod (HookMethod method, System.Object[] args) [0x00000] in <filename unknown>:0
      at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x00000] in <filename unknown>:0
      at Oxide.Core.Plugins.Plugin.CallHook (System.String name, System.Object[] args) [0x00000] in <filename unknown>:0
     
  5. Wulf

    Wulf Community Admin

    Which Oxide version are you using? You should be on 2.0.1985 or higher.
     
  6. im using Oxide build 2.0.1985
     
  7. sorry fixed, me fault
     
  8. not working for me, have it set to zero vac bans and still get players joining with 1 or more bans, I have the latest 2006 oxide build
     
  9. latest oxide is 2026
     
  10. when did that come out ? i only updated oxide 2 days ago and the plugin wasnt working before that or after that and that version was higher than the one you advised the other poster to use, I will now get my server host to again update oxide but i doubt whether the plugin will work then
     
  11. Wulf

    Wulf Community Admin

    Nothing has changed with webrequests, so it shouldn't matter. The only issue was a few weeks ago when there was a bug with a hook.
     
  12. updated Oxide , still getting Vac banned players who usually hid behind a "private profile" which is against server rules, when they go public you see the Vac ban, I wont worry about it as i anticipate a whole mountain of pain when the new XP system is introduced next month and you guys (i think) will be getting more mail than ever from plugins that no longer work, so have a rest grab some coffee and enjoy the peace :)
     
    Last edited by a moderator: Jun 17, 2016
  13. this plugin still works ??
     
  14. Wulf

    Wulf Community Admin

    Should, the method and API it calls hasn't changed.
     
  15. wulf o'que is happening updated my rust upei the oxidize the rolled plugins put their commands in chat is not working all plugins
     
  16. Wulf

    Wulf Community Admin

    Update Oxide, you're on a broken build.
     
  17. more I already downloaded the site now and got the same thing
     
  18. Wulf

    Wulf Community Admin

    If chat commands are not working, you are outdated.
     
  19. already updated the game already downloaded the site oxidize however is with this error you already updated the oxide?
     
  20. Code:
    [06/24/2016 16:41:09] [Oxide] 16:41 [Error] Web request callback raised an exception in 'VACKicker v1.0.0' plugin (ArgumentOutOfRangeException: Argument is out of range.