1.20.1-1.3.3
Compatibility
Required content
Changes
Figura Lite 1.3.3
This update focuses on long-session stability, avatar lifecycle management, and a redesigned responsive interface.
Improvements
- Redesigned the settings screen with a cleaner Minecraft-style appearance.
- Added responsive layouts for different resolutions and GUI scales.
- Added virtualized player and ignore lists for servers with 100+ players.
- Player lists now update even when Auto Panic is disabled.
- Added player search with optimized refresh and sorting.
- Added visible Ignore status:
+ Ignorefor normal players.β Ignoredfor ignored players.
- Improved scrolling and dynamic row counts based on the available screen space.
- Added a compact status and usage section to the settings panel.
Performance
- Reduced per-frame allocations in the player list.
- Player data now refreshes at a controlled interval instead of being rebuilt every frame.
- Only visible list entries are rendered.
- Removed unbounded player-distance and reload-cooldown caches.
- Player state is cleaned when players leave, worlds change, or the client disconnects.
Avatar Lifecycle Fixes
- Fixed permissions not being restored when Auto Panic was disabled.
- Fixed ignored players sometimes remaining blocked.
- Restored modified permissions during disconnects and world changes.
- Replaced unreliable weak-reference permission tracking with deterministic player-state management.
- Added distance hysteresis to prevent repeated avatar reloads near the configured boundary.
- Prevented duplicate and unnecessary avatar reload requests.
- Improved avatar reload failure logging.
Bug Fixes
- Fixed nearby players showing as
0 onlinewhile Auto Panic was disabled. - Fixed stale players remaining in the internal cache.
- Fixed player state being retained across long play sessions.
- Fixed GUI layouts overflowing or becoming unusable at high GUI scales.
- Fixed corrupted characters in interface labels.
- Improved Ignore and Remove button click areas.
Recommended for players using Figura Lite during long multiplayer sessions or on servers with large player counts.
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:z10Y10lz:zrlRU08o"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:z10Y10lz:zrlRU08o"
}

