today we want to know why the structure of bypasses is so ..irritating

The flag bypass permission for players
redprotect.flag.bypass.(flagname)
Examples: redprotect.flag.bypass.build allows to bypass build flag.
You can define adminflag as player useage flag by simly write the name in their permission
examples: redprotect.flag.bypass.minefarm give player on this region the abiility to set minefarm as flag what usually is an adminflag

Now why its irritating..

1. so what is the bypass for it now?
   redprotect.flag.admin.minefarm.bypass or redprotect.flag.bypass.minefarm

2. why the bypass permissions have 2 structure logics here that make it harder to handle..

redprotect.flag.bypass.(flagname) for players
redprotect.flag.admin.(flagname).bypass for admins
the logic suiting to the players permission would be ....redprotect.flag.admin.bypass.(flagname)
so why you choose this different design for the adminflag? :3

A small out of thread quest, dont wanne open a new thread for this.
The wiki tells about permissions that not exsting anymore or do they?
redprotect.own.panel

• redprotect.command.gui.edit hm does only exists as redprotect.command.admin.gui.edit or does the other one exists too?
  Does a redprotect.admin.panel or redprotect.panal also exists?

Also about Teleport...
we have redprotect.command.admin.teleport to teleport to all regions
Is there a redprotect.command.teleport or redprotect.command.own.teleport to player are just allowed to teleport to their own zones but not to others?