From cbf6e6041baea40dd21f8951e9cfdf6b87ef2707 Mon Sep 17 00:00:00 2001
From: foxikle <tristantroop260@gmail.com>
Date: Sat, 30 Nov 2024 19:13:22 -0500
Subject: [PATCH 1/2] add versions

---
 help-versions.json | 4 ++++
 1 file changed, 4 insertions(+)
 create mode 100644 help-versions.json

diff --git a/help-versions.json b/help-versions.json
new file mode 100644
index 0000000..4804bbf
--- /dev/null
+++ b/help-versions.json
@@ -0,0 +1,4 @@
+[
+  {"version":"1.6","url":"/v/1.6/","isCurrent":false},
+  {"version":"1.7","url":"/v/1.7/","isCurrent":true}
+]
\ No newline at end of file

From 637f5803335e9dec11642b0009a77a2d09c1bf1b Mon Sep 17 00:00:00 2001
From: foxikle <tristantroop260@gmail.com>
Date: Fri, 20 Dec 2024 22:11:01 -0500
Subject: [PATCH 2/2] 1.7

---
 Writerside/cfg/buildprofiles.xml              |   5 +-
 Writerside/customnpcs.tree                    |  29 +--
 Writerside/redirection-rules.xml              |   4 +
 Writerside/topics/API-Documentation.md        |   5 +-
 Writerside/topics/API-Roadmap.md              |  20 +++
 Writerside/topics/Acknowledgments.md          |   2 +-
 .../topics/Creating-an-NPC-with-the-API.md    | 167 ++++++++++++++++++
 .../topics/Getting-Started-With-The-API.md    |  73 ++++++++
 Writerside/topics/Gimmicks.md                 |   7 +
 Writerside/topics/Using-Events.md             |  55 ++++++
 Writerside/topics/Using-the-Action-System.md  |   2 +-
 Writerside/topics/Writing-Custom-Actions.md   | 158 +++++++++++++++++
 Writerside/topics/customnpcs.md               |   3 +
 Writerside/writerside.cfg                     |   2 +-
 help-versions.json                            |   4 -
 15 files changed, 512 insertions(+), 24 deletions(-)
 create mode 100644 Writerside/topics/API-Roadmap.md
 create mode 100644 Writerside/topics/Creating-an-NPC-with-the-API.md
 create mode 100644 Writerside/topics/Getting-Started-With-The-API.md
 create mode 100644 Writerside/topics/Gimmicks.md
 create mode 100644 Writerside/topics/Using-Events.md
 create mode 100644 Writerside/topics/Writing-Custom-Actions.md
 create mode 100644 Writerside/topics/customnpcs.md
 delete mode 100644 help-versions.json

diff --git a/Writerside/cfg/buildprofiles.xml b/Writerside/cfg/buildprofiles.xml
index e217495..8a7cee3 100644
--- a/Writerside/cfg/buildprofiles.xml
+++ b/Writerside/cfg/buildprofiles.xml
@@ -2,7 +2,7 @@
 <buildprofiles xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                xsi:noNamespaceSchemaLocation="https://resources.jetbrains.com/writerside/1.0/build-profiles.xsd">
     <variables>
-        <primary-color>emerald</primary-color>
+        <primary-color>aqua</primary-color>
         <product-web-url>https://foxikle.dev</product-web-url>
         <download-title>Download CustomNPCs</download-title>
         <download-page>https://modrinth.com/plugin/customnpcs</download-page>
@@ -15,7 +15,8 @@
         <footer>
             <copyright>Foxikle 2024</copyright>
             <social type="youtube" href="https://youtube.com/@foxikle">Youtube</social>
-            <social type="email" href="mailto:support@foxikle.dev">Email</social>
+            <social type="email" href="support@foxikle.dev">Email</social>
+            <social type="blog" href="https://foxikle.dev">Website</social>
             <link href="discord.gg/4uThsAfJ8g">Discord</link>
             <link href="https://github.com/foxikle/customnpcs">GitHub</link>
             <link href="https://patreon.com/foxikle">Patreon</link>
