Datapacks

Datapacks are neat little packages for loading content into Gophercraft Core.

Structure

Datapacks can either be plain folders, or compressed ZIP archives. As such, they can contain virtually anything.

Datapacks need to use UNIX-like directory paths if archived. (paths/like/this)

Pack.txt

Every pack should have a Pack.txt metadata file in the root directory. This file supplies important details like the datapack's name, and the author.

It's analagous to a go.mod file in a Go repository, or a package.json in a NodeJS module.

Pack.txt is encoded using the Gophercraft Text Format.

{
  Name example-datapack
  Description "Just an example"
  Author "The Gophercraft Developers"

  // Datapacks can depend on other datapacks.
  Depends
  {
    some-other-datapack
    // You can also select for Gophercraft versions:
    @gophercraft>=3.0
  }

  // Scripts to by run by Gophercraft Core. It's essentially a TOC, as it determines the load order.
  ServerScripts
  {
    ExampleScript.lua // Resolves to Scripts/ExampleScript.lua
  }
}