Tags
Creators
Details
Licensed MIT
Published last year
Updated last year
All versions
1.3.2
Release
Entity Logger 1.3.2last year 103
Compatibility
Minecraft: Java Edition
1.21.8
Platform
Fabric
Supported environments
Client-side
Required content
Unavailable version
Changes
EntityLogger v1.3.2 - World Time Fix
๐ Critical Bug Fix
World Time Logging Resolved
- Fixed: World time data now properly saves to database
- Issue:
world_timetable was not being populated due to UPDATE query on non-existent record - Solution: Replaced
UPDATEwithINSERT OR REPLACEfor reliable data insertion
Database Structure Improvements
- Three separate tables for clean data organization:
monsters- Monster positions and distancesplayers- Player positions and distancesworld_time- Game day, ticks, and moon phases
- Simplified initialization - No more complex table setup requirements
๐ง Technical Details
SQL Queries for Bot Scripts
-- Get all monsters sorted by distance
SELECT name, x, y, z, distance_to_player, health FROM monsters ORDER BY distance_to_player ASC;
-- Get all players
SELECT name, x, y, z, distance_to_player, health FROM players;
-- Get current world time
SELECT game_day, game_ticks, moon_phase, time_text FROM world_time WHERE id = 1;
Performance Features
- WAL mode enabled for concurrent read/write access
- Complete table refresh every 10 ticks (2x per second)
- Optimized for external scripts - no historical data clutter
โ ๏ธ Migration Notes
- Delete old database: Remove
minecraft_entities.dbbefore updating - Fresh start recommended: Let the mod recreate tables with proper structure
Requirements
- Fabric 1.21.8
- Fabric API 0.129.0+
- Java 17+
Perfect for bot automation and real-time monitoring!
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:BVKjB9L9:T86KvS6d"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BVKjB9L9:T86KvS6d"
}

