Welcome to the development repository! This project is a puzzle game built in Godot 4.5.1 (Mono/C# Edition) inspired by Sokoban. The core experience revolves around the concepts of water, bomb, and walls.
In this game, explosions aren't just for combat—they are your primary tool for movement and puzzle-solving.
- Explosion: Use your bomb to open your path to the next level!
- Navigation: Master the art of "Explosive Dashing." By timing your movements with blasts, you can launch yourself across massive gaps or push multiple blocks.
- Godot Engine 4.5.1 (.NET/Mono version): Ensure you have the C# support installed.
- .NET SDK: (Version 8.0 or newer recommended) to compile the C# scripts.
- Fork this repository by clicking the "Fork" button at the top right of this page.
- Clone your fork to your local machine:
git clone https://github.com/YOUR_USERNAME/biu.git
This url can be found at your forked project page.
Warning
Make sure the url is not WMsans/biu.git, but your own username.
- Launch Godot 4.5.1 (Mono).
- In the Project Manager, click Import.
- Browse to the folder where you cloned the repo and select the
project.godotfile. - Once the editor opens, click the Build button (hammer icon) in the top-right corner to compile the C# solution for the first time.
We welcome contributions in both code and art!
To add new textures or sprites to the game:
- Place your
.pngfile into theres::/textures/directory within the project folder. - Switch back to the Godot Editor. It will automatically detect the new file and begin importing it.
- Configuration: Select the image in the FileSystem dock.
- Go to the Import tab (next to the Scene tab).
- For pixel art, ensure Compress > Mode is set to
Losslessand Filter is set toNearest. - Click Reimport to apply changes.
- Fork this project.
- [Optional] Create a new branch for your feature:
git checkout -b feature/your-feature-name. - Write your logic in C#, GDScript or any language extension you like. Follow the existing naming conventions (PascalCase for methods and public variables).
- Ensure the project builds successfully before committing.
Once you've made your changes and pushed them to your fork:
- Navigate to the original repository on GitHub.
- You should see a yellow bar saying "Compare & pull request". Click it.
- Describe your changes:
- What does this PR add or fix?
- Are there any breaking changes?
- Attaching images explaining the changes are preferred.
- Click Create pull request.
A maintainer will review your code/assets shortly!