Tags
Creators
Details
1.4
Compatibility
Changes
Version 1.4!
New Feature: Secret/Sub Events!
These new events are special evennts that rarely happen, they can stack on top of the current event, allowing for some intresting combos!
Pumpkin Head
- This Sub-Event causes a pumpkin to be placed on the player's head, if the player is wearing a helmet, it will spring off right into the ground!
- The pumpkins come with 5 random name variantions, this adds some fun uniqueness to each player.
- You can avoid the pumpkin by carving it with the Pumpkin Carver.
New Custom Item!
Pumpkin Carver
- This item allows you to carve the pumpkin right off your head!
Recipe Reworks
- Forcefield Recipe reworked to be slightly cheaper, replacing the beacon with a single piece of tinted glass.
- Event Shuffler now uses a piece of quartz and a breeze rod, replacing the previous clock, and echo shard.
- World Token duplication recipe now uses a netherite upgrade template, and an enderpearl, replacing the eye of ender, and netherite scrap.
Bug Fix and QOL Features
Relog Events
- Previously when logging off during an event change, when you logged back on you would not recive the new event's effects, and keep the previous event, until a new event rolls.
- Now gives you a 2 seecond grace period before welcoming you back and applying the current event. (events like warpall, and token hunt do not apply)
Qol Changes
-
Fixed multiple issues with midas event not properrly registering the player wearing a midas crown.
-
New Credits Section in the admin menu.
-
Fixed Gameplay Admin menu section, not saving custom timer when the world reloaded.
-
Token frenzy now 1.5x as commmon
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| MWE_Resourcepack_recipebookfix.zip | Optional resource pack | 2.79 KiB |
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:6QxXbmvf:vrLB5s0c"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6QxXbmvf:vrLB5s0c"
}

