Creating Objects in DDAPI
Objects can be created by defining a config file in mod/hammerstone/objects/<name>.json
Use Cheats
When testing your mods, it's very useful if you can quickly inspect and cheat in items. Since you've already started using Hammerstone, you might as well pull in Creative Mode as well for development.
Hello World example
Here is a simple example which creates a linked resource
and object
. It references base-game models, so you can safely copy/paste directly into your mod. After adding this file, the new item should appear in game.
This will create a new item called coconut_2
, which you can spawn and decorate with. It can be picked up and stored with the other coconuts (link to storage), but it has no other behaviors (cannot be eaten, or rot, or crafted with).
{
"hammerstone:object_definition": {
"description": {
"identifier": "coconut_2"
},
"components": {
"hs_object": {
"model": "coconut"
},
"hs_resource": {
"storage_identifier": "coconut"
}
}
}
}
Game Objects vs Resources
There are two main lists of items in Sapiens, with huge crossover:
gameObject.lua
defines a list of distinct objects such asapple
andbirchBranch
andpineBranch
resource.lua
defines object categories such asapple
orbranch
The general rule is that game objects are linked to resources. i.e., every branch in Sapiens is part of the branch
resource. For simple objects, like coconut
, it's fully expected that it will be defined as both a gameObject
and a resource
.
Here is a quick refresher:
Game Object
- Can be spawned
spawn(...)
- Exists physically in the world (has a model)
- Contains properties like physics, model scale
- How object transforms when eaten (i.e., meat -> bone)
Resource
- Defines how the object is stored/carried (i.e., all branches have same storage definition)
- Defines food nutrition
- Can be crafted with (i.e., you don't craft with a
birchBranch
you craft with abranch
-the game figures the rest out)
Schema
Refer to the JSON schema for all the possible values.