1.0.0
Compatibility
Changes
PermsCraft v1.0.0-STABLE
š First Stable Release
After extensive development and testing, PermsCraft reaches its first stable public release.
This release introduces the complete foundation of the PermsCraft ecosystem, including permission management, group inheritance, contextual permissions, GUI tools, REST API support, multi-database storage, and network synchronization.
Added
Permission System
- User and group permission management
- Wildcard permissions
- Permission inheritance
- Temporary permissions
- Temporary groups
- Metadata support
- Permission conflict resolution
Context System
- World contexts
- Server contexts
- Game mode contexts
- Time-based contexts
- Custom context support
GUI Suite
- User management GUI
- Group editor GUI
- Permission browser
- Track manager
- Backup manager
- Search utilities
- Context editor
Developer Features
- Public API
- Event system
- REST API
- OpenAPI documentation
- Cached permission access
Storage Providers
- YAML
- SQLite
- MySQL
- MariaDB
- PostgreSQL
- MongoDB
- H2
Network Features
- Redis synchronization
- Multi-server support
- Cross-server updates
- Distributed permission propagation
Integrations
- Vault support
- PlaceholderAPI support
- Brigadier support
Security
- API key authentication
- Rate limiting
- Backup system
- Backup restoration
- Permission audit logging
Monitoring
- Action logs
- Audit trails
- Debug tools
- Advanced filtering
Migration
- Migration utilities
- Automatic backup creation
- Import workflows
Platform Support
- Paper
- Spigot
- Purpur
- Folia
Stability
This release is considered production-ready and intended for live servers.
Thank you for supporting PermsCraft ā¤ļø
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:H8BkDNL7:f6YhXSyA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:H8BkDNL7:f6YhXSyA"
}

