Tags
Creators
Details
Licensed LGPL-3.0-only
Published 6 years ago
Updated 2 months ago
All versions
13.2.0
Release
autoswitch 13.2.010 months ago 1,124
Compatibility
Minecraft: Java Edition
1.21.9–1.21.10
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
13.2.0
- Add debug huds to show matched targets and tool selectors
- Access via
F3+F6 - Named
autoswitch:attack_targets,autoswitch:tool_selectors, andautoswitch:interact_targetstool_selectorsdo not take into consideration the target or Action, they only consider the held item- Sorted based on data ratings (not very useful)
*_targetsare sorted based on target priority and data ratings- Mimics the sorting used by the Selection Engine to choose which tool to use
- Access via
- Add debug hud to show item tags that apply to the currently held item
- Access via
F3+F6 - Named
autoswitch:item_tags
- Access via
- Add debug hud to show enchantment tags for currently held item
- Access via
F3+F6 - Named
autoswitch:enchantment_tags
- Access via
- Add debug hud to show entity tags of the currently targeted entity
- Access via
F3+F6 - Named
autoswitch:entity_tags
- Access via
- Update Neoforge for new transfer api
- Support for 21.9.1-beta+
13.1.0
- Implement enchantment level specification for item selectors
- See examples here
- Add debug huds to show enchantment ids and potion contents of the currently held item.
- Access via
F3+F6 - Named
autoswitch:enchantmentsandautoswitch:item_components
- Access via
13.0.0
- Update for 1.21.9/25w37a
12.2.0
- Implement enchantment level specification for item selectors
- See examples here
12.1.2
- Fix fabric loader dependency always being bumped when building
- Lock MC version upper bound to 1.21.8/25w36a due to breaking changes in vanilla
12.1.1
- Convert
feature-config.switch-away-from-toolsfrom a boolean to a set of actions that can have the switch away behavior. Defaults to just theATTACKaction. - Fix switchback not triggering when
feature-config.switch-away-from-toolsselects an empty slot. - Fix switchback remembering the incorrect slot
12.1.0
- Add config option
feature-config.switchback-waits-for-attack-progressto control when switchback waits for attack progress to fully reset.
AutoSwitch 12.0.1
- Fix skipDeletedItems not being applied to items with durability
Changes Since AutoSwitch 11
- Complete rewrite of AutoSwitch
- Update for 1.21.6
- Minecraft version range is no longer open ended
- Added Neoforge support
- New config system using HOCON, see config file in config/autoswitch.conf
- Added target priorities for cases where multiple targets (eg tags) match
- Support limiting entity targets based on equipment
- Support ItemComponent selectors
- Currently limited to Potion Contents
- Removed custom tool groups, everything is now using item tags
- Allow combing selectors with expressions such as AND, OR, XOR, etc for more complex selection logic
- Use entity sensitive_to tags to for enchantment preferences
- Remove entity ride event default in favor of interact selectors
- Add default selector for interacting with fire -> water splash potion
- Add support for choosing what items to move to the offhand and for which action
- Fix DPS calculation for entity tool ratings
- Swords are not correctly preferred over axs without explicit ordering
- Disable switchback when the player selects a new slot manually
- Rework AutoSwitch API
- No longer requires a compile time dependency on AutoSwitch
- On Neoforge, use IMC
- On Fabric, use ObjectShare
- No longer requires a compile time dependency on AutoSwitch
- Use Minecraft's internal profiler in some places
- Added actual tests so hopefully things don't break
- Removed config commands
- emvoe bow target
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:uSdcnlts:AO00ycW1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uSdcnlts:AO00ycW1"
}

