Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
Updated last month
All versions
2.4.0
Release
2.4.02 years ago 110
Compatibility
Minecraft: Java Edition
1.21–1.21.4
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.8–1.8.9
Platforms
Bukkit
Paper
Spigot
Changes
Improvements
- New config layout
- Old configurations are updated automatically
- Config files are now created in the plugin folder automatically
- Added FancyHolograms integration
- Holograms can be selected and edited using EasyArmorStands
- Added Lands integration
- Role flag
easyarmorstands_edit(Edit entities) - Bypass using
easyarmorstands.lands.bypass
- Role flag
- Renamed
/eas groupto/eas select- Permission changed to
easyarmorstands.select - Selecting multiple entities also requires
easyarmorstands.grouppermission
- Permission changed to
- Added
/eas tagcommand to manipulate scoreboard tags- Makes it easier to target entities using command blocks
- Permission:
easyarmorstands.property.tags /eas tag add: Add a tag/eas tag remove: Remove a tag/eas tag list: List tags of the selected entity/eas tag select: Select all entities with a tag- Permission:
easyarmorstands.select.tag - Selecting multiple entities also requires
easyarmorstands.grouppermission
- Permission:
- Added
/eas viewrange- Can be used to set the view range of a display entity
- Values are relative:
1.0is the default, e.g.0.5halves the view range
- Added scale limits to the config
- Allows preventing the creation of very large entities
- Display entity scale is unrestricted by default
- Allow disabling integrations using the config
Fixes
- Fix Head Database menu on versions before 1.13
API changes
- Added
Session#getElements
Optional dependencies
Any compatible version
Any compatible version
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:8DDI76SG:9kkloXf7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8DDI76SG:9kkloXf7"
}

