Tags
Creators
Details
Licensed LGPL-3.0-only
Published last month
Updated last month
All versions
0.4.1-vs2.3
Beta
VS: Analog Warfare 0.4.1-vs2.32 months ago 20
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Changelog 0.4.1
Setup Block
Temporary Block Removal
- Added support for marking temporary blocks for automatic removal after setup execution.
- Added configurable removal delays and support for marking blocks across multiple ships.
- Added removal-mode feedback showing how many temporary blocks are marked.
Vehicle Setup Compatibility
- Added support for Create linked controllers and DBW Controller Hubs.
- Added support for Trackwork wheels and suspension stiffness adjustment.
- Fixed action delays when setups are spawned with VMod.
- Added progress messages during setup execution.
Macro Editor
- Reworked the editor into separate
Actions,Transmitters, andRemovalspages. - Added individual delete buttons for actions and transmitters.
- Added removal-delay editing and improved delay tooltips.
- Improved action descriptions and row icons.
- Added a confirmation prompt for deleting all actions.
Recording
- New actions are now appended instead of replacing existing actions.
- Added separate regular and temporary-removal recording modes.
- Added sneak-scroll mode switching with the Analog Screwdriver.
Fixes
- Fixed Vehicle Setup actions targeting the wrong block by one block after VMod pastes on dedicated servers.
- Fixed DBW backup-block links being restored incorrectly after VMod pastes.
- Fixed Create linked controllers and DBW Controller Hubs retaining their hub link after VMod pastes.
- Fixed Ender energy transmitter passwords being truncated to 16 characters in the configuration screen.
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:DjnOEDuA:R3HqaLKc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DjnOEDuA:R3HqaLKc"
}

