Transmutation Builder
Transmutation Builder
Section titled “Transmutation Builder”The Transmutation Builder is an interactive tool that helps you create transmutation configuration files without writing JSON manually.
Features
Section titled “Features”- Visual Rule Builder: Create conversion rules with a user-friendly interface
- Condition Builder: Build complex logical conditions with AND/OR operators
- Operation Sequencer: Define operations in the correct order
- Live JSON Preview: See the generated JSON in real-time
- Validation: Ensures all required fields are filled correctly
- Export: Copy JSON directly to your configuration files
Using the Builder
Section titled “Using the Builder”Rule Information
Unique identifier for this conversion rule
Higher values = checked first (1000+: critical, 100-999: high, 0: default, -100: fallback)
Condition Builder
Define when this rule should match an item
Operations
Define transformations to apply (executed in order)
Generated JSON
1. Start with Priority
Section titled “1. Start with Priority”Set the priority first to understand where this rule will fall in the evaluation order:
1000+: Critical conversions100-999: High priority1-99: Normal0: Default (fallback rules)
2. Build Specific Conditions
Section titled “2. Build Specific Conditions”Use all conditions to ensure your rule only matches the items you intend:
{ "type": "all", "all": [ {"type": "component_exists", "path": "..."}, {"type": "component_equals", "path": "...", "value": "..."} ]}3. Sequence Operations Correctly
Section titled “3. Sequence Operations Correctly”Remember that operations execute in order:
- Copy or read data first
- Transform item ID
- Set new components
- Clean up old data last
4. Test Your Rules
Section titled “4. Test Your Rules”After generating JSON:
- Copy to
config/alchemy/transmutations/yourfile.json - Enable
logConversionsinconfig.json - Test with a few items first
- Monitor server logs for conversion messages
Common Patterns
Section titled “Common Patterns”Plugin Item Migration
Section titled “Plugin Item Migration”Condition: component_exists → path to plugin markerOperation 1: set_item_id_from_lookup → map old IDs to newOperation 2: remove_component → clean up plugin dataData Restructuring
Section titled “Data Restructuring”Condition: component_exists → old data locationOperation 1: set_component → create new structure with from_sourceOperation 2: remove_custom_data_key → remove old dataConditional Conversion
Section titled “Conditional Conversion”Condition: all → [exists check, equals check for type]Operation 1: set_item_id_from_component → use embedded new IDOperation 2: copy_component → preserve important dataOperation 3: remove_component → cleanupNext Steps
Section titled “Next Steps”- Example Configurations - See real-world examples
- Conditions Reference - All condition types
- Operations Reference - All operation types