Godmode

Oh yeah that worked. now how do I turn off everyone else having Godmode turned on?

 

revoke all those the perms you did give it before maybe. by something like 'revoke group xxx godmode.admin' or 'revoke user xxx godmode.admin'.
Also the chatcommand '/gods' show you who has it currently on, active or sleeping.

 

I didn't give any permissions out to any other users but me and when I do /gods it tells me only I'm in God mode although everyone sleeping cannot be looted.

 

then you got probably any other plugin activated which is donig that, like sleeper-protection or soemtihng else. dont know the right names anymore. There where two of such from Wulf, which could change this.

 

No got nothing like that installed. I just gave myself the permission godmode.lootplayers and I can now loot players but how would I set that to everyone

 

This version is not working. It refuses to put me back in godmode.

I tried to reverse it back to the old version, and that version is now broke aswell.

A way to fix this?

Gyazo - 9d864fcb8936be5e689926339ca790c0.png

Regards
Whistle

 

Same issue as previous writers, everyone gets godmode while I load the plugin. I have not granted any group permissions except the admin group.

 

can confirm. /god = disabled godmode or something like that. can't toggle it in adminmenu either
i have reverted to the previous version for now.
@whistlerzs, make sure you are doing /reload Godmode when reverting

 

I am trying to download the mod but I'm getting this The requested attachment could not be found. when i hit the download

 

Yeah I'm getting the same

 

Help, The requested attachment could not be found.

 

Wulf, still the same bug.

Gyazo - 1913d5748aca4030e12147e689dcc08e.jpg

Regards
Whistle

 

ya, the problems from yesterday update are fixed.

 

@Wulf Im getting this error with lang, in Kits plugin I have this error too:



Seems like a problem with Lang API

 

its weird no matter what /god just says disabled god mode over and over each time? This was on 4.0.2, i rolled back to 3.2.1 and it works fine again... hmm.

 

@Mike - Have you updated your plugin? According to the change log, it should have been fixed.