Offline Protection Not Working

I have offline protection enabled for all players via the default group. It is working for everyone except for one base. The player is offline, yet the base is showing as unprotected. I can't figure out what the issue is. Any suggestions?

It looks like the base does not have a founder. The founder is loaded from whoever has the same OwnerID thats found attached to the tool cupboard. Do you have a plugin that lets you see what the OwnerID of the toolcupboard is?

So if the founder has the raidprotection.ignore permission, then the base is raidable even if the other players are offline?

I just tested this and it appears that is the case. This seems like a bug to me or at least something that needs to be fixed. 

Any thoughts on this? I would like to be able to assign the ignore permission to certain groups of users, so that their online status does not influence raid protection, but if they happen to be the founder and in one of those groups, their base won't be protected at all.

Hey, just checking in on this one. It has been awhile so thought I would see if there were any updates.

Hey no updates for this, I'm still not sure what is happening here... you said the found has the ignore perm, but you still want the base protected? If thats the case, can you use the admin commands to assign a different founder?

Correct, protection is not working if the founder of the TC has the raidprotection.ignore permission assigned to them.

I could try that, however I have no way of knowing which bases are covered by TCs that were placed by players with this permission, so it wouldn't really do me any good, plus that is a manual process every time a TC is placed that meets this condition.

I think we were discussing this in another support ticket right? This one:
https://codefling.com/files/support/16868-ignore-permission-not-working/

its related, but not the same issue
this issue is that if the founder of the tc has the ignore permission, then raid protection doesn't work

After discussing this offline we determined that the way this works is intentional

Changed Status from Pending to Not a Bug