Remove gitbook from repo.

Add library support.

Author: Moderocky

README.md

@@ -1,6 +1,5 @@
 ---
-description: A short introduction to ByteSkript, its uses, goals and applications.
-coverY: 0
+description: A short introduction to ByteSkript, its uses, goals and applications. coverY: 0
 ---
 
 # 🎶 Introduction to ByteSkript
@@ -13,14 +12,16 @@ An experimental language based on Skript (with no pre-eminent DSL dependencies)
 
 ### Visit the [documentation](https://moderocky.gitbook.io/byteskript/) and wiki [here](https://moderocky.gitbook.io/byteskript/).
 
-ByteSkript draws heavily from the original [Skript](https://github.com/SkriptLang/Skript/) language design, with some minor structural adaptations to strengthen the language grammar, to remove some unnecessary jargon and make the language more reliable. ByteSkript also increases interoperability with existing JVM languages.
+ByteSkript draws heavily from the original [Skript](https://github.com/SkriptLang/Skript/) language design, with some
+minor structural adaptations to strengthen the language grammar, to remove some unnecessary jargon and make the language
+more reliable. ByteSkript also increases interoperability with existing JVM languages.
 
 {% hint style="info" %}
 **ByteSkript is not affiliated with** [**SkriptLang**](https://github.com/SkriptLang/Skript/)**.**\
-ByteSkript is a completely **new** implementation of the general guide and style of the 'Skript' language, with its own language specification, goals and licence.
+ByteSkript is a completely **new** implementation of the general guide and style of the 'Skript' language, with its own
+language specification, goals and licence.
 
-For clarity: SkriptLang's Skript implementation will be referred to as 'original' or 'minecraft' Skript.
-{% endhint %}
+For clarity: SkriptLang's Skript implementation will be referred to as 'original' or 'minecraft' Skript. {% endhint %}
 
 ### Goals
 
@@ -44,7 +45,9 @@ For clarity: SkriptLang's Skript implementation will be referred to as 'original
    The layout, look, readability and core language components should keep parity with original Skript.\
    Some small changes will be made to improve readability and compile accuracy.
 
-Skript is designed to be beginner-friendly. Ideally, a user with no experience should be able to read Skript code and understand its function. All instructions are written in basic English, avoiding niche programming terms and symbols wherever possible.
+Skript is designed to be beginner-friendly. Ideally, a user with no experience should be able to read Skript code and
+understand its function. All instructions are written in basic English, avoiding niche programming terms and symbols
+wherever possible.
 
 ## Using ByteSkript
 
@@ -62,68 +65,76 @@ Running these for the first time will create special folders in the run director
 
 This is the simplest resource, used for loading (and running) user-created script files.
 
-Raw script files can be written and placed in the `skript/` folder. All scripts will be loaded internally, but no classes or jar files will be written.
+Raw script files can be written and placed in the `skript/` folder. All scripts will be loaded internally, but no
+classes or jar files will be written.
 
 The `on [script] load` event will be triggered for each script as an entry point.
 
-{% hint style="success" %}
-The ByteSkript compilers, language specification and compile-time API are available in this resource, so advanced scripts may use dynamic loading to load extra skript code written at runtime!
+{% hint style="success" %} The ByteSkript compilers, language specification and compile-time API are available in this
+resource, so advanced scripts may use dynamic loading to load extra skript code written at runtime!
 {% endhint %}
 
 ### SkriptClassCompiler
 
-This resource is used for generating compiled JVM `.class` files for each script in the `skript/` folder. The classes produced by this are not directly executable, but may be useful for sharing and special loading.
+This resource is used for generating compiled JVM `.class` files for each script in the `skript/` folder. The classes
+produced by this are not directly executable, but may be useful for sharing and special loading.
 
 The compiled scripts will **not** be loaded or run.
 
 ### SkriptJarBuilder
 
-This resource builds an executable jar containing all of the user-created scripts, resources and the ByteSkript runtime (`skript` namespace and functions.)
+This resource builds an executable jar containing all of the user-created scripts, resources and the ByteSkript
+runtime (`skript` namespace and functions.)
 
 \
-This output jar can be run with `java -jar JarName.jar` and is distributable - it does not need anything as a dependency.
+This output jar can be run with `java -jar JarName.jar` and is distributable - it does not need anything as a
+dependency.
 
-When executing this jar, all scripts will be loaded and the `on [script] load` event will be triggered for each script as an entry point.
+When executing this jar, all scripts will be loaded and the `on [script] load` event will be triggered for each script
+as an entry point.
 
-{% hint style="danger" %}
-The ByteSkript standard compiler and compile-time API are **not** added to the output jar.
-{% endhint %}
+{% hint style="danger" %} The ByteSkript standard compiler and compile-time API are **not** added to the output jar. {%
+endhint %}
 
-{% hint style="success" %}
-The dynamic function on-the-fly compiler **is** available in this jar, so dynamic function calls are available.
-{% endhint %}
+{% hint style="success" %} The dynamic function on-the-fly compiler **is** available in this jar, so dynamic function
+calls are available. {% endhint %}
 
 ## Language Libraries
 
-Due to its fixed nature, the Skript language has always relied on third-party add-ons to add new syntax and functionality for specific areas.
+Due to its fixed nature, the Skript language has always relied on third-party add-ons to add new syntax and
+functionality for specific areas.
 
 ByteSkript achieves this through libraries, which can register compile-time and run-time functionality.
 
-There are two provided syntax APIs, labelled `v1` and `v2`. Both are available and easily accessible, but may be suited to different tasks.
+There are two provided syntax APIs, labelled `v1` and `v2`. Both are available and easily accessible, but may be suited
+to different tasks.
 
-Within the set of built-in functions in the `skript` namespace are some for accessing JVM resources which can be used to build more advanced functionality.
+Within the set of built-in functions in the `skript` namespace are some for accessing JVM resources which can be used to
+build more advanced functionality.
 
 ### API v1
 
-The `v1` syntax API offers complete control of syntax, including writing bytecode instructions, look-aheads, additions, etc.
+The `v1` syntax API offers complete control of syntax, including writing bytecode instructions, look-aheads, additions,
+etc.
 
-However, it also requires creating and individually registering (fairly complex) classes to add new syntax and language structures.
+However, it also requires creating and individually registering (fairly complex) classes to add new syntax and language
+structures.
 
-This is the most powerful syntax API, as it allows control of the result code at the VM-bytecode level for experienced users. It is recommended for adding entirely new language structures or features with excessively-variable layouts.
+This is the most powerful syntax API, as it allows control of the result code at the VM-bytecode level for experienced
+users. It is recommended for adding entirely new language structures or features with excessively-variable layouts.
 
-{% hint style="info" %}
-The implicit array creation syntax `(a, b, ...)` has to use the v1 API to create variable-size arrays.
-{% endhint %}
+{% hint style="info" %} The implicit array creation syntax `(a, b, ...)` has to use the v1 API to create variable-size
+arrays. {% endhint %}
 
 ### API v2
 
 The `v2` syntax API is significantly easier to use, but offers much less control over syntax.
 
-Syntax methods are given an annotation, and the class they belong to is registered to a library. This API is much more suitable for property syntax, where creating a class for each one would be excessive.
+Syntax methods are given an annotation, and the class they belong to is registered to a library. This API is much more
+suitable for property syntax, where creating a class for each one would be excessive.
 
-{% hint style="info" %}
-The v2 API is used internally by all of the I/O handler syntax. A lot of these are also forced to extract or bridge.
-{% endhint %}
+{% hint style="info" %} The v2 API is used internally by all of the I/O handler syntax. A lot of these are also forced
+to extract or bridge. {% endhint %}
 
 ### Libraries Used
 

SUMMARY.md

@@ -12,6 +12,7 @@
     <properties>
         <maven.compiler.source>17</maven.compiler.source>
         <maven.compiler.target>17</maven.compiler.target>
+        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
     </properties>
 
     <build>
@@ -102,12 +103,6 @@
             <version>9.2</version>
             <scope>compile</scope>
         </dependency>
-        <dependency>
-            <groupId>mx.kenzie</groupId>
-            <artifactId>glass</artifactId>
-            <version>1.0.0</version>
-            <scope>compile</scope>
-        </dependency>
         <dependency>
             <groupId>mx.kenzie</groupId>
             <artifactId>mimic</artifactId>