ValkyrieLib in Project Infinity 0.1

ValkyrieLib is in this pack at version 1.20.1-4.0.5.0, shipped as the Forge file valkyrielib-forge-1.20.1-4.0.5.0.jar. It has been there since version 0.0.45.4 or earlier, so it isn't a recent addition.^[1]

Unverified The sources I have don't describe what ValkyrieLib does, and there is no in-jar guidebook to check, so I can't say what it adds or whether it has any settings you can change.

Unverified The sources here show no recipe that produces this mod's items and no quest in the pack that involves it, so there is no confirmed first-item order to give you.

What the pack sets up for you

The one thing the sources show the pack configuring for this mod is its config file. Every option in it is set to true: ma:tab.bo:enabled, ma:tabz.bo:enabled and ma:workspace.bo:enabled. You don't need to change anything to get started.^[2]

Messages you may see

The mod's language file has status messages for a Builder and a Destructor: "Starting Builder", "Starting Destructor" and "Destructor Finished". The constructor can also report "Missing" when a component is not there.^[3]

If you see "Invalid player facing direction!", the mod suggests you try looking at a different side of the CCU. The destructor can also report "Cannot break block at position:" when it cannot remove a block.^[3]

ValkyrieLib is mostly a library, and the sources for this pack only show a small part of how it works. What they do show is some of the text it displays while a builder or a destructor runs, plus a few config switches.^[2][3]

Builder and destructor feedback

The mod has status messages for two processes. When a build begins you see "Starting Builder". A missing component is reported with the message "Missing". When a teardown begins you see "Starting Destructor", and when it is done you see "Destructor Finished".^[3]

The destructor can also fail on a block. In that case it reports "Cannot break block at position:" followed by the location, so you know which block stopped it.^[3]

Facing direction and the CCU

Direction matters when you use these processes. If you get "Invalid player facing direction!", the mod suggests you "Try looking at a different side of the CCU." So the side of the CCU you are looking at decides whether the action works.^[3]

Pack config

The pack's ValkyrieLib config file sets these options, and every one of them is true: ma:tab.bo:enabled, ma:tabz.bo:enabled and ma:workspace.bo:enabled.^[2]

This pack ships config for ValkyrieLib in a main file and a client file. The sources here don't show the mod's own defaults, so I can't tell you which values the pack changed. What I can give you is exactly what the pack sets.^[2][4]

Main config: valkyrielib.json

The main file is config/valkyrielib/valkyrielib.json. In this pack, every option in it is switched on:^[2]

• ma:tab.bo:enabled is set to true.^[2]
• ma:tabz.bo:enabled is set to true.^[2]
• ma:workspace.bo:enabled is set to true.^[2]

Client config: valkyrielib-client.json

The client file is config/valkyrielib/valkyrielib-client.json. The pack sets bo:generate_documentation to false, so that option is off here.^[4]