1.2.0
Compatibility
Required content
Changes
Sit On Everything 1.2.0
Added
- New builds: Fabric 1.19.2, Forge 1.21.1, Forge 1.21.11. They behave exactly like the other builds.
Removed
- Minecraft 26.1 and 26.1.1 are no longer supported. Use the 26.1.2 build instead.
Changed
- Fabric and NeoForge builds now require Architectury API. Forge builds need nothing beyond Forge.
- Each file now asks only for the loader versions it actually runs on (see Compatibility).
- The Fabric 26.1.2 build needs Fabric Loader 0.19.5 or newer.
Fixed
- A seat offset in
config/sitoneverything.jsontoo large to be a number (e.g.1e400) sent the seat and its rider to an infinite position. Such values now count as missing, and the default applies. - If
config/sitoneverything-client.jsoncouldn't be read (e.g. a missing comma after a hand edit), it was overwritten with defaults at start-up, which lost your settings and turned theSit on targetkey and Ctrl + Right Click sitting back on. The file is now left untouched so you can repair it, and the defaults apply for that session only. - Breaking a waterlogged stair or slab someone was sitting on left them seated in the water. They are now set down, like with any other seat block that disappears.
Unchanged
- Same config files,
/sitcommand, key bindings, translations and seats.
Compatibility
- Install on the server (or in single-player). On the client it's optional: it adds the
Sit on targetkey, the Ctrl + Right Click toggle key and Ctrl + Right Click sitting. Players without it can sit with/sit, or by sneaking and right-clicking a block with empty hands when the server enablessneakRightClickSitting. Modded and unmodded clients and servers can still connect to each other.
Fabric (requires Fabric API and Architectury API)
| Minecraft | Fabric Loader | Fabric API | Architectury API | Java |
|---|---|---|---|---|
| 1.19.2 | 0.14.9+ | 0.66.0+1.19.2+ | 6.6.92+ (6.x) | 17 |
| 1.20.1 | 0.14.21+ | 0.83.0+1.20.1+ | 9.2.14+ (9.x) | 17 |
| 1.21.1 | 0.15.11+ | 0.102.0+1.21.1+ | 13.0.11+ (13.x) | 21 |
| 1.21.11 | 0.17.3+ | 0.139.4+1.21.11+ | 19.0.1+ (19.x) | 21 |
| 26.1.2 | 0.19.5+ | 0.154.0+26.1.2+ | 20.1.14+ (20.x) | 25 |
| 26.2 | 0.19.3+ | 0.154.0+26.2+ | 21.0.7+ (21.x) | 25 |
| 26.3 | 0.19.5+ | 0.160.5+26.3+ | 22.0.1+ (22.x) | 25 |
Forge (nothing else required)
- 1.19.2: Forge 43.1.0+ (43.x)
- 1.20.1: Forge 47.1.0+ (47.x)
- 1.21.1: Forge 52.1.0+ (52.x)
- 1.21.11: Forge 61.1.0+ (61.x)
NeoForge (requires Architectury API)
- 1.21.1: NeoForge 21.1.1+ (21.1.x), Architectury API 13.0.11+ (13.x)
- 1.21.11: NeoForge 21.11.0-beta+ (21.11.x), Architectury API 19.0.1+ (19.x)
- 26.1.2: NeoForge 26.1.2.99+, Architectury API 20.1.14+ (20.x)
- 26.2: NeoForge 26.2.0.40-beta+, Architectury API 21.0.7+ (21.x)
- 26.3: NeoForge 26.3.0.0-beta+, Architectury API 22.0.1+ (22.x)
26.1 and 26.1.1 are replaced by 26.1.2, because Architectury API was never built for them.
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:YGxct0Sg:Bm1TjoKd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YGxct0Sg:Bm1TjoKd"
}

