1.0.9
Compatibility
Changes
๐ง Arcticโs Essentials โ Stability & Rebrand Update
This update marks the official transition from SE Essentials to Arcticโs Essentials, aligning the project with the ArcticZero ecosystem.
Alongside the rebrand, major internal refinements and stability improvements have been made.
โ Rebrand
- Renamed SE Essentials โ Arcticโs Essentials
- Updated mod ID & branding alignment
- Cleaned up internal references
- Configuration folder standardized to:
config/arctics_essentials/
- Improved consistency across messages and structure
๐ง Command Improvements
๐ Speed System Overhaul
- Reworked
/speedto use a clean multiplier system (0โ20) 1= default speed (1x)- Values scale logically up to a safe cap
- Improved stability and consistency in movement handling
๐ Fly Speed Changes
- Removed
/speed fly - Added dedicated
/flyspeed <0โ20>command - Added
/flyspeed reset - Improved clarity and separation between walk and fly speed controls
๐ง Teleport & RTP Improvements
- Fixed RTP crash scenarios
- Added safe failure handling when no valid location is found
- Improved teleport stability & edge-case handling
- Refined warmup cancellation logic
๐พ Data Handling
- Improved async saving behavior
- More stable player data storage
- Reduced risk of edge-case corruption
- General performance optimizations
๐ General Stability
- Internal code cleanup
- Better error handling across multiple systems
- Improved modular config behavior
- Reduced unnecessary operations during runtime
โ RTP Notice
Random Teleport has been stabilized and will no longer crash the server.
Safe-location logic is currently being refined.
If a valid location cannot be found within configured attempts, RTP will now safely abort instead of forcing a teleport.
Further RTP improvements are planned.
๐ฆ Foundation Release
This update focuses on:
- Stability
- Structure
- Clean architecture
- Brand alignment
Future updates will continue expanding functionality while maintaining performance and modularity.
Thank you for using Arcticโs Essentials.
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:scKtunJV:6jDl7S4I"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:scKtunJV:6jDl7S4I"
}

