BetaChangelog.gg
Myriad Mayhem
Steam News 17 October 20257mo ago

0.73.0.0 (@Experimental Branch)

Summary This patch doesn’t add much visible content, as most of the work focused on updating the game engine and tools. A new ability — Meteor — has been added. Due to a critical security issue in Unity, I had to upgrad…

Update log

Full Myriad Mayhem update

The complete published notes, normalized for clean reading and source attribution.

Extracted changes

2 fixes5 additions3 changes0 removals
  • Workshop
  • Gameplay
  • Security
  • Performance
  • Balance
  • Fixes
addedSummaryThis patch doesn’t add much visible content, as most of the work focused on updating the game engine and tools .
addedSummaryA new ability — Meteor — has been added.
changedSummaryDue to a critical security issue in Unity, I had to upgrade the project’s Unity version right away. While necessary, the update caused several compatibility issues with existing tools — but after some fixes and updates, the Pathfinding is now running smoother than before!
addedGame mechanicsNew Pathfinding AI – The Unity upgrade broke the old pathfinding system, and fixing it turned out to be trickier than expected (on top of Unity changing or removing previously working features). It seems however the new AI are much better at finding their way. Load times have also improved significantly — about 50% faster when starting a new match.
fixedGame mechanicsUnity Update Side Effects – Updating Unity introduced bugs. And I’ve fixed a bunch and tried to catch them all, but I could easily have missed some, so I’m sorry you have to experience them in that case. Hopefully, I won’t be “highly encouraged” to update Unity again anytime soon — each upgrade tends to break existing systems and eats up valuable time I’d rather spend making new content. And would take days to read through all their patch-logs to determine what I need to update in my game to work properly, for example: it’s no longer possible to directly set a Sprite Renderer’s material color in code when using the Lit shader (which I use so sprites can receive world light and cast shadows). I had to bake in a _Color variable into the shader and update it via a MaterialPropertyBlock, like this: [c]_Renderer.GetPropertyBlock mbp); mbp.SetColor("_Color", _CombinedColour); _Renderer.SetPropertyBlock(mbp [/c] Weird approach, in my opinion — but at least it works again! :).
addedContentNew ability - Meteor This one sure extended the time to finish the patch as it is more like three new abilities with new mechanics that the code had to be modified to support. But, with the new ability system, so can any other ability use those features right from the bat, without having to write any code, things like: CastTime Abilities with secondary effects (sub-abilities) - This was more complex to add then one might think. Telegraphing (red circle indicating where things will go ouch) Abilities can now have “FieldSize” attribute - So: Size = Actual abilities size (e.g. Firebolt projectile size) AreaSize = The actual area an effect is affecting, e.g. fireball’s “explosion area” FieldSize = The field stuff can happen in, e.g. Meteor's possible field they can land in, when using MeteorShower.
Reduced Beam - Blast talent damage modifier-75% to -80%Increased Beam - Devastation,+50% to +60%

Summary

This patch doesn’t add much visible content, as most of the work focused on updating the game engine and tools.

A new ability — Meteor — has been added.

Due to a critical security issue in Unity, I had to upgrade the project’s Unity version right away. While necessary, the update caused several compatibility issues with existing tools — but after some fixes and updates, the Pathfinding is now running smoother than before!

Game mechanics

  • New Pathfinding AI – The Unity upgrade broke the old pathfinding system, and fixing it turned out to be trickier than expected (on top of Unity changing or removing previously working features). It seems however the new AI are much better at finding their way.

    • Load times have also improved significantly — about 50% faster when starting a new match.

  • Unity Update Side Effects – Updating Unity introduced bugs. And I’ve fixed a bunch and tried to catch them all, but I could easily have missed some, so I’m sorry you have to experience them in that case. Hopefully, I won’t be “highly encouraged” to update Unity again anytime soon — each upgrade tends to break existing systems and eats up valuable time I’d rather spend making new content. And would take days to read through all their patch-logs to determine what I need to update in my game to work properly, for example:

    • it’s no longer possible to directly set a Sprite Renderer’s material color in code when using the Lit shader (which I use so sprites can receive world light and cast shadows). I had to bake in a _Color variable into the shader and update it via a MaterialPropertyBlock, like this: [c]_Renderer.GetPropertyBlock mbp); mbp.SetColor("_Color", _CombinedColour); _Renderer.SetPropertyBlock(mbp [/c]

    • Weird approach, in my opinion — but at least it works again! :).

Content

  • New ability - Meteor

    • This one sure extended the time to finish the patch as it is more like three new abilities with new mechanics that the code had to be modified to support. But, with the new ability system, so can any other ability use those features right from the bat, without having to write any code, things like:

      • CastTime

      • CosmeticAbilities with secondary effects (sub-abilities)This was more complex to add then one might think.

      • Telegraphing (red circle indicating where things will go ouch)

      • Abilities can now have “FieldSize” attribute - So:

        • Size = Actual abilities size (e.g. Firebolt projectile size)

        • AreaSize = The actual area an effect is affecting, e.g. fireball’s “explosion area”

        • FieldSize = The field stuff can happen in, e.g. Meteor's possible field they can land in, when using MeteorShower.

Quality of Life

  • Vibrant colors is now off by default - After the latest Unity version, so did it make it look much worse, even when I’ve tried to lessen the effect, so I would recommend turning it off (or at least try it off, as it is not as visually appealing anymore).

Balancing

  • CosmeticReduced BeamBlast talent damage modifier from -75% -> -80% (Balance-wise, so should it be -90%, but it felt really boring)
  • CosmeticIncreased BeamDevastation, from +50% -> +60%

Other

  • Fixed a few talent value-formatting typos.

  • Added the value (100%) to Friendly Fire to be more descriptive.

  • Made the “level up window” taller, to easier fit larger talent-descriptions.

  • Beam ability with “Piercing”, will now continue its maximum length, if it can pierce more then it hit (before, it always stopped at max-hitted targets, even if that was 20 units, which

Source

Steam News / 17 October 2025

Open original