Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 4 years ago
Updated 2 weeks ago
All versions
2.2.0-1.20.1-forge
Release
Fake Players 2.2.0 (1.20.1 Forge/NeoForge)2 weeks ago 411
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Changes
v2.2.0
- Fakes can fight with ranged weapons (#58). A fake holding a bow, crossbow or trident now fights like a skeleton instead of walking into melee: it holds its distance, circles the target, backs off when the target closes and looses when it has a clear line of sight. Bows are drawn and released properly, crossbows charge and fire on the pillager's timing, and tridents are thrown. This applies wherever a fake already fights, so a Guard on patrol and a fake defending itself both use it.
- Ranged fakes shoot their own ammunition (#58). Arrows come out of the fake's inventory, offhand first, so tipped and spectral arrows work and a fake that runs out falls back to melee rather than shooting for free. A thrown trident is not recoverable, so the held one is damaged instead of being consumed and the fake is never left unarmed. The Infinity enchantment is not honoured yet.
- The management screen can be opened with a key of your choosing (#57). There is a new "Open Fake Player Menu" binding under a Fake Players category in the controls screen. It is unbound by default, so sneak + right-click keeps working exactly as before. Bind a key and the menu opens from that key instead while you are looking at a fake, and sneak + right-click stops opening it, which gets Fake Players out of the way of mods that claim right-click on mobs.
Thanks to Raileen and user_xkelxur3h8vuiwfb for the requests.
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:1RSY6DQH:hTOxAIIY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1RSY6DQH:hTOxAIIY"
}

