- Plugins can override permission evaluation.
   * PluginBase contains onRequestPermission(String playerKey, String permission)
   * return null (default implementation) to let Rainbow's default permission evaluate.
- Most built-in commands previously provided by default now require permissions:
   /bal      rainbow.bal
   /bp      rainbow.bp
   /buy      rainbow.buy
   /colors      rainbow.colors
   /divorce    rainbow.divorce
   /ec      rainbow.ec
   /home      rainbow.home
   /ignore      rainbow.ignore
   /jemote      rainbow.jemote
         rainbow.jemote.smile
         rainbow.jemote.hug
         ...
         rainbow.jemote.*
   /jot      rainbow.jot
   /marry      rainbow.marry
   /me      rainbow.me
   /name      rainbow.name
   /namecolor   rainbow.namecolor
   /pay      rainbow.pay
   /plugins   rainbow.plugins
   /ride      rainbow.ride
   /sell      rainbow.sell
   /sethome   rainbow.sethome
   /spawn      rainbow.spawn
   /suicide   rainbow.suicide
   /tell, /msg   rainbow.tell
   /throw      rainbow.throw
   /tpaccept   rainbow.tpaccept
   /tpahere   rainbow.tpahere
   /trigger   rainbow.trigger
   /ver      rainbow.ver
   /warp      rainbow.warp
   /wild      rainbow.wild
   /worth      rainbow.worth

- For convenience to server owners who want the default permission configuration as before.
  I've included a BasicPerms.txt file and you can run:
  /diw script BasicPerms

- CRON Command !!
   Create commands to run at a specified interval
   /cron add ServerLoop 23h diw autorestart
   /cron add TehCakes 15s give @a cake
   
   All kinds of options open up. One is scheduled restarts, for the more adventurous, 
   could do creative things with commands like setblock and /diw script 
   Timing resolution is 500ms (half second) to avoid accidentally spamming commands.