Add comment to config to warn customers that changing command visibility also affects command blocks

pom.xml

@@ -5,7 +5,7 @@
     <!-- A good example on why temporary names for project identification shouldn't be used -->
     <groupId>LibsDisguises</groupId>
     <artifactId>LibsDisguises</artifactId>
-    <version>10.0.3</version>
+    <version>10.0.3-SNAPSHOT</version>
 
     <build>
         <defaultGoal>exec:java clean install</defaultGoal>

src/main/java/me/libraryaddict/disguise/disguisetypes/Disguise.java

@@ -80,10 +80,11 @@ public abstract class Disguise {
      * If set, how long before disguise expires
      */
     private long disguiseExpires;
-    @Getter
     /**
      * For when plugins may want to assign custom data to a disguise, such as who owns it
-     */ private final HashMap<String, Object> customData = new HashMap<>();
+     */
+    @Getter
+    private final HashMap<String, Object> customData = new HashMap<>();
 
     public Disguise(DisguiseType disguiseType) {
         this.disguiseType = disguiseType;

src/main/resources/config.yml

@@ -22,6 +22,7 @@ Permissions:
   # The permissions for commands are a simple 'libsdisguises.seecmd.command' where 'command' can be
   # 'disguise', 'undisguise' etc. A simple 'libsdisguises.seecmd' permission may also work for children
   # If you change this while the server is running, players may need to rejoin for it to take effect
+  # Remember that command blocks need 'TRUE' or 'OP' to use the commands.
   # TRUE = Everyone can see this, the default. Can be negated with permissions
   # FALSE = No one can see this without permissions to allow it
   # OP = Only operators can see this