refactor: update guide order, refactor and fix indentation (#310)

* fix: fix tab indentation

* refactor: change guide order and move ecs guide over to the rest of guide

* refactor: adjust wording and provide further clarification on ECS, fix links to ecs guide

* refactor: remove useless info from ECS systems guide

* refactor: add warning in env setup and building

Author: oskarscot

content/docs/en/guides/ecs/systems.mdx

@@ -115,51 +115,28 @@ public class PermissionAttachmentSystem extends RefChangeSystem<EntityStore, Per
     return EntityStoreRegistry.get().getPermissionAttachmentComponentType();
   }
 
-  private PermissibleProvider getProvider() {
-    for (PermissionProvider provider : PermissionsModule.get().getProviders()) {
-      if (provider instanceof PermissibleProvider) {
-        return (PermissibleProvider) provider;
-      }
-    }
-    LOGGER.atWarning().log("PermissibleProvider not found in PermissionsModule!");
-    return null;
-  }
-
   @Override
   public void onComponentAdded(@Nonnull Ref<EntityStore> ref, @Nonnull PermissionAttachment permissionAttachment, @Nonnull Store<EntityStore> store, @Nonnull CommandBuffer<EntityStore> commandBuffer) {
     UUIDComponent component = store.getComponent(ref, UUIDComponent.getComponentType());
     UUID playerUuid = component.getUuid();
 
-    PermissibleProvider provider = getProvider();
-    if (provider != null) {
-      provider.updateCache(playerUuid, permissionAttachment.getPermissions(), permissionAttachment.getGroups());
-    }
+    // PermissionAttachment component was added to a new entity
   }
 
   @Override
   public void onComponentSet(@Nonnull Ref<EntityStore> ref, @Nullable PermissionAttachment oldAttachment, @Nonnull PermissionAttachment newAttachment, @Nonnull Store<EntityStore> store, @Nonnull CommandBuffer<EntityStore> commandBuffer) {
     UUIDComponent component = store.getComponent(ref, UUIDComponent.getComponentType());
     UUID playerUuid = component.getUuid();
 
-    PermissionRepository repository = PermissiblePlugin.getInstance().getInternalPermissionRepository();
-    repository.savePlayerPermissions(playerUuid, newAttachment.getPermissions());
-    repository.savePlayerGroups(playerUuid, newAttachment.getGroups());
-
-    PermissibleProvider provider = getProvider();
-    if (provider != null) {
-      provider.updateCache(playerUuid, newAttachment.getPermissions(), newAttachment.getGroups());
-    }
+    // PermissionAttachment component was updated using replaceComponent or putComponent
   }
 
   @Override
   public void onComponentRemoved(@Nonnull Ref<EntityStore> ref, @Nonnull PermissionAttachment permissionAttachment, @Nonnull Store<EntityStore> store, @Nonnull CommandBuffer<EntityStore> commandBuffer) {
     UUIDComponent component = store.getComponent(ref, UUIDComponent.getComponentType());
     UUID playerUuid = component.getUuid();
 
-    PermissibleProvider provider = getProvider();
-    if (provider != null) {
-      provider.removeFromCache(playerUuid);
-    }
+    // PermissionAttachment component was removed from an entity
   }
 
   @Nullable