diff --git a/Writerside/customnpcs.tree b/Writerside/customnpcs.tree
index fddf55d..9a2af97 100644
--- a/Writerside/customnpcs.tree
+++ b/Writerside/customnpcs.tree
@@ -2,21 +2,24 @@
 <!DOCTYPE instance-profile
         SYSTEM "https://resources.jetbrains.com/writerside/1.0/product-profile.dtd">
 
-<instance-profile id="customnpcs"
-                 name="CustomNPCs"
-                 start-page="Wiki.md">
-
-    <toc-element topic="Wiki.md">
-        <toc-element topic="getting-started.md"/>
-        <toc-element topic="configuring-customnpcs.md"/>
-        <toc-element topic="Creating-Your-First-NPC.md"/>
-        <toc-element topic="Commands.md"/>
-        <toc-element topic="Using-the-Action-System.md">
-            <toc-element topic="Using-Conditions-Within-Actions.md"/>
-        </toc-element>
+<instance-profile id="customnpcs" name="CustomNPCS" start-page="Wiki.md">
+    <toc-element topic="Wiki.md"/>
+    <toc-element topic="getting-started.md"/>
+    <toc-element topic="configuring-customnpcs.md"/>
+    <toc-element topic="Creating-Your-First-NPC.md"/>
+    <toc-element topic="Commands.md"/>
+    <toc-element topic="Using-the-Action-System.md">
+        <toc-element topic="Using-Conditions-Within-Actions.md"/>
+    </toc-element>
+    <toc-element topic="API-Documentation.md">
+        <toc-element topic="Getting-Started-With-The-API.md"/>
+        <toc-element topic="Creating-an-NPC-with-the-API.md"/>
+        <toc-element topic="Writing-Custom-Actions.md"/>
+        <toc-element topic="Using-Events.md"/>
+        <toc-element topic="Gimmicks.md"/>
+        <toc-element topic="API-Roadmap.md"/>
     </toc-element>
     <toc-element topic="Support.md"/>
     <toc-element topic="Contributing.md"/>
     <toc-element topic="Acknowledgments.md"/>
-    <toc-element topic="API-Documentation.md"/>
 </instance-profile>
\ No newline at end of file
diff --git a/Writerside/redirection-rules.xml b/Writerside/redirection-rules.xml
index 54b11a6..4be2a9a 100644
--- a/Writerside/redirection-rules.xml
+++ b/Writerside/redirection-rules.xml
@@ -14,4 +14,8 @@
         <description>Created after removal of "Creating an NPC" from Help Instance</description>
         <accepts>Creating-an-NPC.html</accepts>
     </rule>
+    <rule id="98a84b6">
+        <description>Created after removal of "v2" from CustomNPCs</description>
+        <accepts>v2.html</accepts>
+    </rule>
 </rules>
\ No newline at end of file
diff --git a/Writerside/topics/API-Documentation.md b/Writerside/topics/API-Documentation.md
index cd7c6f8..2e33222 100644
--- a/Writerside/topics/API-Documentation.md
+++ b/Writerside/topics/API-Documentation.md
@@ -1,4 +1,5 @@
 # API Documentation
 
