Bridging the Gap Between MK:Ultra Spells and DivineRPG Mobs
If you have ever combined the arcane power of MK:Ultra with the sprawling dimensions of DivineRPG, you have probably noticed something frustrating. Your carefully crafted spells sail right past hostile mobs from DivineRPG as if they were invisible. That happens because the MKfactions mod uses an entity_default_factions.json file that does not recognize the massive roster of creatures added by DivineRPG. Thankfully, a community-made datapack fixes this exact problem for Minecraft 1.21.1, and it is already tested on multiplayer servers.
Why Spells Ignore DivineRPG Creatures
MK:Ultra runs on a faction-based targeting system. Every mob in the game belongs to a faction that determines whether your spells consider it a friend, foe, or neutral bystander. The issue is that DivineRPG introduces dozens upon dozens of new entities across its biomes and dimensions, from overworld nuisances to end-game boss monsters. Because the base MKfactions configuration only covers vanilla and internally registered mobs, those new DivineRPG entities have no assigned faction. Without that critical data mapping, the spell mechanics simply skip them during target selection, leaving your spellbook useless against custom creatures.
How the Compatibility Patch Works
This datapack does not replace either mod or require any complicated crafting recipes. Instead, it alters the entity_default_factions.json file inside the MKfactions mod so that MK:Ultra spells can target all of the many DivineRPG mobs you will encounter. The patch was built with direct assistance from Kovak, the MK:Ultra developer, which means the faction assignments align with the mod's intended balance and threat calculations. Once the files are in place, your fireballs, heals, debuffs, and buffs will interact with DivineRPG creatures exactly as they do with vanilla zombies, creepers, or skeletons. It is a clean fix that respects both mods without bloating your server.
File Structure and Placement
Getting everything into the right folders is the most important step, and precision matters here. You will need two specific items: a pack.mcmeta file and the updated entity_default_factions.json. Here is exactly where they belong on your server or local instance:
- pack.mcmeta goes into minecraft/your_world/datapacks/factions/
- entity_default_factions.json goes into minecraft/your_world/datapacks/factions/data/mkfaction/data_maps/entity_type/
The word "factions" in those paths can actually be anything you want, as long as the folder name matches exactly for both files. Just replace "your_world" with the actual name of your world directory. Because the original files could not be uploaded in their pre-nested format due to submission restrictions, you must create those folders manually. After dropping the files in, run the reload command or restart your server so the MKfactions mod picks up the new mappings during its next initialization.
Installation Tips for Modded Playthroughs
Before you drop these files in, double-check that your server or client is running Minecraft 1.21.1, since that is the specific version this patch was built and tested against. Using it on older or newer versions might cause data map errors or simply fail to load. Because this is a pure datapack solution rather than a full mod jar, you do not need to install anything extra on the client side if you are playing on a dedicated multiplayer server. Everyone connected will automatically benefit from the updated faction data as soon as the server recognizes the pack. If you are running a single-player world, the same folder rules apply, and you can verify the load order by checking the datapack list when you first launch the save.
Keeping track of multiple mods and their dependencies can get messy, especially when you are juggling dimension overhauls, new biomes, and complex magic systems in the same mod list. If you want to avoid manual file hunting, this mod can be easily installed via the foxygame.net launcher — a convenient, flexible, and modern Minecraft launcher where you can download mods right from the menu. Having that kind of streamlined control makes experimental combinations like MK:Ultra and DivineRPG far less intimidating, letting you spend more time exploring and less time troubleshooting folder paths.
Testing and Community Validation
One of the best parts about this patch is that it has already seen real action on a multiplayer server. That means the faction tags have been stress-tested against actual combat scenarios, not just a quiet creative flatworld with no stakes. Players reported that spells correctly identified DivineRPG mobs as hostile targets, which opened up entirely new strategies for dungeon crawling through the mod’s late-game dimensions. Since the file is lightweight and only touches the MKfactions data map without rewriting entity AI or adding new blocks, the risk of conflicts with other updates or mechanics is extremely low. You get all the compatibility benefits without sacrificing server performance or stability.
Final Thoughts on Cross-Mod Compatibility
Minecraft’s modding community thrives when separate projects can talk to each other instead of existing in isolated silos. DivineRPG brings an enormous bestiary of challenging mobs to fight, while MK:Ultra gives players a deep spell-casting system that deserves to work across every biome and dimension you visit. This datapack is a perfect example of how a few carefully edited lines of JSON can bridge two massive mods without forcing players to wait for an official update that might never come. Whether you are hosting a magic-focused server for your friends or just want your wizard build to feel complete while conquering the Iceika dimension, this compatibility patch is an essential addition to any mod list that pairs these two giants together.