@@ -171,7 +148,7 @@ public class PermissionAttachmentSystem extends RefChangeSystem<EntityStore, Per
 ```
 
 In this system we listen for changes on the `PermissionAttachment` component inside of the `EntityStore`. This gives us access to `onComponentAdded`, `onComponentSet` and `onComponentRemoved` which in this example caches and persists permission data
-which is stored on a player inside of a custom `PermissionAttachment` component. This example comes from [Permissible](https://github.com/oskarscot/Permissible) permissions plugin where you can find more examples of heavy ECS usage.
+which is stored on a player inside of a custom `PermissionAttachment` component.
 
 
 

content/docs/en/guides/meta.json

@@ -2,13 +2,12 @@
   "title": "{meta.guides.title}",
   "pages": [
     "learning-to-learn.mdx",
-    "plugin",
     "java-basics",
+    "plugin",
+    "ecs",
     "...",
     "---Gameplay Systems---",
-    "prefabs.mdx",
-    "---Advanced Guides---",
-    "ecs"
+    "prefabs.mdx"
   ],
   "icon": "GraduationCap"
 }

content/docs/en/guides/plugin/build-and-test.mdx

@@ -5,6 +5,10 @@ authors:
     - name: "Michael B"
 ---
 
+<Callout type="warning">
+This guide is outdated and will be updated soon. Whilst this guide is still accurate, there are now better alternatives for building your mod.
+</Callout>
+
 If you followed along with the [Setting Up Your Development Environment](./setting-up-env) page, you should now be able to build your project.
 
 ## Building Your Mod

content/docs/en/guides/plugin/creating-commands.mdx

@@ -19,7 +19,7 @@ It's important to know that `AbstractPlayerCommand` extends `AbstractAsyncComman
 
 You can use the `Store` along with the `Ref` to access all entity components like the `Player` component, `UUIDComponent` or `TransformComponent`.
 
-For more information about Hytale's Entity Component System visit the [Hytale ECS Theory](https://hytalemodding.dev/en/docs/guides/ecs/hytale-ecs-theory) guide.
+For more information about Hytale's Entity Component System visit the [Hytale ECS Theory](https://hytalemodding.dev/en/docs/plugin/ecs/hytale-ecs-theory) guide.
 
 
 ```java

content/docs/en/guides/plugin/setting-up-env.mdx

@@ -6,6 +6,11 @@ authors:
       link: "https://itsneil.dev"
 ---
 
+<Callout type="warning">
+This guide is outdated and will be updated soon. Whilst this guide is still accurate, there are now better alternatives for setting up your environment.
+</Callout>
+
+
 This guide will walk you through setting up a complete development environment for Hytale modding, including all necessary tools and dependencies.
 
 ## Prerequisites

content/docs/en/guides/plugin/store-persistant-data.mdx

@@ -6,6 +6,8 @@ authors:
       url: "https://github.com/ArcticRaven"
     - name: "Neil Revin"
       url: "https://itsneil.dev/"
+    - name: "oskarscot"
+      url: "https://oskar.scot"
 ---
 
 Here is how to store persistent data using a custom component on a Player.
@@ -105,7 +107,7 @@ public class YourPlugin extends JavaPlugin {
 
 Your component will be stored within the `Store<EntityStore>` when added to the player. In the provided example,
 we'll fetch this data off the player using the `ensureAndGetComponent()` method, which will add the component to
-the player if it does not exist.
+the player if it does not exist with the default values.
 
 ```java
 public class IncompleteCustomCommand extends AbstractPlayerCommand {
@@ -123,13 +125,15 @@ public class IncompleteCustomCommand extends AbstractPlayerCommand {
         @NonNullDecl World world
     ) {
         YourPlayerData customData = store.ensureAndGetComponent(ref, YourPlugin.instance().getYourPlayerDataComponent());
-
+        // ensureAndGetComponent adds the component to the ref, with the default values defined inside your component.
  		// use your data
     }
 }
 ```
 
 And that's it! Your data will now be saved and loaded automatically with the player.
 
-## Conclusion
-Using custom components to store persistent data on players is a powerful way to maintain state across sessions. By following the steps outlined above, you can easily create, register, and utilize your own data structures within the Hytale modding framework. This approach ensures that your data is seamlessly integrated with the game's existing systems, providing a robust solution for managing player-specific information. Happy modding!
+Using custom components to store persistent data on players is a powerful way to maintain state across sessions. 
+By following the steps outlined above, you can easily create, register, and utilize your own data structures within the Hytale ECS framework. 
+This approach ensures that your data is seamlessly integrated with the game's existing systems.
+For more information about Hytale's Entity Component System visit the [Hytale ECS Theory](https://hytalemodding.dev/en/docs/plugin/plugin/hytale-ecs-theory) guide.