All versions
1.1.5
Release
Rei Chikita Mod Evangelion 1.1.53 months ago 35
Compatibility
Minecraft: Java Edition
1.18.2
Platform
Forge
Supported environments
Client and server
Changes
Version 1.1.5 (Oct 18, 2022) — [MC 1.19.2, 1.18.2, 1.16.5]
Vehicles & Mechs
- Added Eva 01 as a decorative entity dropped upon defeating Rei Mediana. Features 3 distinct display poses cycled via Right-Click.
Version 1.1.4 (May 31, 2022) — [MC 1.18]
Equipment
- Added the Spear of Gaius.
Assets
- Added dynamic animations for Rei Chikita, Asuka Chikita, Bandaged Rei, Helmeted Rei, and Mari Chikita.
Version 1.1.3 (Aug 18, 2021)
Entities
- Added Mari Chikita as a tamable entity.
Version 1.1.2 (Jul 9, 2021)
Fixes
- Resolved a crash associated with spawning Rei Mediana.
Version 1.1.1 (Jul 7, 2021)
Entities
- Added Asuka Chikita (tamable using Chocomilk).
Equipment
- Added the Spear of Cassius.
Version 1.1.0 (Jul 2, 2021)
Entities & World Generation
- Added Rei Chikita (Antifunas Helmet Variant). Spawns exclusively in Jungle biomes and is immune to Rei Mediana attacks.
- Added Pen Pen as a tamable entity using any fish type.
Version 1.0.6 (Jun 4, 2021)
Fixes
- Addressed minor internal errors to optimize gameplay performance.
Version 1.0.5 (May 22, 2021)
Equipment
- Added the Spear of Longinus, craftable by combining Longinus Spear Fragments dropped by Rei Mediana.
Version 1.0.4 (May 11, 2021)
Assets & Fixes
- Resolved model display errors and improved shadow rendering for Rei Chikita.
Version 1.0.3 (May 7, 2021) — [MC 1.16.5]
System
- Backported mod compatibility to Minecraft 1.16.5.
Items
- Added the Rei Chikita Plush as a decorative block.
Version 1.0.2 (Apr 22, 2021)
Entities
- Rei Mediana: Introduced as a formidable mini-boss. Upon defeat, transforms into a tamable Bandaged Rei.
- Rei Chikita: Increased natural spawn rate by 300%.
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:PesFb6Ie:aCpSoe49"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PesFb6Ie:aCpSoe49"
}

