All versions
- Journey of Slime: Get to the other side without being squished by trains or drowning in rivers. Difficulty affects speed and frequency of both trains and logs, as well as the length of the map.
1.1.0
Release
Evil Captcha 1.1.02 years ago 169
Uploaded by
Compatibility
Minecraft: Java Edition
1.21–1.21.4
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
- added 2 new captchas
Spoiler
- Sponsor: You're shown an ad you need to skip after waiting for a few seconds (time increases based on difficulty) if you click the ad instead of the skip button, you "download" unwanted addons that affect your screen for a while.- Journey of Slime: Get to the other side without being squished by trains or drowning in rivers. Difficulty affects speed and frequency of both trains and logs, as well as the length of the map.
- added more config options, mainly for dis-//enabling specific sources of captchas
- added yayConfig (access via
/captcha configor/yayconfig captcha:world) - added reward loot table
- empty per default, you can use datapacks to customize it
- added cap to visual gambling coins
- added more config options (mainly for en-//disabling sources of captchas)
- added commands to set, reset and check both global (server-wide) and local (of specific players) captcha difficulty
- fixed issue that caused certain captchas to completely break when started at a too low difficultyunexpectedly)triggered using a command
- added config entry to dis-//enable reward loot tables more easily
- improved flow of loot containers being locked behind captchas
- the loot container is now automatically openend after the captcha is completed successfully
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| captcha-1.1.0-sources.jar | Unknown | 3.95 MiB |
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:qAfRVAcU:p0H6nqeB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qAfRVAcU:p0H6nqeB"
}

