The extra fields can be used for data to pass to that custom function. Sometimes it will be defined in stonehearth/jobs/base_job.lua instead, since all jobs inherit from it. This 'type' is the name of a function defined in the job's controller file. If the perk involves something more elaborate, it will have a 'type' field plus any additional custom fields for data. If the perk consists in something that is automatically controlled by other files (such as unlocking recipes - each recipe defines at which level it will get unlocked) no extra fields are needed. The 'id' is an identifier used to perform checks in Lua when we need to know whether a hearthling has unlocked a perk or not. The minimum fields are 'name', 'id', 'icon', 'description' and 'level'. They all consist of an array of JSON objects. The way job perks from the job_description.json file work is: E.g.: 'controllers': - the list of job perks for this job. The existing jobs are inside the stonehearth/jobs directory.Īdd an alias for your custom job in your manifest, pointing to the JSON file that contains the description of the job.Īdd an alias in the 'controllers' section of your manifest, pointing to the Lua file of your job.

Preferably one that is most close in functionality to what you're creating.

These are generic steps for creating a new job:Ĭopy an existing job from the stonehearth mod. We can create our own jobs / classes and alter the existing promotion tree to suit our preferences.

Stonehearth steam mods not showing up