0.2.0
Compatibility
Required content
Changes
Camp Board v0.2.0-beta
This update adds configurable large Camp Boards, command-only removal support, material importing, and several fixes around board data and placement behavior.
Added
- Added configurable Camp Board size.
- Standard size keeps the original board.
- Large size places a true 3x3 Camp Board.
- Added Mod Menu option for board size.
- Added configurable break behavior.
- When enabled, Camp Boards can be broken normally.
- When disabled, Camp Boards must be removed with a command.
- Added
/campboard remove.- Removes the Camp Board the player is looking at.
- Works with both standard and large boards.
- Added material import support.
- Import material requests from text-style files stored on the server.
- Supports simple lines like
minecraft:stone 128or128 minecraft:stone.
Changed
- Large Camp Boards now use real 3x3 placement instead of an oversized single-block model.
- Large Camp Board hitboxes now match the placed board sections more reliably.
- Large Camp Board pieces share the same board data.
- Breaking or removing one piece of a large Camp Board removes the full board.
- New placed boards now receive unique board IDs to better separate data between multiple boards.
Fixed
- Fixed large Camp Boards rendering with incorrect/random textures.
- Fixed command removal for large Camp Boards.
- Fixed board data overlap risk when multiple Camp Boards are placed.
- Improved handling for command-only board removal.
Import Notes
Material import files should be placed in:
serverconfig/campboard/imports/
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:osLrfskF:4wxpK0SP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:osLrfskF:4wxpK0SP"
}

