Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
MythicCrucible MythicCrucible
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 56
    • Issues 56
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • MythicCraft
  • MythicCrucibleMythicCrucible
  • Wiki
  • ResourcePack Generator

ResourcePack Generator · Changes

Page history
added examples for Furniture/ blocks, added context and updated filetree example authored Oct 17, 2023 by LcorpOfficial's avatar LcorpOfficial
Show whitespace changes
Inline Side-by-side
Showing with 74 additions and 22 deletions
+74 -22
  • ResourcePack-Generator.md ResourcePack-Generator.md +74 -22
  • No files found.
ResourcePack-Generator.md
View page @ 7ef8cab9
# Introduction # Introduction
The ResourcePack Generator feature allows you to generate a resourcepack from the items and blocks you have configured.
Crucible can be used to automatically generate some assets from item configurations to be drop-in ready for deployment to a resource pack!
The Generation logic will:
- auto-detect if the path points to a json or bbmodel file.
- If it's a bbmodel it will automatically extract the textures, mcmeta, and other relevant data
- Will generate any necessary atlases
- The Generation fields also work on furniture and furniture states
# Usage # Usage
## Generate the Resourcepack
This can be done via the use of the `/crucible generate` command This can be done via the use of the `/crucible generate` command
## Configure the Items
Generation settings are configured on the item. If no textures are specified, it will attempt to read the model and derive the textures from that
```yaml
GolfPutter:
Material: IRON_HOE
Model: 1
Display: 'TGolf Club (Putter)'
Generation:
Model: item/clubs/putter
Textures: # this is optional
- item/clubs/putter
```
# Packs # Packs
Packs can now contain an "Assets" folder with the following layout Packs can now contain an "Assets" folder with the following layout:
``` ```
Pack Pack
|-- Assets |-- Assets
|-- blueprints (for bbmodels, not implemented yet) |-- models (.json or .bbmodel files, can use subfolders to organize)
|-- models (json model files) |-- textures (textures, can use subfolders to organize)
|-- textures |-- sounds (.ogg sound files, can use subfolders to organize)
|-- sounds
``` ```
The contents of these folders should be similar to an actual resource pack. In the example item, it would copy the texture file `Assets/textures/item/clubs/putter.png`. The contents of these folders should be similar to an actual resource pack. In the example item [HERE](#items), it would copy the texture file `Assets/textures/item/clubs/putter.png`.
Items will be generated **using the configured Material and Model numbers**, and will output a warning if duplicates are detected. Items will be generated **using the configured Material and Model numbers**, and will output a warning if duplicates are detected.
...@@ -39,3 +33,61 @@ The structure of the sounds folder will be used to generate a sounds.json. ...@@ -39,3 +33,61 @@ The structure of the sounds folder will be used to generate a sounds.json.
If there are multiple numbered sounds, it will add those all as random options to the same sound e.g. growl1.ogg, growl2.ogg If there are multiple numbered sounds, it will add those all as random options to the same sound e.g. growl1.ogg, growl2.ogg
All assets are generated in the `mythic:` namespace to avoid conflicts, including with custom blocks now (the sound mechanic will automatically detect these sounds so adding it manually isn't necessary) All assets are generated in the `mythic:` namespace to avoid conflicts, including with custom blocks now (the sound mechanic will automatically detect these sounds so adding it manually isn't necessary)
## Configure the Items
Generation settings are configured on the item. If no textures are specified, it will attempt to read the model and derive the textures from that.
## Example Usage
### Furniture
```yml
TestGeneration5:
Material: LEATHER_BOOTS
Model: 10
# ^^^ The CustomModelData ID for the Material to use.
# In this case, the model generated will be
# LEATHER_BOOTS with a CustomModelData ID of 10.
Display: 'Test Generation 5'
Generation: item/toilet
# ^^^ This denotes the file structure for the item's model to be placed.
Type: FURNITURE
Furniture:
Type: DISPLAY
Material: BRICK
Model: 11
# Furniture states are also accounted for in the same way.
# For example, item/toilet would be BRICK CMD 11
Generation: item/toilet
States:
UH_OH:
Model: 12
Generation: item/toilet_flushed
# And this would be BRICK CMD 12
```
### Items
```yml
GolfPutter:
Material: IRON_HOE
Model: 1
Display: 'TGolf Club (Putter)'
Generation:
Model: item/clubs/putter
# The json or bbmodel file named "putter" in the pack
# if no Model is defined, it will default to an extruded texture (think diamonds)
Textures:
- item/clubs/putter
# Textures is optional, best for if there is more than 1 texture on a model.
```
### Blocks
```yml
CustomBlock:
Type: MUSHROOM_BLOCK
Id: 18
Texture: block/stars1
# The texture here will default to a generic block with the texture on all sides.
```
\ No newline at end of file
Clone repository
  • Home
  • Changelogs
  • Commands / Permissions
  • FAQ / Common Issues
Usage
  • Installation
  • Item Options
  • Item Skills
  • Item Durability
  • Custom Blocks
  • Furniture
    • Paint Brush
  • Crafting Recipes
  • Custom Bags
  • Ammo System / Guns
  • Dynamic Lore Generation - WIP
  • ResourcePack Generator - WIP
New Mechanics
  • Item Mechanics
  • Item Targeters
  • Item Triggers
  • Item Conditions
New Placeholders
  • Placeholders
  • Placeholders.yml