23 lines
1.2 KiB
Markdown
23 lines
1.2 KiB
Markdown
---
|
|
tip_number: 46
|
|
date: 2026-09-20
|
|
category: crafting-ux
|
|
status: pending
|
|
---
|
|
|
|
# Tip #46 — Crafting Simulator
|
|
|
|
**Date:** 2026-09-20
|
|
**Category:** crafting-ux
|
|
**Source:** MC-Survival Wiki Daily Tip (cron @ 18:00 MESZ)
|
|
|
|
## Crafting Simulator
|
|
|
|
A crafting simulator is an in-browser 3x3 grid where players drag items in and instantly see which recipe (if any) they have built. It solves the recurring complaint that players cannot tell whether a recipe combination is valid without launching Minecraft and gathering the actual items. The signal is player behavior on the recipe detail page: most visits happen because a player is mid-game on another device and just wants to confirm a recipe before committing resources. Persisting the last grid in localStorage turns the simulator into a sticky scratchpad that keeps bringing players back.
|
|
|
|
## Implementation tips
|
|
|
|
1. Drag items from the picker into a 3x3 grid; server function looks up the matching shaped or shapeless recipe and shows the result.
|
|
2. Persist the last grid state in localStorage keyed by user-id (anonymous ok).
|
|
3. Show 'no match' with a 'Save as custom recipe' CTA for editors — a built-in user-to-content funnel.
|