1.0.0
Compatibility
Required content
Changes
Camp Board v1.0.0
Camp Board is now moving out of beta as a stable release. This version includes physical project boards, project/task/material tracking, suggestions, server-side storage, configuration, JEI visibility, Mod Menu support, and material importing.
Added
- Physical Camp Board block.
- Standard and large Camp Board placement options.
- Board UI for projects, suggestions, and archived projects.
- Project statuses:
- Planned
- Active
- Paused
- Completed
- Archived
- Project leaders.
- Task tracking with helper participation.
- Material request tracking.
- Material contribution and withdrawal support.
- Project location tracking with Overworld/Nether coordinate conversion.
- Suggestions tab for non-official project ideas.
- Activity log entries for project changes.
- Editable server-side JSON storage.
- Automatic backups.
- Crafting recipe.
- Creative inventory visibility.
- JEI recipe/category support.
- Mod Menu configuration screen.
- Admin maintenance commands.
/campboard removefor command-based board removal.- Material import support from server-side text-style files.
Fixed
- Camp Board item rendering in inventory and hand.
- Wall-mounted board placement and hitbox behavior.
- UI readability and layout issues.
- Task and material scrolling/layout problems.
- Board data persistence.
- Multiple placed boards now keep separate project data.
- Material import now works with projects created from placed Camp Boards.
- Server startup hang from earlier builds.
Material Import
Import files are read from:
serverconfig/campboard/imports/
Run:
/campboard materials import <projectID> <fileName>
Example:
/campboard materials import nether_hub nether_hub_materials.txt
Supported line examples:
minecraft:stone 128
128 minecraft:spruce_planks
minecraft:glass, 64
File extensions are not restricted, but structured JSON, CSV headers, and .litematic files are not parsed directly yet.
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:mhuR84ea"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:osLrfskF:mhuR84ea"
}

