First suggestion: Add a more detailed flag for doors. use:door:birch use:door:oak use:door:jungle use:door:spruce use:door:darkoak use:door:iron Examples of use: You give everybody use:door perms so they can enter a nice village you built, but you don't want to have people going into a building. You can easily place an unused door and do /res pset use:door:birch false so nobody can enter the building and you aren't plagued with ugly access/restrict signs Second suggestion: Allow residence owners and admins to open iron doors by right clicking it or with an item in hand.
Use doors seems sufficient enough to me, especially if you include access signs to the mix. As for right clicking iron doors, that would be a fundamental change of this doors base functionality....would not be as simple.
Only the owner of an egg can pick up a dragon egg. I assume it would be that easy. It wouldn't replace the existing door command. It would just be an optional option that is optionally optional. There would still be use:door Just think of the limited possibilities!
I don't think this would matter too much since there are access signs, but I think it would be nice to have places you don't want people in closed off without a sign +1
+1, to avoid clutter of access signs near doors and to make easier to show which doors are accessible to anyone or certain groups...
The only part of this idea I agree with is the ability for res owners and admins to open iron doors like wooden ones.
As cool as this is. Simply isn't feasible with how the subflag system is written - only written to support 1 level of subflags. Consider it denied. Although we reserve the possibility that if that system is re-written (highly unlikely) that we would definitely consider a suggestion like this. And, no. With the iron doors also. I think it would be best to keep those restricted to redstone input. I like that feature of minecraft.
That doesn't solve anything >_>. and definitely couldn't use the '_' character. The issue has nothing to do with how possible it is, it has everything to do with the amount of time it would take to rewrite that entire system to support such a specific usage. The rewrite would include at least 4 things, loading/saving the flag permissions, setting new flags, a conversion system to transfer to the new flags, and maintaining a quick way to read them when the server needs to check it. The current system simply was not designed At All to accommodate a 3rd level of flags. Even the non-subflags like build. Is recorded in the system as build:main. Again, technically possible to design a different mapping to handle this, but working on this would simply be overly tedious for extremely little results. :/
