Custom Textures and Resource Packs

TypicalWaypoint generates a resource pack from files under plugins/TypicalWaypoint/. The generated pack contains item models, processed textures, atlas data, shader files, and an overlay for newer client formats.

First generated files

On setup, the plugin seeds defaults when needed:

• plugins/TypicalWaypoint/waypoints/waypoint_circle.png
• plugins/TypicalWaypoint/shaders/core/rendertype_item_entity_translucent_cull.vsh
• plugins/TypicalWaypoint/shaders/core/rendertype_item_entity_translucent_cull.fsh
• plugins/TypicalWaypoint/shaders/typicalwp_26_1_2/core/item.vsh
• plugins/TypicalWaypoint/shaders/typicalwp_26_1_2/core/item.fsh

Add a texture

1. Put a PNG in plugins/TypicalWaypoint/waypoints/.
2. Use a filename that can become a model id. Letters, numbers, dots, underscores, and dashes are safest.
3. Run /waypoint pack.
4. Use the model id with /waypoint set <name> [waypointTexture].

Example:

plugins/TypicalWaypoint/waypoints/dungeon_exit.png

Command:

/waypoint set exit dungeon_exit

The plugin lowercases the filename, replaces unsupported characters with underscores, collapses repeated underscores, and removes leading or trailing underscores.

Build outputs

/waypoint pack writes two outputs:

• Zip: path from resource-pack-output-path, default plugins/TypicalWaypoint/build.zip.
• Exploded folder: always plugins/TypicalWaypoint/build/.

The success message includes both paths and the number of model ids included.

Texture processing

Every source PNG is processed before it enters the pack. The plugin writes a sentinel pixel into the top-left pixel so the shader can recognize waypoint textures. Keep source textures as valid PNG files.

Bundled defaults for developers

The repository includes waypoint-pack/ for authored pack assets and src/main/resources/resource-pack-defaults/ for runtime defaults bundled in the plugin jar. When changing default assets in code, keep both trees in sync.