Godmode

Moved

Total Downloads: 30,059 - First Release: Oct 23, 2014 - Last Update: Oct 27, 2017

4.76667/5, 60 likes
  1. Yes, it's blocking damage properly (I also have the plugin updated to the current latest version)
     
  2. Wulf

    Wulf Community Admin

    Did you try to run the command for someone else, ie. giving a name after /god or any symbols or anything?
     
  3. Strange things happening now, if u try to destroy something or shoot at someone, u loose your own hp

    i see errors only when players use /god command
     
  4. Wulf

    Wulf Community Admin

    This plugin won't hurt players. Are you sure you didn't install the Hide and Seek plugin?

    For your /god errors, my only thought is they are typing something else along with it, but I'll test and see.
     
  5. No hide and seek plugin on my server.
    I have did server update oxide update one more time (just in case it hasnt been updated to latest versions).I will also test /god name command ..
     
  6. Wulf

    Wulf Community Admin

    Dunno then about the damage, there is nothing in this plugin that would hurt players.
     
  7. Looks like i didnt updated oxide or server files thats why i have this strange bugs, looks like its ok for now!

    [Error] Failed to call hook 'God' on plugin 'Godmode v3.0.8' (NullReferenceException: Object reference not set to an instance of an object)
    Got it after i used /god areudeadyet
    :)
     
  8. Wulf

    Wulf Community Admin

    So you're still having that error?
     
  9. yes, but only if someone use /god and add something after

    its ok, now i know what it means

    Thx for help, all working now
     
  10. We have the same error Oxide and server are updated tho : [Oxide] 10:03 [Error] Failed to call hook 'God' on plugin 'Godmode v3.0.8' (ArgumentException: oldValue is the empty string.)
     
  11. Wulf

    Wulf Community Admin

    What do you have PrefixFormat set to? It should not be empty.
     
  12. Ohh well its empty xD Im gone change it and let you know if it works ;)
    [DOUBLEPOST=1461947169][/DOUBLEPOST]Ok works thank you that was an easy fix xD
     
  13. Hello! I install the plugin , but it does not work the button " RUN " when God mode enabled .
    Thank you in advance.

    Code:
    {
      "CanBeHurt": false,
      "CanBeLooted": false,
      "CanHurtPlayers": true,
      "CanLootPlayers": true,
      "InfiniteRun": true,
      "InformOnAttack": false,
      "PrefixEnabled": false,
      "PrefixFormat": "GOD"
    }
     
  14. Perhaps you could put in a check to see if PrefixFormat is null when it loads it from the config and reset it back to the default again, save the config then reload it while printing a warning to console saying it can't be empty and to change PrefixEnabled to false if you don't want the prefix on.

    People always are posting their errors from the console, so they should notice it telling them it has been reset and why.
     
  15. Wulf

    Wulf Community Admin

    I can check it and reset it, but I doubt many would read the message, they always still ask. ;)
     
  16. I will go by your word since you know this place better than me ;)
     
  17. Line 319, I don't see any specific significance in it Wulf (Maybe you could tell me), but it is what's preventing users from running while in Godmode.

    fn.OnRunPlayerMetabolism
    Line 319:
    Code:
           player.SetPlayerFlag(BasePlayer.PlayerFlags.NoSprint, false);
    It doesn't seem to be needed for the event that it's in, as it functions properly with line commented.
     
  18. Can i ask what version of Oxide u running?
    I had same issues with running while god mode is enabled and i was running older oxide.Installed new one , deleted config and reloaded GodMode plugin.That helped me.
     
  19. Wulf

    Wulf Community Admin

    That is needed. The NoSprint flag was added in an update, that disables that flag it when running. NoSprint true = no running.
    [DOUBLEPOST=1462152554][/DOUBLEPOST]
    An Oxide update wouldn't changes this, that flag is from Rust not Oxide. Nothing has changed in the Oxide builds that would affect this plugin.
     
  20. I see, it would seem as though that didn't fix it for me anyways, just seemed like it had for some reason.