Custom origins
Adding your own custom origins is actually quite simple - all you need to do is create a copy of one of the origin files that already exist, and make your own changes.
The origins for the default Origins-Reborn plugin can be found in the folder ~/plugins/Origins-Reborn/origins/
- this is also where you put the .json
files when making your own custom origins.
For addon plugins such as Origins-Monsters, you can find custom origins added by these plugins in their respective plugin folders. For example, for Origins-Monsters, you can find the origins in ~/plugins/Origins-Monsters/origins/
.
If you want to delete any existing origins you can do that too - just delete the corresponding origin file in the folder.
You can configure different settings for your custom origins. These are the settings you can configure on each origin:
Required settings:
"powers" - the powers the origin has. See here for a list of powers, and information on how to make or request custom powers.
"icon" - the icon used to represent the origin.
This uses a subsection where you can specify the icon and (optionally) custom model data.
"order" - the 'order' of the origin - this determines what position it shows up in the origin selection GUI relative to other origins with the same impact.
"impact" - the 'impact' of the origin - this determines the appearence of the traffic light symbols you see in the top right hand corner of the origin selection GUI, which represent how much the origin changes gameplay.
Impact also influences how origins are ordered in the GUI, which origins with a higher impact always appearing after ones with a lower impact.
"description" - The description of the origin. This is used as the text that appears below the origin's name in the GUI.
Optional Settings:
"name" - the name of the origin. If not specified, the origin will be named whatever the file is named without the .json ending (e.g. an origin file named 'arachnid.json' will make an origin named Arachnid)
"max" - the maximum number of players that can have this origin before it stops being selectable. If not specified, this defaults to the value specified in the config.yml. If that value is not changed, there is no limit on the number of players that can have the origin.
"layer" - the 'layer' the origin appears on. By default this is 'origin'. Read more about layers and what they do here.
"cost" - the Vault cost of this origin. Only applicable if you have Vault enabled in the config.yml. If this value is not specified it will default to the cost specified in the config.yml.
"permission" - the permission required to choose this origin. If not specified, anyone can choose this origin, as long as it is not unchoosable.
"unchoosable" - whether the origin can appear in the Origin selection GUI. By default this is
false
. If this value is set totrue
, the origin will not appear in the GUI, but can be applied by admins using the /origin set command."priority" - a number representing how 'important' this origin is in relation to origins with the same file name.
This is only needed when making custom plugins that implement the same origins as others, but want to change them
One example of this being used is in Origins-Monsters, which adds the same 'drowned' origin as Origins-Mobs, but makes it unchoosable and instead is selected when a player with the 'zombie' origin drowns, so overrides the one in Origins-Mobs using a higher priority.
Example Configuration
Here is an example configuration for a custom origin:
Last updated
Was this helpful?