Tags
Creators
Details
2.0.1-neoforge-1.21.1
Compatibility
Changes
SmallShips 2.0.0
Added
- New ships: Galleon, Caravel, Dhow
- Dockyard: build, upgrade and repair ships
- Datapack-driven dockyard recipes
- Wind-based sailing with a wind profile per ship
- Ship upgrades: Iron Scantlings, Copper Plating, Cotton Sails
- Ammo types: Cannonball, Chain Shot, Grape Shot (mouse wheel to select, HUD shows available ammo)
- Ground Cannon
- Ramming
- Sinking animations and wood debris on cannon impact
- Epic Knights shield support
- Gunner seats: click a cannon to man it
- Ship inventory panel to detach cannons, banners and shields
- Sail patching with string and iron nuggets
- Control tips when boarding a ship
- Hoppers can access the ship's hold
- NPCs leave the deck onto nearby land when the ship lies still
- Addon API (ship registry) for ship-addon mods
- Update checker
Improved
- Multipart hitboxes: decks are walkable
- Cannon aiming: accurate, camera sits on the barrel
- Seating: players get the helm first, then the nearest free seat
Fixed
- Creative tab disabled by default on Forge
- Freshly spawned ships not walkable
- Passengers damaging their own ship
- Bubble columns affecting ships
- Ship turning on its own after the driver dismounts
- Cargo visuals out of sync with multi-page inventories
Config
- Split into server and client config; server values sync to clients
- Ship attributes apply live to existing ships
dockyardBuildableShipswhitelist (empty = all ships)- Per-ship upgrade costs
updateCheckerEnabletoggle
##2.0.1 Hotfix
-fixed dockyards do not recognize ships sometimes -fixed shields info display -fixed ships from dockyards can spawn in other ships -improved API for addons and compatiblity -added shoulder surfing compatiblity -added Turkish, German, Spanish and Russian Language
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:rGWEHQrP:QNjKZdCr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rGWEHQrP:QNjKZdCr"
}

