Edit: we decided to switch the approach we followed for this badge and describe a beautiful love story between two elements initially intented to be enemies, that ended up loving each other 💘
We are talking about Canvas Apps and a Custom API built inside a Minecraft Java server in a Virtual Machine (damn, that was long!).
Of course, that’s something that cannot happen without some awesome magic! In the middle of those two powerful elements there is a Custom Connector and multiple Power Automate Flows.
We will talk in detail about the 4 of them:
- The Pro Code layer: Minecraft API
We have a really cool Minecraft plugin built in Java that, among other thing, exposes an API that shares real time information about the players.
As an example, here we have an endpoint for retrieving the inventory of a player:
- The smart adapter: Custom Connector
That’s a vital piece for two main reasons! The first one is that it prepares the integration for our Low Code fellows to use and the second, and most important for me, is that it can almost be autogenerated with a proper Open API specification!
So easy to do, yet so important.
This is the Postman specification! - The brain: Power Automate
Of course, this Custom Connector has to be used somewhere. In this case, Power Automate acts as a tiny layer between the Canvas App and the custom connector, since most of the data operations will be held in our Canvas Apps.
- The beautiful face: PixelStreet Canvas App
All the elements previously described converge here; we have our own Canvas App for reading and performing actions in our Minecraft Server.
There are so many cool things I recommend checking our badge Feature Bombing.
Thanks for following along!
Claiming the Power User Love for our app that helps teachers and administrators plan and execute classes for each semester. A combination of PCF component in a Model Driven app to help teachers set the end and start dates of semesters in one field.