-## Coming Soon ;)
-For now, look [here](https://github.com/Foxikle/CustomNPCs/wiki).
+The API is the best way to utilize the true potential of CustomNPCS. With the API, you can customize nearly every aspect
+of any NPC. The API is written in Java, and requires the CustomNPCs plugin to be installed on the same server as the 
+plugin utilizing the API.
\ No newline at end of file
diff --git a/Writerside/topics/API-Roadmap.md b/Writerside/topics/API-Roadmap.md
new file mode 100644
index 0000000..d8704c2
--- /dev/null
+++ b/Writerside/topics/API-Roadmap.md
@@ -0,0 +1,20 @@
+# API Roadmap
+
+Here is the current roadmap for features that I would *like* to implement. This doesn't mean these features are 
+guaranteed to be implemented in the given version, or at all. If you would like to request a feature, join my Discord
+server and create a feature request ticket. Alternatively, you could create an issue with the feature request template.
+
+## 1.8
+- Walking paths (A list of locations to "teleport" the NPC to)
+- Multiple data storage options, (Databases, file, etc.)
+  - Along with this, NPC data will likely shift from YAML to json
+- A pose editor
+- A bunch of qol and small tweaks to make using the plugin better
+
+## 1.9
+- Goal based AI
+- Generic pathfinding
+- "Keyframed" walking. 
+  - The idea here is to have a set of points or "keyframes" for the NPC to navigate in between, using its own pathfinding
+to fill in the gaps.
+- Adding the ability to damage the NPCs (and knock back) would probably fit in well with the theme of this update.
\ No newline at end of file
diff --git a/Writerside/topics/Acknowledgments.md b/Writerside/topics/Acknowledgments.md
index 0cb4907..ca743d3 100644
--- a/Writerside/topics/Acknowledgments.md
+++ b/Writerside/topics/Acknowledgments.md
@@ -4,4 +4,4 @@ day knowing that you chose my plugin to use. I appreciate everyone who reaches o
 
 If you would like to support me, you can do so on [Patreon](https://patreon.com/foxikle).
 
-\~ Foxikle <3
\ No newline at end of file
+Foxikle <3
\ No newline at end of file
diff --git a/Writerside/topics/Creating-an-NPC-with-the-API.md b/Writerside/topics/Creating-an-NPC-with-the-API.md
new file mode 100644
index 0000000..1f6b19c
--- /dev/null
+++ b/Writerside/topics/Creating-an-NPC-with-the-API.md
@@ -0,0 +1,167 @@
+# Creating an NPC with the API
+
+
+> You can visit the JavaDocs at `https://repo.foxikle.dev/javadoc/public/dev/foxikle/customnpcs/<VERSION>`
+> [Here](https://repo.foxikle.dev/javadoc/public/dev/foxikle/customnpcs/1.7) are the latest javadocs!
+
+## Creating the NPC object
+To start, you need an NPC object. You can create one by calling `NPC::new` (The constructor)
+Here is an example:
+
+```java
+World world = Bukkit.getWorld("world"); // the default world name
+// But you should do a null check, as 
+// an error will be thrown if the world is null 
+NPC npc = new NPC(world);
+```
+
+## General Customization
+### Position
+
+From there, you have to do a few things in order for the NPC to be useful. For starters, you should set the 
+spawn location. If you don't the NPC will spawn at (0, 0, 0).
+```java
+// arbitrary numbers for the sake of example
+npc.setPosition(new Location(world, 100, 100, 100));
+```
+
+### Rotation
+
+If you want to customize the yaw and pitch of the NPC's head, you should do so using the Location object.
+```java
+// arbitrary numbers for the sake of example
+Location loc = new Location(world, 100, 100, 100, 45, 0);
+npc.setPosition(loc);
+```
+
+
+### Skin Data
+If you want to specify a skin for the NPC, you should do so using the `setSkinData` method. To get the signature and
+value, you can use InventiveTalent's [Mineskin](https://mineskin.org).
+```java
+String value = ...; // assume an actual value
+String signature = ...; // assume an actual signature
+String skinName = ...; // shown when a user tries to edit the NPC
+npc.setSkinData(skinName, signature, value)
+```
+
+## The Settings Object
+> It is imperative that you call `NPC#reloadSettings()` if you edit the Settings or Equipment objects **after** creating
+> the NPC {style=warning}
+
+
+### Interactability 
+Interactability defines if the NPC will have the clickable hologram. (More info Later) If this is set to false, even if 
+you give the NPC actions, they will be ignored. (Defaults to **false**)
+To change it, simply call
+```java
+npc.getSettings().setInteractable(true);
+```
+
+### Tunnel Vision
+Tunnel vision defines if the NPC will look at nearby players. (Defaults to **false**)
+To change it, simply call
+```java
+npc.getSettings().setTunnelVision(true);
+```
+
+### Resilient
+Resiliency, or being resilient, defines if the NPC should persist on server restarts or running `/npc reload`. This
+defaults to **false**, unlike creating NPCs using the plugin's UI. Setting this to true may fill up your `npcs.yml` file
+if you are not careful.
+To change it, simply call
+```java
+npc.getSettings.setResilient(true);
+```
+
+### ~~Direction~~ (Deprecated -- To be removed in 1.8)
+Lets you set the yaw of the NPC's head. Just set the Yaw in the NPC's location :)
+
+### Skin Data (But settings)
+The method on the NPC is just a wrapper around the settings object, it is functionally the same. You can view the docs
+on it [here](#skin-data).
+
+### Hide Clickable Hologram
+This option hides the Clickable hologram, making the NPC appear as if I wasn't interactable, yet still being 
+interactable. (Defaults to **false**)
+To change it, simply call
+```java
+npc.getSettings().setHideClickableHologram(true);
+```
+
+### Custom Interactable Hologram
+This option allows you to override the global Clickable Hologram value. The string value can contain MiniMessage tags 
+and PlaceholderAPI placeholders.
+To change it, simply call
+```java
+npc.getSettings().setCustomInteractableHologram("<Your hologram>");
+```
+
+## The Equipment Object
+> It is imperative that you call `NPC#reloadSettings()` if you edit the Settings or Equipment objects **after** creating
+> the NPC {style=warning}
+
+I am not going to go through every method, because their names are self-explanatory. The point is, you can set/get the 
+itemstack object the NPC uses. 
+
+If you would like to import that equipment from a player, for example, you can use the `importFromEntityEquipment()`
+method.
+
+Here is an example:
+```java
+Player player = ...; // pretend its valid
+npc.getEquipment().importFromEntityEquipment(player.getEquipment());
+```
+
+## Using Actions
+In 1.7, the Action system got a complete rewrite. This makes it way easier to use over its predecessors. Instead of 
+using a string array and an enum, each action has its own class. If you want to add an action, you can just call 
+`NPC#addAction(Action)`. [Here](Using-the-Action-System.md) is a list of available actions. For example, sending a message:
+```java
+npc.addAction(new SendMessage("Text Here", 0, ONE, List.of()));
+```
+All actions follow the same general constructor parameter layout:
+
+First, are the action specific parameters, in our case, the message to send.
+
+Then, there is an integer, specifying the number of ticks of delay to run the action after the initial interaction.
+
+Then, there is a `Condition.SelectionMode` enum constant, signifying if one, or all of the following conditions must be
+met in order for the action to execute.
+
+Finally, the list of conditions the player must fulfil for the Action to be executed.
+
+If you would like to write your own actions, check out [this](Writing-Custom-Actions.md) page.
+
+If you would like to create your own Conditions, check out the [Roadmap](API-Roadmap.md), as that is a planned feature.
+
+## Moving the NPC
+You can move the NPC by calling the `moveTo(Location)` method. Please note that it takes the pitch and yaw into account.
+The movements are only temporary, as reloading the npcs will put the NPC back to its spawn location.
+
+## Looking at things
+You can make the NPC look at things in two ways. First, you can use the `lookAt(Location)` to look at the specified 
+location.
+```java
+npc.lookAt(new Location(world, 0, 0, 0);
+```
+Additionally, you can look at an entity instead.
+```java
+npc.lookAt(entity, true);
+```
+The first argument is the entity to look at. It cannot be null.
+
+The second argument is true of the npc should look at the entity's head, or false for their feet
+
+## Swinging the NPC's arm
+You can swing the NPC's arm by calling `npc.swingArm()`.
+
+## Manual Injection (Not recommended)
+Even though the plugin handles injection, or making the NPCs actually appear, it is possible to handle it yourself.
+This could be useful, for example, if you are creating per-player NPCs. (But even then, there are better ways of doing 
+it) In order to inject NPCs yourself, you can call
+```java
+npc.injectPlayer(player);
+```
+
+Please note, if you want to do conditional injection, you should cancel the NpcInjectEvent instead :)
diff --git a/Writerside/topics/Getting-Started-With-The-API.md b/Writerside/topics/Getting-Started-With-The-API.md
new file mode 100644
index 0000000..9240607
--- /dev/null
+++ b/Writerside/topics/Getting-Started-With-The-API.md
@@ -0,0 +1,73 @@
+# Getting Started With The API
+
+To start, you need to add CustomNPCs as a dependency in your dependency manager.
+
+<tabs>
+<tab title="Maven">
+Add the repository to the `repositories` section in your `pom.xml`
+<code-block lang="XML">
+&lt;repository&gt;
+  &lt;id&gt;customnpcs&lt;/id&gt;
+  &lt;name&gt;Foxikle's Repository&lt;/name&gt;
+  &lt;url&gt;https://repo.foxikle.dev/public&lt;/url&gt;
+&lt;/repository&gt;
+</code-block>
+
+
+Then, add the dependency to your dependencies section
+<code-block lang="xml">
+&lt;dependency&gt;
+  &lt;groupId&gt;dev.foxikle&lt;/groupId&gt;
+  &lt;artifactId&gt;customnpcs&lt;/artifactId&gt;
+  &lt;version&gt;1.7&lt;/version&gt;
+&lt;/dependency&gt;
+</code-block>
+</tab>
+<tab title="Gradle (kotlin)">
+
+Add the CustomNPCs Maven Repository
+
+<code-block lang="kotlin">
+maven {
+    name = "foxiklePublic"
+    url = uri("https://repo.foxikle.dev/public")
+}
+</code-block>
+ OR
+<code-block lang="kotlin">
+maven ("https://repo.foxikle.dev/public")
+</code-block>
+
+
+<br>
+
+Then, add the dependency to your `build.gradle.kts`
+<code-block lang="KOTLIN">
+compileOnly("dev.foxikle:customnpcs:1.7")
+
+</code-block>
+
+</tab>
+<tab title="Gradle (Groovy)">
+
+Add the CustomNPCs Maven Repository
+
+<code-block lang="groovy">
+maven {
+    name "customnpcs"
+    url "https://repo.foxikle.dev/public"
+}
+
+</code-block>
+
+Add the dependency to your `build.gradle`
+ <code-block lang="groovy">
+compileOnly "dev.foxikle:customnpcs:1.7"
+
+</code-block>
+</tab>
+</tabs>
+
+
+Then, you can reload your project and get ready to use the API!
+
diff --git a/Writerside/topics/Gimmicks.md b/Writerside/topics/Gimmicks.md
new file mode 100644
index 0000000..dc2204e
--- /dev/null
+++ b/Writerside/topics/Gimmicks.md
@@ -0,0 +1,7 @@
+# Gimmicks
+
+The API has a few gimmicks with it, as it is still under active development. Here are a few.
+
+NPC Rotation
+: In order to set the yaw of the NPC's head, you can use two methods. You can either call `Settings#setDirection` or 
+you can modify the NPC's SpawnLocation property.
\ No newline at end of file
diff --git a/Writerside/topics/Using-Events.md b/Writerside/topics/Using-Events.md
new file mode 100644
index 0000000..89c6307
--- /dev/null
+++ b/Writerside/topics/Using-Events.md
@@ -0,0 +1,55 @@
+# Using Events
+
+> Please note that this is an advanced tutorial and I expect you to have an understanding of the structure
+> of a Paper plugin, and the event system.
+
+
+> Please note the event system is still green, and likely to change substantially as the api gets ironed out. {style=note}
+
+
+## Default Methods
+All of the events inherit from `NpcEvent`, which implements `Cancellable` and `PlayerEvent`. Meaning each event has a 
+`getPlayer()`, `isCancelled()`, and `setCancelled()` method. On top of that, each event has a `getNpc()` method. That 
+method returns an InternalNpc, which is rather unstable, and doesn't see proper deprecation. It's best to use the 
+`apiNPC()` to use the wrapper object.
+
+## NpcInjectEvent
+Lets you cancel the injection of NPCs. Called when the NPC's InjectionManager determines a player needs to be injected.
+
+### Unique Methods {id="unique-methods-inject"}
+**getDistance()**
+: Gets the distance between the player and the NPC being injected.
+
+**getDistanceSquared()**
+: Gets the distance between the player and the NPC before it has been square rooted. This is slightly more performant,
+and is generally better than `getDistance()`.
+
+
+## NpcDeleteEvent
+Lets you cancel the deletion of NPCs.
+
+### Unique Methods {id="unique-methods-delete"}
+**getDeletionSource()**
+: Gets the reason the NPC was deleted. The possible solutions are: `COMMAND`, `MENU`, `API`, and `UNKNOWN`. For more 
+information about what each source means, check out the javadocs.
+
+
+## NpcInteractEvent
+Lets you cancel the deletion of NPCs.
+
+### Unique Methods {id="unique-methods-interact"}
+**getExecutingActions()**
+: Gets the actions that meet their conditions for execution. If the event is not cancelled, these are the actions that 
+will be executed.
+
+**getFailingActions()**
+: Gets the actions that have failed their conditions for execution. Even if the event is cancelled, these actions won't
+be executed.
+
+
+
+
+
+
+
+
diff --git a/Writerside/topics/Using-the-Action-System.md b/Writerside/topics/Using-the-Action-System.md
index d723736..ef438a5 100644
--- a/Writerside/topics/Using-the-Action-System.md
+++ b/Writerside/topics/Using-the-Action-System.md
@@ -20,7 +20,7 @@ writing, version 1.6 provides the following 12 default actions.
 
 <warning>
     The `Toggle Following` action is an unstable feature, and therefore is still under heavy development.
-As of 1.6, it is currently disabled.
+As of 1.7, it is currently disabled.
 </warning>
     <tip>
         The 
diff --git a/Writerside/topics/Writing-Custom-Actions.md b/Writerside/topics/Writing-Custom-Actions.md
new file mode 100644
index 0000000..0ebcc2a
--- /dev/null
+++ b/Writerside/topics/Writing-Custom-Actions.md
@@ -0,0 +1,158 @@
+# Writing Custom Actions
+
+> Please note that this is an advanced tutorial, and I will be glazing over a few topics like inheritance.
+>  {style=note}
+> Additionally, this guide exposes a lot of the internals of the plugin, which are subject to change without proper
+> deprecation and are likely to break as this new api gets ironed out.
+
+## Writing the Action class
+To get started, create a class that extends `Action`.
+
+## Creation Button
+To start, write a method that will be the creation button, used by the player creating menus via the UI. For the
+purposes of this demo, I will call it `creationButton()`. The method should be static. The method's return type should 
+be `io.github.mqzen.menus.misc.button.Button`. This is a button that is clickable in the menu, from Mqzn's Lotus 
+library. Here is the creation button method for the ActionBar action.
+```java
+public static Button creationButton(Player player) {
+        return Button.clickable(ItemBuilder.modern(IRON_INGOT)
+                        .setDisplay(Utils.mm("Actionbar"))
+                        .setLore(Utils.mm("Displays an Actionbar"))
+                        .build(),
+                ButtonClickAction.plain((menuView, event) -> {
+                    event.setCancelled(true);
+                    Player p = (Player) event.getWhoClicked();
+                    ActionBar actionImpl = new ActionBar("", 0, Condition.SelectionMode.ONE, new ArrayList<>());
+                    CustomNPCs.getInstance().editingActions.put(p.getUniqueId(), actionImpl);
+                    menuView.getAPI().openMenu(p, actionImpl.getMenu());
+                }));
+    }
+```
+
+> If you want a MiniMessage parser, you can use `Utils.mm()` or `Msg.format()`. They both work!
+
+It is important that you include the `CustomNPCs.getInstance().editingActions.put(p.getUniqueId(), actionImpl);`, as
+that tells the plugin which action is being edited by the given player. 
+*While I acknowledge that this isn't ideal, this is the current structure of the internals.*
+
+## Serializing and Deserializing
+
+Continuing with the trend of copying the ActionBar class, here is how CustomNPCs helps you write actions that can be
+serialized and deserialize without much work from the action developer. In the Action superclass, there are a handful
+of utility methods to parse individual "fields" of the serialized blob of data, which is defined during serialization,
+more on that in a bit. Without further ado, here is the deserializer for the ActionBar class.
+```java
+ public static <T extends Action> T deserialize(String serialized, Class<T> clazz) {
+        if (!clazz.equals(ActionBar.class)) {
+            throw new IllegalArgumentException("Cannot deserialize " + clazz.getName() + " to " + ActionBar.class.getName());
+        }
+        String rawMessage = parseString(serialized, "raw");
+        ParseResult pr = parseBase(serialized);
+
+        ActionBar message = new ActionBar(rawMessage, pr.delay(),  pr.mode(), pr.conditions());
+
+        return clazz.cast(message);
+    }
+```
+> It is critical the method is named "deserialize", as the method is accessed via reflection. {style=warning}
+
+Here is a list of the helper methods:
+
+**parseString(String, String)**
+: Allows you to parse a string value from the serialized string data, and the key associated with the value to fetch.
+
+**parseArray(String, String)**
+: Allows you to parse a serialized JSON array. It is imperative the data is formatted as a json array or the parsing
+will fail. The main use case for this is the conditions every action has.
+
+**parseDouble(String, String)**
+: Allows you to parse a double value from the serialized string data, and the key associated with the double value.
+
+**parseBoolean(String, String)**
+: Allows you to parse a boolean value from the serialized string data, and the key associated with the double value.
+
+**parseFloat(String, String)**
+: Allows you to parse a float value from the serialized string data, and the key associated with the double value. This
+is almost the same as `parseDouble`, but it's a float instead.
+
+**parseEnum(String, String, Class<T>**
+: Allows you to parse an enum constant directly from the String data, the key, and the class of the enum type. This 
+will probably throw errors if the constant doesn't exist, so you may want to handle those.
+
+**parseInt(String, String)**
+: Allows you to parse an integer from the serialized string and key. Does basically what it sounds like.
+
+**parseBase(String)**
+: Parses 3 things. The delay (integer), the Condition SelectionMode (Condition.SelectionMode), and the conditions
+(List<Condition>). These three values are packaged into a ParseResult record. 
+
+Then when it comes to serialization, there is also a helper method to aid in that.
+> Do not include the "base" values of the action, (Delay, SelectionMode, or Conditions) as the plugin already handles 
+> this for you. {style=warning}
+
+```java
+    @Override
+    public String serialize() {
+        return generateSerializedString("ActionBar", Map.of("raw", rawMessage));
+    }
+```
+You should use the `generateSerializedString(String, Map<String, Object>)` method to generate your serialized strings.
+The first argument should be the same id used to register your action in the action registry. The keys used in the map
+are the exact keys used in the serialized action string.
+
+## Customizer Menu
+This is the point where I begin to glaze over things. This isn't a Lotus tutorial, but you should use 
+`Customnpcs.getInstance().getLotus()` as your lotus instance. But, you can use `MenuUtils.actionBase(action, player)`
+which will add a few buttons. These include the delay customizer, a go back button, and a confirm button. When you're
+done writing your menu class, make the `getMenu()` method return an instance of the menu.
+
+## Favicon
+The Action Favicon is similar to the Creation button, in that it is an item. It serves two purposes, it
+lets your users know the details of the action instance, and lets them edit the action. Here is ActionBar's 
+`getFavicon()` method. 
+```java
+    @Override
+    public ItemStack getFavicon(Player player) {
+        return ItemBuilder.modern(IRON_INGOT)
+                .setDisplay(Msg.translate(player.locale(), "customnpcs.favicons.actionbar"))
+                .setLore(Msg.translate(player.locale(), "customnpcs.favicons.delay", getDelay()),
+                        Msg.translate(player.locale(), "customnpcs.favicons.preview", Msg.format(getRawMessage())),
+                        Msg.format(getRawMessage().isEmpty() ? "<dark_gray><i>" + Msg.translatedString(player.locale(), "customnpcs.messages.empty_string") : getRawMessage()),
+                        Msg.format(""),
+                        Msg.translate(player.locale(), "customnpcs.favicons.edit"),
+                        Msg.translate(player.locale(), "customnpcs.favicons.remove")
+                ).build();
+    }
+```
+
+Your action will probably be cleaner, as you (probably) won't care about localization.
+
+## Performing the Action
+This is the part you probably care about, the part that makes your action, well..., an action. You achieve this by
+implementing the `perform()` method. Keeping up with the trend of internals, you won't have an API NPC object, but the 
+internal one. If this is a problem, the API NPC object has a constructor with an InternalNpc. On top of that, you
+should call the `processConditions(Player)` method as the first thing you do. I could probably come up with a way to 
+make this the default behaviour, at the cost of becoming opinionated. On top of that, rather than checking if the 
+server has PlaceholderApi, you can use the boolean field of the CustomNPCs class, `papi`. If its true, the server
+has PAPI installed, otherwise its false.
+
+```java
+    @Override
+    public void perform(InternalNpc npc, Menu menu, Player player) {
+        if (!processConditions(player)) return;
+        player.sendActionBar(Msg.format(CustomNPCs.getInstance().papi ? PlaceholderAPI.setPlaceholders(player, rawMessage) : rawMessage));
+    }
+```
+
+## Registering Your Action
+Before you try to use your shiny new action, you should probably register it. :)
+
+To do so, add it to the `CustomNPCs.ACTION_REGISTRY`.
+```java
+    CustomNPCs.ACTION_REGISTRY.register("ActionBar", ActionBar.class, ActionBar::creationButton);
+```
+
+> The ID specified must match the ID used in the serialize method. {style=warning}
+
+
+Tada! You now have made a custom Action!
diff --git a/Writerside/topics/customnpcs.md b/Writerside/topics/customnpcs.md
new file mode 100644
index 0000000..b83bc1c
--- /dev/null
+++ b/Writerside/topics/customnpcs.md
@@ -0,0 +1,3 @@
+# About CustomNPCs
+
+Start typing here...
\ No newline at end of file
diff --git a/Writerside/writerside.cfg b/Writerside/writerside.cfg
index b3d1129..89ee7a6 100644
--- a/Writerside/writerside.cfg
+++ b/Writerside/writerside.cfg
@@ -6,5 +6,5 @@
     <images dir="images" web-path="CustomNPCs-Docs"/>
     <categories src="c.list"/>
     <vars src="v.list"/>
-    <instance src="customnpcs.tree" version="1.6" web-path="customnpcs"/>
+    <instance src="customnpcs.tree" version="1.7"/>
 </ihp>
\ No newline at end of file
diff --git a/help-versions.json b/help-versions.json
deleted file mode 100644
index 4804bbf..0000000
--- a/help-versions.json
+++ /dev/null
@@ -1,4 +0,0 @@
-[
-  {"version":"1.6","url":"/v/1.6/","isCurrent":false},
-  {"version":"1.7","url":"/v/1.7/","isCurrent":true}
-]
\ No newline at end of file