I do this for fun while waiting for things to load

Arch because I like getting the latest releases of packages

The open source kernel drivers will work. If you want to bother installing their proprietary drivers, I’d recommend reading the Arch Wiki, but you may need to do some things differently even though EndeavorOS is Arch-based.

From the wiki: “Most users do not need these proprietary drivers.”

https://wiki.archlinux.org/title/AMDGPU_PRO

Yay! It looks awesome! I’m going to get my friend to play it with me as soon as it goes live

3. The joy of “figuring it out” and customizing everything you want to the minutest details

Customization is my reason. I’ve got a two-monitor setup in KDE with different panels on each one. Each one is highly customized specifically to me, and the customizations can’t be done in Windows.

It’s easy if you can follow directions, hard if you don’t have directions, impossible if you don’t have directions and don’t know what you’re doing; archinstall is effortless.

It’s hard to give advice about how code should be structured, since there’s many ways of accomplishing the same things, but you’re doing the right thing by thinking about scalability before you get too deep to change it.

You could try separating eacg trigger condition into their own functions, so that if an OnAttack gets triggered it will only check and loop through OnAttack abilities.

Something like:

OnAttack.connect( CheckOnAttack )
OnDamaged.connect( CheckOnDamaged )

func CheckOnAttack( ATTACK_TYPE ):
          match ATTACK_TYPE:
                  ....

func CheckOnDamaged( DAMAGE_TYPE ):
         match DAMAGE_TYPE:
                  ....

“Hijinks” makes me think of exactly the kind of casual mess-with-your-friends gameplay that can happen with Nintendo games. I like it.

As a side note, I’m curious to see how the game turns out. Nintendo Land was the only game I’ve played on the Wii U that made proper use of the game pad, and the ghost mansion was my favorite minigame.