Datapack System

Valkyrien Skies has a few built-in datapack systems that can be used to tweak its functionality or provide extra compat.

To start off with, you will need a datapack. The Minecraft wiki has a tutorial on the basics of setting one up here.

Valkyrien Skies currently has 3 datapack features. Being able to modify block properties (mass, friction, etc), being able to modify entity behaviour (teleported out the shipyard, or not. Commonly used for compat with modded entities), and being able to specify dimension properties (atmosphere and gravity, used by addons for calculations).

You can find a utility for creating these VS datapack files at https://cosmic-mod-generator.github.io

Block Properties

You can modify the weights of blocks already specified by Valkyrien Skies (you can see which weights it specifies here) by using the priority fields (like in the below example). Higher values have higher priority, with VS having a priority of 100. A priority of 101 is usually enough for most packs.

The files to specify block mass will be placed in your datapack as the following:

The file format is as follows:

 [
   {
     "block": "minecraft:block",
     "mass": 0.0,
     "priority": 101
   },
   {
     "block": "mynamespace:myblock",
     "friction": 0.0,
     "no_collision": true
   },
   {
     "tag": "namespace:myblocktag",
     "mass": 0.0,
     "friction": 0.0,
     "elasticity": 0.0,
     "priority": 101
   }
 ]

You can get an example datapack here with all the values filled out, just make sure to replace the names when you make your own: example datapack download

To apply changes, you’ll need to restart minecraft.

Shipyard Entities

Most entities in the shipyard are automatically teleported to where they should be relative to the ship. However, this doesn’t work with all entities. Some entities (for example, paintings and item frames) need to stay in the shipyard for them to work properly. To account for this, VS allows you to specify certain entities to stay in the shipyard. This isn’t recommended for most entities, it won’t magically fix their pathfinding or anything and can often lead to more issues with them, but for some entities it’s just what they need.

The files to specify an entities handler will be placed in your datapack as the following:

You can get the entities namespace and name by looking at the “targeted entity” section of the F3 menu while looking at the entity (it will be written as namespace:entity_name).

The file format is as follows:

An example file:

{
  "handler": "valkyrienskies:shipyard"
}

Currently in Valkyrien Skies there are only two handlers, valkyrienskies:shipyard and valkyrienskies:default. Most entities are default by default, meaning they will be teleported outside the shipyard. There is one exception to this however. If the entity registry name (aka the name you use for the json file) has seat or chair, or its class name contains SeatEntity, its default behavior will be shipyard instead. This is to try and add some ‘automatic’ compat with most modded seat entities. If this breaks one of your entities however, you can simply override this behavior for your entity by setting its handler to default.

Dimension Properties

As of update 2.4.0, Valkyrien Skies has an atmospheric system. This means ships are affected by drag in the air, instead of simply moving forever if they have no gravity. 2.4.0 also introduces a unified per-dimension gravity system, so that addons don’t conflict with their own. These systems are both configurable with a datapack file.

The files to specify the dimension properties will be placed in your datapack as the following:

The file format is as follows:

An example file:

{
  "dimensionId": "minecraft:dimension:minecraft:overworld",
  "maxYPos": 1000,
  "seaLevel": 62,
  "gravity": [0.0, -10.0, 0.0],
  "priority": 2
}