Tags
Creators
Details
1.6.0
Compatibility
Changes
Enhancements
- Added
/msgtogglecommand to toggle private messages.- TIP: This works differently than the
/ignorecommand. The/ignorecommand also blocks teleport requests sent via/tpa, whereas/msgtoggleonly disables receiving private messages.
- TIP: This works differently than the
- Added
/seencommand to check when a player was last online. - Added a server slot management command to dynamically adjust player slots.
-
Added a server links feature to the pause menu (1.21+ only).

- Added separate permission for gamemode:
eternalcore.gamemode-/gamemodeeternalcore.gamemode.other-/gamemode <player>
- Enhanced Auto-Warp GUI and fixed related bugs.
- Refactored item-edit related commands.
- Improved admin chat command and event modifications handling.
- Player selected language is now saved to database.
Fixes
- Fixed auto-message issues with database query and message ordering.
- Fixed chat delay not saving to configuration.
- Fixed AFK permission check order and typo in configuration.
- Fixed delay issues and improved alert (queue) messages.
- Fixed death message handling, added
{CAUSE}placeholder. - Fixed
/sudocommand placeholder issues. - Fixed catboy remove using
/butchercommand. - Fixed catboy bug after server restart.
- Fixed multiple bugs in default language files.
- Several internal code fixes
đ§ Developer API
To use EternalCore API, you first need to add EternalCode to your project. To do that follow these steps: You can check the latest release number here(https://github.com/EternalCodeTeam/EternalCore/releases/latest).
- Add repository:
For Gradle projects use:
maven("https://repo.eternalcode.pl/releases")
For Maven projects use:
<repository>
<id>eternalcode-reposilite-releases</id>
<url>https://repo.eternalcode.pl/releases</url>
</repository>
- Add dependency:
For Gradle projects use:
compileOnly("com.eternalcode:eternalcore-api:1.6.0")
For Maven projects use:
<dependency>
<groupId>com.eternalcode</groupId>
<artifactId>eternalcore-api</artifactId>
<version>1.6.0</version>
<scope>provided</scope>
</dependency>
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:NgVN6prx:GZJFG2wZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NgVN6prx:GZJFG2wZ"
}

