1.3
Compatibility
Changes
LFT 1.3
LFT 1.3 is a major visual and multiplayer update focused on immersion, communication, and overall server atmosphere.
New textures
- Added brand-new textures for multiple LFT blocks and items.
- Improved visual consistency across the Primordial block set.
- Updated models and textures to better match the dark fantasy style of the mod.
New chat system
The vanilla chat has been completely replaced with a custom LFT chat system.
Local chat
Messages are only visible to nearby players.
Format:
[L] [PlayerName] message
Global chat
Start a message with ! to send it to the entire server.
Format:
[G] [PlayerName] message
Example:
!Hello everyone
Configurable local chat radius
Server operators can change the local chat range in real time:
/lft chatsettings <radius>
Examples:
/lft chatsettings 40/lft chatsettings 120/lft chatsettings 250
Redesigned private messages
Added a completely new private messaging system using the /message command.
Format:
PlayerOne → PlayerTwo: message
Features:
- Clean modern formatting
- Colored player names and message text
- High-pitched note block notification sound when receiving a message
- Independent from the vanilla messaging system
Vanilla private messages disabled
The vanilla /msg, /tell, and /w commands have been disabled to avoid formatting conflicts and ensure all players use the new LFT messaging system.
Use:
/message <player> <text>
Chat improvements
- Removed the vanilla
<Player>chat format. - Added colored prefixes for local and global channels.
Internal changes
- Reworked the chat handling system for NeoForge 1.21.1.
- Added a shared runtime configuration manager for chat settings.
- Improved compatibility and stability of custom chat and command handling.
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:XCt8ykxg:xcWUhQjR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XCt8ykxg:xcWUhQjR"
}

