Probably The Lord of the Rings. I read the entire thing almost ten years ago, and only remember bits and pieces. It’s so long that I could definitely read it multiple times and still learn new information every time I read it.
Probably The Lord of the Rings. I read the entire thing almost ten years ago, and only remember bits and pieces. It’s so long that I could definitely read it multiple times and still learn new information every time I read it.
- 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:
....
Well, I have freckles all over the place, so my pattern was chosen already.
Nonsense, LOTR has been sold as a single volume for a long time now. I have the 50th anniversary edition, which is a single physical book.