Tags
Creators
Details
Licensed ARR
Published 3 years ago
Updated last month
All versions
4.6.2
Release
Axiom 4.6.2last year 19.4K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Required content
Any compatible version
Changes
4.6.1
Custom Creative Tabs
- Added buttons to gradient tab to export gradient into Editor
- Selected tab now remains open when closing and reopening the creative inventory screen Tool Raycasting
- Improved raycast accuracy and quality for many tools
- Added 'Tool Smoothing' option to Editor UI (found next to flight speed for tools that support it) New Window: Inventory
- Part of the Editor UI, automatically docked next to the Palette window
- Mirrors the creative-mode inventory, providing an alternative way to select blocks Ruler Tool
- Added 'Split' button to split a line into multiple evenly spaced segments Ingame Exact Block Copying (Ctrl+C)
- Block items with properties now show the properties in the item tooltip
- Added support for SpongeV3 schematics
- Added support for Litematic schematics
- Fixed Import Schematic not loading block entities correctly Marker & Display Entities
- Marker: min/max bounds now support relative coordinates when prefixed with ~
- Prevent shift from sneaking & flying downwards when using the 'no snapping' mode Block Tag Fixes
- Fixed custom axiom block tags not working in 1.21+
- Fixed custom axiom block tags not working on non-fabric multiplayer servers
4.6.2
- Pressing ESC on marker/display entity edit screens now saves instead of cancelling
- Fixed crash and other strange behaviour when using the smooth tool quickly
- Fixed mod crashing on startup when loaded on Forge via Sinytra Connector
- Fixed Litematics with negative size values (why?) not loading
- Bumped MixinConstraints to 1.0.7
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:N6n5dqoA:jGbJ87UX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:N6n5dqoA:jGbJ87UX"
}

