Tags
Creators
Details
26.1.2-51
Compatibility
Changes
This is the ASE Update for 26.1 through to 26.1.2. The first of the new numbering scheme cause Mojang decided, following Windows is a good idea. Cheers!
Read this before updating
ASE as of 26.1 is built using Java 25. If you need to update your Java on your Server, please read https://docs.papermc.io/misc/java-install .
Failure to do this before updating to 26.1 or higher, and complaining that ASE is giving an error like has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 61.0 will result in your issue being closed as NOT A BUG.
Config Changes
ArmorStandEditor now supports a way to block armorStands with given names from being edited. So you can do that by adding the following to your Config.yml
#----------- BLOCKED NAMES
# Armor stands with the following names will not be able to be edited
# Use exact name matching (case sensitive)
enableBlockedNames: false
blocked-names:
- "BlockedArmorStandName"
# - "ItemsAdder_furniture"
Also CustomDataModel is now done by using float numbers , not integers as in line with the PaperAPI
#Also please if you are using this, ensure that you also give people the ability asedit.give in
#order to allow them to change their edit tool for the right Custom Model Data
allowCustomModelData: false
customModelDataInt: 0.0
Other Changes
- Better Update Checker
- Java 25 Support
- CoreProtect Support
- Folia is better supported
- Maven has been replaced with Gradle
- Better Towny Permission Check
- Introduction for Bolt Protection (for users of Bolt)
New Contributors
- @Izopropyl made their first contribution in https://github.com/Wolfieheart/ArmorStandEditor/pull/845
Full Changelog: https://github.com/Wolfieheart/ArmorStandEditor/compare/1.21.11...26.1.x
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:7DxLZFJJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oIBGjZ77:7DxLZFJJ"
}

