slipcor · g3forcemc · May 17, 2021 · May 17, 2021 · May 17, 2021 · May 27, 2021
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,23 @@
+---
+name: Bug report
+about: Report an error or something that doesn't work correcty
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+Describe what happened and what you were trying to do.
+
+**Reproduction steps**
+Describe the context of the bug. Did it happen during a match, in the lounge or out of an arena? If it was during a match, with which goal and how many teams/players? Is there a specific action to do in order to trigger the error?
+
+**Additional elements**
+If applicable, add screenshots, log extract (between two lines of ` ``` `), or additional information to help explain your problem.
+
+**Config information**
+- Server software and version: [e.g. Paper 1.20.4]
+- Java Version: [e.g. 17]
+- PVPArena version: [e.g. 1.15.4-SNAPSHOT-b1]
+- [If necessary: affected module and its version]
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,11 @@
+---
+name: Feature request
+about: Suggest an idea for enhancing PVPArena
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+**Describe the solution you'd like**
+A clear and concise description of what you want and why.
diff --git a/.gitignore b/.gitignore
@@ -8,4 +8,6 @@ dependency-reduced-pom.xml
 
 
 /bin/
-/.settings/
+/.settings/
+/.classpath
+/.project
diff --git a/LICENSE b/LICENSE
diff --git a/doc/commands.md b/doc/commands.md
@@ -19,12 +19,13 @@ Click on a command to get its syntax, usage examples and more information about
 Command | Shorthand | Definition
 ------------- | ------------- | -------------
 [/pa debug](commands/debug.md) | /pa !d | Debug nodes
+/pa duty | /pa !du | Toggle your shortcuts override status
 [/pa modules](commands/modules.md) | /pa !mi | Manage modules
 [/pa reload](commands/reload.md) | /pa !r | Reload arena configs
 
 ## Arena Administration Commands
 
-> ℹ Permission: pvparena.admin OR both ownership and pvparena.create
+> ℹ Permission: pvparena.admin OR both ownership of an arena and pvparena.create
 
 Command | Shorthand | Definition
 ------------- | ------------- | -------------
@@ -39,6 +40,7 @@ Command | Shorthand | Definition
 [/pa forcewin](commands/forcewin.md) | /pa !fw | Force a player/team to win.
 [/pa gamemode](commands/gamemode.md) | /pa !gm | Change the general gamemode of an arena
 [/pa goal](commands/goal.md) | /pa !g | Manage arena goals
+[/pa playerclass](commands/playerclass.md) | /pa !pcl | Manage player classes
 [/pa playerjoin](commands/playerjoin.md) | /pa !pj | Make a player join
 [/pa protection](commands/protection.md) | /pa !p | Manage arena protections
 [/pa region](commands/region.md) | /pa !rg | Manage arena regions
@@ -75,4 +77,4 @@ Command | Shorthand | Definition
 [/pa ready](commands/ready.md) | /pa -r | Ready you up or list who is ready
 /pa spectate | /pa -s | Spectate an arena
 [/pa stats](commands/stats.md) | /pa -s | Show [arena/global] statistics
-/pa version | /pa -v | Show detailed version information
+/pa version | /pa -v | Show detailed version information
diff --git a/doc/commands/playerclass.md b/doc/commands/playerclass.md
@@ -0,0 +1,21 @@
+# Playerclass command
+
+## Description
+
+This command manages the player class for an arena. You can use it to edit and remove (clear) it, but you cannot show it.
+
+## Usage
+
+Command |  Definition
+------------- | -------------
+/pa [arena] playerclass save    | Save your inventory to the class items of your player class
+/pa [arena] playerclass remove  | Remove a player class
+
+Example: use `/pa temp playerclass save` to save your inventory to your player class of the arena "temp"
+
+> **🚩 Tip:**  
+> Type `/pa leave` to leave class preview
+
+## Hazards
+
+You shouldn't do that when a game is running, and make sure that you /pa reload afterwards.
diff --git a/doc/commands/setowner.md b/doc/commands/setowner.md
@@ -1,11 +1,11 @@
 # Setowner Command
 
-##Description
+## Description
 
-This command hands over ownership. This has to be either "%server%" or a player name. Note that the player name is 
+This command hands over ownership. This has to be either "%server%" or a player name. By default every arena created by a player with permission `pvparena.admin` is owned by the server. Note that the player name is 
 NOT checked, but you can verify it with [`/pa info`](../commands.md#arena-standard-commands)
 
-##Usage Examples
+## Usage Examples
 
 Command |  Definition
 ------------- | -------------

diff --git a/doc/commands/spawn.md b/doc/commands/spawn.md
@@ -17,12 +17,18 @@ Example:
 
 ## Details
 
-There are two syntax according to the [gamemode](gamemode.md) of your arena : 
-- If you're using a "free" arena, you can define unlimited spawns using syntax `/pa myArena spawn spawnX` where X should
- be anything (word, digit, letter, etc).
-- If your arena works with teams, you have to use `/pa myArena spawn teamspawn` where "team" is the name of one of your 
-team.
+There are two syntaxes for the spawns for the fight, depending on the [gamemode](gamemode.md) of your arena: 
+- if you're using a "free" arena, you can define unlimited spawns using syntax `/pa myArena spawn spawnX` where X can
+ be anything (word, digit, letter, etc.)
+- if your arena works with teams, you have to use `/pa myArena spawn teamspawn` where "team" is the name of one of your 
+teams
 
+Then you must have lounge spawns:
+- in the "free" gamemode: just one spawn named `lounge`
+- in the "team" gamemode: one spawn for each team with the syntax `teamlounge` where "team" is the name of the 
+team
+
+In addition to these spawns, every arena must have "exit" and "spectator" spawns.
 
 If you get a message "spawn unknown", this is probably because you did not install/activate a [goal](../goals.md) or 
 a [module](../modules.md). 
@@ -36,4 +42,4 @@ You can define unique offsets for each spawn name, in order to not be placed on
 - `/pa [arena] spawn [spawnname] offset X Y Z`
 
 For example 0.5 0 0.5 as X Y Z would work setting you on an edge. 
-You might want to keep F3 at hand to see if you actually have to add or subtract to get to the right edge.
+You might want to keep F3 at hand to see if you actually have to add or subtract to get to the right edge.
diff --git a/doc/configuration.md b/doc/configuration.md
@@ -34,7 +34,7 @@ general:
   leavedeath: false #Kill the player on battleground leaving
   lang: none
   owner: server #Set owner of the arena
-  regionclearexceptions: [] #List of regions where entities are not cleared
+  regionclearexceptions: [] #List of entities that must not be cleared from arena regions, editable with '/pa regionclear' command
   quickspawn: true #Spawn all players at the same time. If false, spawn player one by one.
   prefix: MyArena #Name of the arena displayed in chat messages
   showRemainingLives: true #Brodcast ramaning lives in chat
@@ -53,6 +53,7 @@ goal:
 items:
   keepAllOnRespawn: false #Keep inventory on respawn
   excludeFromDrops: none #List of items not dropped on kill
+  onlyDrops: none #List of only items dropped on kill
   keepOnRespawn: none #List of items kept on respawn (if keepAllOnRespawn is disabled)
   minplayers: 2 #Minimum number of players to start fighting
   random: true
@@ -201,4 +202,4 @@ spawns:
   spawn2: world,863,58,-1007,0,0
   spawn3: world,853,58,-997,-90,0
   spawn4: world,863,58,-987,180,0
-```
+```
diff --git a/doc/faq.md b/doc/faq.md
@@ -44,6 +44,21 @@ an arena, use the command `sudo @p pa leave`.
 
 <br>
 
+## How to create a join sign for an arena?
+
+Create a simple sign with the following pattern:
+```
+[arena]
+yourArenaName
+teamName
+
+```
+
+You can keep the third line empty to join a random team.
+The fourth line can still be empty or filled with a custom message.
+
+<br>
+
 ## How to regen my battlefield after a game?
 
 Currently, there are two ways to regen battlefield after a match. You can use either 
@@ -70,6 +85,19 @@ Just set `tp.death` to `spectator` in your arena config file (or with [`/pa [are
 
 <br>
 
+## Is it possible to automatically affect a class to all players or to a specific team?
+
+Yes it is. In your arena config, you can set the `autoclass` the setting according to your needs:
+* Use `None` if you don't want to use the auto-class mechanism. (default option)
+* Write a simple class name, to affect the class to everyone.  
+  Ex: `autoclass: pyro`
+* Use the following pattern to affect a class to each team:  
+  `autoclass: teamName1:classNameA;teamName2:classNameB`
+
+NB: For the 3rd option, you have to specify a class for each team. There is no default choice.
+
+<br>
+
 ## Still have questions?
 
 Don't hesitate to [get in touch](../readme.md#support) with us 😉
diff --git a/doc/mods/betterfight.md b/doc/mods/betterfight.md
@@ -28,7 +28,7 @@ Case does not matter :)
 
 ## Commands
 
-- `/pa [arena] !bf messages [number]` \- set message for [number]th kill
+- `/pa [arena] !bf messages [number] [message]` \- set message for [number]th kill
 - `/pa [arena] !bf items [items]` \- set an item string to add deadly items ("fireball,snowball,arrow")
 - `/pa [arena] !bf reset` \- toggle killstreakondeath reset 
 

diff --git a/doc/mods/items.md b/doc/mods/items.md
@@ -22,6 +22,8 @@ Now set as many item spawning places as you want: `/pa [arena] spawn itemX`
 - items \- the items to choose from
 - interval \- spawn interval in seconds 
 
+> 🚩 You can set items with the [set](https://github.com/Eredrim/pvparena/blob/master/doc/commands/set.md) command (`inventory` or `hand`)
+
 ## Commands
 
 \-