We´re back! A new year and another ACDC. PointPixels are super excited to join the hackathon again.

For the Early Delivery Badge, we have crafted an idea for what we want to build. Our solution is based on utilising Power Platform and Azure capabilities to interact with Minecraft. We want to build a storefront which we have named “PixelStreet”, as in Wall Street, in Power Platform. It´s going to be a modern, responsive and sleek looking interface for players (users) to trade resources and manage inventory with our own currency PointCoins.

The store has a clerk operating as an NPC that is able to explain materials, assists with purchases, and guide crafting and building for in-game creation of structures. Our clerk is technically built using Copilot Studio and the agent will be able to connect to our Minecraft JAVA server hosted in Azure through the PixelPointAPI and MCP server for performing CRUD operations which will enable the player (user) to execute commands that will craft the item and build the physical structure in our Minecraft world.

PixelPointAPI

This API will act as the bridge between Minecraft and all our integrations! So far, we are able to:

List Inventory of a player (/api/intentory/<player>)

Get player general information (/api/player/<player>)

For buying and selling resources, the idea is to build an economy layer that determine the price of resources based on AI and the actual rate players in Minecraft is trading resources in-game.

That means the price of resources will fluctuate depending on what and how much players are buying and selling. We will use Azure Functions to send events to Power Platform.

Point Coins 🤑

Every Item in Minecraft will effectively have a buying price and a sell price. Which will change over time based on which transactions take place!

Using Agents for automation in Minecraft

To make life easier for the users, they will be able to use their Point Coins to feed our automation agents.

So far, we plan to implement:

• Crafting Agent: helps players recommending items to craft, suggesting on how to craft them and, in case they want to craft something which items they are missing. This will also be helpful for making autocrafting mechanisms (that agent can craft for you if prompted for instance). The apis for retriving inventory information can be combined with the crafting apies for full context.

[GET] /recipe/{id}/{count} returns the recipe for a given item based on the id. It is also provide an amount to recalculate the ingredients needed.

[POST] /showCurrentCraftingOptions display all the available crafting opportunities based on a inventory and tools input:

— If a crafting table is available more items will be unlocked.

[POST] /showRemainingItems/{id}/{count} returns a list of missing ingredients to craft an item based on the inventory and tools available

[POST] /simulateCraftingResult/{id}/{count} simulates the inventory state after crafting is done for a specified item and amount based on a inventory and tools input. math: inventory – recipies expended + newly crafted items.

• Building Agent: given the resources or Point Coins in value + a fee, this agent will build structures based on the prompt of the user.