The mod Castra Krastorio Compatibility+ (1.1.0) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event castra-krastorio-compatibility-plus::on_configuration_changed
Error when running interface function castra-prime.set_enemy_ammo_types: castra-prime/castra-cache.lua:25: attempt to call global 'containsValue' (a nil value)
stack traceback:
castra-prime/castra-cache.lua:25: in function 'update_item_cache'
castra-prime/castra-cache.lua:182: in function 'update_castra_enemy_data'
castra-prime/control.lua:16: in function <castra-prime/control.lua:6>
stack traceback:
[C]: in function 'call'
castra-krastorio-compatibility-plus/control.lua:4: in function <castra-krastorio-compatibility-plus/control.lua:2>

I'm getting this exact same error when creating a new map

Same error pops for me and I'm just trying to continue a game.

I'm guessing just downgrade Castra Prime untill it's fixed

same error, just updated the mod and now i'm getting the same error on my save when i tried to continue

The mod Castra Krastorio Compatibility+ (1.1.0) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event castra-krastorio-compatibility-plus::on_configuration_changed
Error when running interface function castra-prime.set_enemy_ammo_types: __castra-prime__/castra-cache.lua:25: attempt to call global 'containsValue' (a nil value)
stack traceback:
    __castra-prime__/castra-cache.lua:25: in function 'update_item_cache'
    __castra-prime__/castra-cache.lua:182: in function 'update_castra_enemy_data'
    __castra-prime__/control.lua:16: in function <__castra-prime__/control.lua:6>
stack traceback:
    [C]: in function 'call'
    __castra-krastorio-compatibility-plus__/control.lua:4: in function <__castra-krastorio-compatibility-plus__/control.lua:2>

fixed this by downgrading Castra Prime to v0.9.2

I believe 0.9.4 should fix this issue - please try it and let me know. If it doesn't fix the problem I will revert the original PR in order to fix this.

can confirm 0.9.4 fixed it for me, thank you!

I really appreciate both the clear error message, and seeing multiple people posting on this. That made it clear that there was an "audience" for the fix.

I checked, and the error appeared even when my mod wasn't there. Everything is fine now