Tags
Creators
Details
26.3-52
Compatibility
Changes
Updated for Minecraft 26.3. This release adds head retrieval limits, an admin cleanup tool for invisible empty stands, Dominion support, and a long list of fixes.
Read Before Updating
- New file:
playerheads.ymlis generated on first load and stores per-server head retrieval counts. - Head limit is on by default:
maxNumberOfHeadRetrievalsdefaults to5. Raise it inconfig.ymlif you don't want players capped. - Reset with care: the head reset command is admin-only and can zero everyone's retrieval count.
- Paper plugin descriptor: ASE now uses
paper-plugin.yml. Run it on Paper or a Paper fork. - Java 25 is required (carried over from 26.1).
Config Changes
Add these to your config.yml under Misc Options:
#---- Misc Options
# Limit the number of times that players can get their head on the server
maxNumberOfHeadRetrievals: 5
# Prevents players from leaving invisible armor stands with nothing equipped around the world.
# Stands with a visible custom name (holograms) are ignored.
# OFF - Do nothing (default)
# VISIBLE - Make the stand visible again
# GLOW - Keep the stand invisible, but make it glow so it can be found and removed
invisible-empty-stand:
mode: OFF # OFF | VISIBLE | GLOW
- Head retrieval counts are stored in the new
playerheads.yml.
New Commands & Permissions
| Command / Permission | Description |
|---|---|
/ase resetHeads |
Resets head retrieval counts back to 0, with a confirmation step. Admins/OPs only. |
asedit.resetHeads |
Allows resetting the head retrieval count for a player. Admins only. |
asedit.resetHeads.all |
Allows resetting the head retrieval count for all players. Admins only. |
New Features
- Invisible empty stand mode: admins can clean up empty invisible stands by making them visible again or glow (see config above).
- Player head limits: head gathering is limited per server and persisted in
playerheads.yml. - Legacy small size: the legacy small ArmorStand size is back, with menu integration.
- Equipment lock copy and paste: copy and paste lock slots between stands.
- Dominion protection: support added using DominionAPI 4.7.3.
- GriefPrevention protection: reimplemented, with a config option.
- MiniMessage support for tool lore, plus legacy color code translation in the language system.
- Shelves added to the interactables list.
Improvements
- Updated to Minecraft 26.3.
- Permission checks now allow ItemFrame interactions, and ArmorStand permission handling is refined.
- Dominion edit privilege flag changed from
PLACEtoBREAK_BLOCK. - Towny protection: better entity checks and logging (ItemFrames need special handling).
- Better glowing handling, highlight method refactor, and menu fixes.
- Command handling partially moved to Brigadier.
CommandExreturn values are no longer always the same. - Language class refactored for thread safety and better config handling.
- Conditional config loading now gathers only conditional entries. Item tool validation and config reset fields refactored.
- Added debug logging for entity protection, visibility enforcement, empty stand checks, edit permission checks and head resets. Default debug log level changed.
- Reduced complexity in
onEnable, and cleaned upisEditTool. - Updated the WorldGuard dependency and upgraded Gradle to 9.6.1.
- Plugin version is now resolved at build time.
Fixes
- Scheduler not initializing.
- ASE not being allowed to interact with some interactables (potentially fixes #865).
- Claim protections being ignored for ArmorStand interaction (#881).
ResetWithRangemissing from the/ase ?output.customModelDataValuebug.- Option keys not resolving to their translated value before substitution.
- NPE in command handling.
- Head reset commands now validate the target player and handle offline players safely.
- Removed redundant permission and equipment null checks.
- Replaced deprecated code in a debug message.
- Reverted the changes that were required for Scale.
New Contributions
- None listed in the changelog.
Full Changelog: https://github.com/Wolfieheart/ArmorStandEditor/compare/26.1.x...26.3-52
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:oIBGjZ77:xUTmFqSj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oIBGjZ77:xUTmFqSj"
}

