Tags
Creators
Details
1.19-35
Compatibility
Changes
[CORE] Changes
Changes to the core of the plugin - Ex: New Features, Bug Fixes, Performance Improvements etc.
- [x] [CORE] Re-implementation of PlotSquared, WorldGuard, GriefPrevention and Towny Protections - BREAKING CHANGE
- [x] [CORE] Updated Translations
- [x] [CORE] Metrics Fixes for Bstats
- [x] [CORE] Bug Fixes
- [x] [CORE] Permission Improvements for OP Users - BREAKING CHANGE
- [x] [CORE] Performance Improvements
- [x] [CORE] Introduction of CustomModelData Support - BREAKING CHANGE
- [x] [CORE] Update Readme.md for Discord Support
- [x] [CORE] More Debug Output
- [x] [CORE] 1.19 Update
- [x] [CORE] Code Review Remarks from SonarCloud and CodeFactor
[CI] Changes
Changes relating to the Continuous Integration of other Plugin APIs etc.
- [x] [CI] Massive Dependency Updates
- [x] [CI] Java 18 Builds (futureproofing)
- [x] [CORE/CI] Move to PaperMC API - Investigated and not feasible at the moment.
BREAKING CHANGE INFO:
Protections:
ASE now has implemented better protection options for the following plugins
- PlotSquared
- GriefDefender and GriefPrevention
- WorldGuard
- SuperiorSkyblock
This may or may not break existing functionality but was tested and checked by Wolfieheart before release
Permissions:
Overhaul of permissions and introduction of permpacks. Recommendation of the permissions below:
- asedit.* for all Mods and Admins
- asedit.permpack.basic and asedit.permpack.dontIgnoreProtections for everyone else
CustomModelData Support
ASE now supports CustomModelData. If you wish to avail of this, please enable it in the config and give people the permission asedit.give in order to use this
Issues and Questions?
Please report all issues to https://github.com/Wolfieheart/ArmorStandEditor/issues
What's Changed
Full Changelog: https://github.com/Wolfieheart/ArmorStandEditor/compare/1.18.2-34.2...1.19-35
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:tE6xCDgP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oIBGjZ77:tE6xCDgP"
}

