This document explains the end-to-end process from the perspective of a player (Steve) using the Model-Driven App within the Minecraft-themed procurement and crafting system.
1. Player Login (Steve)
Steve is a player (user) who logs into the Model-Driven App. From here, Steve can manage Projects, Recipes, Crafting requests, and track all activities.
2. Creating a Project
Steve creates a new Project. A Project represents a request for a specific item or component that needs to be sourced or crafted.
Within the Project, Steve specifies:
- Deadline (when bids should close)
- Budget (in Emeralds 🟩 / EM)
- Recipe or Component required
3. Publishing the Project
Once all Project details are complete, Steve publishes the Project, changing its status from Draft to Open. Publishing makes the Project visible to Vendors via the Power Page (Power Page will not be covered here).
4. Vendors: Villagers & Wandering Traders
Vendors are external parties who interact with the system via the Power Page. There are two types of Vendors:
- Villagers: Crafters and shippers who can manufacture (print) and deliver items.
- Wandering Traders: Providers of Recipes or Components, offering 3D-printable designs.
5. Bids (Handled via Power Page)
Wandering Traders can view published Projects on the Power Page and place Bids. A Bid includes the price for providing the requested Recipe or Component.
Although Bids are created through the Power Page, all Bid records and statuses are visible to Steve in the Model-Driven App.
6. Selecting a Winning Bid
Once the deadline has passed, or earlier if Steve is satisfied, Steve selects a winning Bid.
The selected Bid determines which Wandering Trader will provide the Recipe or Component.
7. Contract Creation & Signing
After a Bid is selected, a Contract is automatically created and sent to the winning Wandering Trader for signing.
The Contract formalizes the agreement, including price, delivery expectations, and terms.
8. Receiving the Recipe / Component
Once the Contract is completed, Steve receives the Recipe or Component. At this point, Steve has two options:
- Print / craft the item themselves.
- Request a Villager to craft and ship the item.
9. Creating a Crafting Record
If Steve cannot or does not want to craft the item personally, they create a Crafting record.
In the Crafting record, Steve specifies:
- The Recipe to be crafted
- The selected Villager
- Shipping details (not yet implemented)
Villagers will charge an additional fee for crafting and shipping, which is tracked within the system.
10. Visibility & Tracking
Although Villagers and Wandering Traders primarily use the Power Page, all records, logs, and statuses are also visible to Steve in the Model-Driven App for full transparency.
11. Recipes Management
Recipes can be created in multiple ways:
- Automatically by selecting an item from the Minecraft API.
- Manually created by a player to define a custom Recipe.
Recipes can be reused across Projects and Crafting requests.
The Name column is implemented as a PCF control using Fluent UI React v9. When the magnifying glass is clicked, a modal window appears that calls the Minecraft API, allowing players to select a recipe and return its name, description, and icon.
12. Summary
This process creates a complete Minecraft-themed procurement and crafting flow. From Project creation, bidding, contracting, recipe sourcing, to final crafting and delivery.
#low-code + pro code #category