Links
Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 3 years ago
Updated 2 years ago
All versions
fabric-1.1.0+mc1.20.4
Release
SpectatorPlus 1.1.03 years ago 995
Compatibility
Minecraft: Java Edition
1.20.4
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Required content
Any compatible version
Changes
SpectatorPlus 1.1.0
- Added open screen syncing (Currently only supported on Paper servers)
- This feature allows spectators to view the currently open container screen of players (e.g. a chest, furnace, or even the player's inventory)
- The player's own inventory will only be automatically shown when the spectated player has the SpectatorPlus client mod installed as well. This is due to vanilla Minecraft not sending a packet when players open their inventories, so the server doesn't know when it is opened
- It is also possible to configure the plugin to show some synced screens to clients that don't have the mod installed as well
- Many aspects of the mod and plugin are now configurable, on both the client and server side
- Added option to automatically start spectating players when teleporting using the spectator hotbar menu.
- Added option to hide other spectators, as well as an option to not highlight other spectators when using Vanilla's "Highlight Players" keybind.
- Improvements to Paper spectator workarounds
- Fixed Vanilla
/spectatecausing a glitched state when entity currently isn't tracked - Stopped relying on
PlayerTeleportEvent, instead directly listen to Paper'sPlayerUntrackEntityEvent - Now works for spectating any entity, not just players
- Send
ClientboundSetCameraPacketdirectly when possible, instead of fully re-applying the spectator target on the server side
- Fixed Vanilla
Full Changelog: https://github.com/hpfxd/SpectatorPlus/compare/v1.0.0+1.20.4...v1.1.0+1.20.4
Optional dependencies
Any compatible version
Any compatible version
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:qnFMs6Ja:do6gzvAO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qnFMs6Ja:do6gzvAO"
}

