The premiere long-distance brush editor for Sponge.
We use gradle to handle our dependencies.
- Check out this repository.
- Run
./gradlew build
The master branch is automatically build on our jenkins server (VoxelSniper Jenkins Job).
How do I create a ticket the right way?
- Seperate your reports. You think there is something wrong, but also want this new brush? Make life easier for us and create two tickets. We'd appriciate it big times.
- Don't tell us your story of life. We want facts and information. The more information about
the Problemyou give us, the easier it is for us to figure out what's wrong. - Check the closed tickets first. Maybe someone created a similiar ticket already. If you think it's unresolved, then give us more information on there instead.
Make sure to not tell us your story of life. We want brief descriptions of what's wrong to get directly to fixing. Also try to make the title describe briefly what's wrong and attach things like logs or screenshots to help illustrate the issue further.
Here is an example, where an imaginary brush that should create a ball, creates a cube:
Title: Brush A creates Cube instead of Ball
Expected behaviour:
Brush A should create a ball with radius 5 when I set it to brush A with brush size 5.
Experienced behaviour:
Brush A created a cube instead.
Additional Information:
SpongeForge: 1.10.2-2052-5.0.0-BETA-1675
Minecraft Forge: 12.18.1.2057
VoxelSniper: 8.0.0
Additional Information like what java version the server runs on would be appriciated, but is not required at all times.
This is where imagination comes in, but make sure to keep as it easy for us. As mentioned, we don't want your story of life. We want to know what you think would be a good enhancement.
Here is an example of an enhancement request.
Title: Brush that creates lines
Enhancement Proposal:
Creating a brush that creates a line.
Suggested usage:
You click two points with your arrow and it will create a line with blocks.
Reason of proposal:
It would be useful, since off angle lines are sometimes hard to make.
Keep in mind that those are guidelines. We will still look into stuff that does not follow these guidlines, but it will give you an idea what we want in a ticket and make our life easier.
We do accept pull requests and enhancements from third parties. Guidelines how to submit your pull requests properly and how to format your code will come.
Some rough guidelines for now:
- Keep the number of commits to a minimum. We want to look over the commit and basically see what you've done.
- Coding guidelines should try to comply to the checkstyle rules (checkstyle.xml) but not blindly. Use your mind to make smart decissions.
- Give us a good description to what you've done.
- Try to submit one change in one pull request and try to link it to the issue in the tracker if possible.