A Minecraft plugin that integrates with the BrickChain platform for property management and user authentication.
- User Authentication: Register, login, and logout with BrickChain API
- Property Requests: Define property areas using enchanted fence blocks
- API Integration: Seamless communication with BrickChain backend
- Unbreakable Markers: Property boundary blocks cannot be broken
- Download the latest JAR file from releases
- Place the JAR in your server's
pluginsfolder - Restart the server
- Configure the plugin if needed (optional config in
plugins/Siose/config.yml)
- Minecraft Server (Paper/Spigot 1.20+)
- BrickChain API Server running on localhost:3000
/register- Register for a BrickChain account/login <token>- Login with your authentication token/logout- Logout and clear session/getdata- Fetch user data (requires authentication)/requestproperty- Get 3 enchanted fence blocks to define property area
- Run
/requestpropertyto receive 3 enchanted fence blocks - Place the first block at the property corner
- Place the second block to define length
- Place the third block to define breadth
- The plugin calculates the area and submits the property request to the API
The plugin communicates with the BrickChain API at http://host.docker.internal:3000/v1:
POST /register- User registrationPOST /auth/minecraft/login- Minecraft loginGET /user/@me- Fetch user profilePOST /user/property-requests- Submit property requests
{
"entity": "{\"coordinates\": [[x1,y1,z1], [x2,y2,z2], [x3,y3,z3]], \"area\": 123}"
}- Java 17+
- Maven 3.6+
- Minecraft development environment
mvn clean compile
mvn packagesrc/main/java/me/samarthh/
├── Main.java # Plugin main class
├── api/
│ └── SioseApiClient.java # API client for BrickChain
├── commands/ # Command implementations
├── listeners/ # Event listeners
└── managers/ # Data managers
- Fork the repository
- Create a feature branch
- Make your changes
- Test thoroughly
- Submit a pull request
This project is licensed under the MIT License - see the LICENSE file for details.
For issues and questions, please open an issue on GitHub or contact the development team.