Gameplans: Modularity of Mods

[OvermindDL1]

@Max

These are the calls the Mechaenetia team would use to interact with the mod API through WASM, if test_func() -> i64 and test_func2(u32, u32) -> u64 were in the API. Right?

Or wasmer instead of wasmtime, but basically the same yeah.

@Gregorius

The Mechaenetia Events that cause HP to be lost would contain also the Body Parts that got hit and the Damage Type. So a Flat HP Mod would just not care about those Parts and simply change your HP Bar depending on amount of Damage (or on amount you get hit), while all others do. Also the Flat HP Mod could be a buffer BEFORE damage is taken to the individual Body Parts, kindof like a Shield.

Shouldn’t it more of give the physical location of the hit, so the character itself can determine what part was hit? Or do you want to force it to be bipeds instead of allowing for robotic or arachnid or whatever characters? Lol

@Max

In this case, that is feasible. But there will be other incompatible systems that your base game will not anticipate - for example maybe there are two magic system mods, one for flat mana and one for body chakras (different magic levels for different body parts). Since Mechaenetia base doesn’t have magic events, the magic system mods add the events themselves. The flat mana mod does not include body parts in its API or events, as far as magic levels are concerned.

So again the physical location would make more sense then passing in a part? Can always query the character for what part is at that location anyway, which could be an open type since mods could add parts.