Resource Packs

IgnisCore auto-generates a resource pack from loaded extension textures and custom model data assignments.

How it works

1. Extensions ship PNG textures in their JARs
2. On load or reload, IgnisCore merges textures into a pack
3. An embedded HTTP server serves the pack at the configured public URL
4. Clients receive the pack URL on join (or via /ignis pack)

Rebuild and apply

Players can trigger a rebuild in-game:

/ignis pack

Admins can reload everything (extensions + pack):

/ignis reload all

Debug

/ignis debug pack

Shows latest pack hash, registered block model mappings, and the configured public URL.

Configuration

Key	Purpose
resource-pack.host	Bind address for pack server
resource-pack.port	TCP port
resource-pack.public-url	URL sent to clients

Ensure public-url is reachable from player machines — often a public IP or reverse proxy, not localhost.

Related

• Configuration — server config reference
• Troubleshooting — pack not updating
• Commands — /ignis pack and /ignis debug pack