Edaqa Mortoray

I make puzzles, food, and code.

Wishlist my upcoming game, Rabanaz, a deck (chip-bag) building gambler.
https://store.steampowered.com/app/3380650/Rabanaz

"the Way to Hexet": Find the lost metal bands in the northern forests. https://edaqasroom.com/game/the-way-to-hexet

Games: https://edaqasroom.com/
Kitchen: https://edaqaskitchen.com/
Blog: https://mortoray.com/
Discord: https://discord.gg/NfPJNF3fsa

Last Notes

2024-12-27 14:16:49 CET

Somehow, the primary shop in my game has the code level name as MiniShop, despite having 5 sub-screens. There's another upgrade-shop, but it's actually smaller.
I debate whether it's worthwhile changing code symbols as the meaning in the game solidifies. I do find myself talking about things that players have no idea about, since I use the wrong name.
#gamedev #indiedev
https://s3.wasabisys.com/pmg-media/media_attachments/files/113/724/966/460/015/112/original/9c9a986c76bf6762.png

2024-12-21 22:08:01 CET

- reply

I guess I'm not fully understanding what #nullable does then, since it clearly does not mean things can't be null, at least not in all contexts.
I did use `where T: notnull` now and the error also goes away. But in my mind, that should be the default when #nullable is enabled.

2024-12-21 14:52:01 CET

- reply

But yes, nonetheless, declaring it nonnull does fix the problem.
`class Something<T> where T : notnull`
But I still don't understand why. It seems to go against what `#nullable enable` means.

2024-12-21 14:50:32 CET

- reply

But I have `#nullable enable` on the file, implying all references are non-null unless declared otherwise, like `T?`.
Also, if I mark source as `T? source` then I get errors in my code, implying that it isn't actually nullable, except in this circumstance.

2024-11-23 11:36:55 CET

It's hard to divorce the state model of a game piece from the animation. The duration of an animation can block a state transition until the animation is complete.
This is quite different from typical app programming where animations are virtually irrelevant in terms of data state.
I still do state-based for my game, but I either need to have the state be aware of transmission times (fragile), or have the render layer be able to lock a piece (invasive).
I suppose this isn't an issue for physics based games, where the underlying animation state is a part of the true physics state. So this may only be a problem for "faked" systems like the machine in my game.
#gamedev #indiedev

2024-09-08 13:06:52 CEST

It's annoying when the thematic word for an item changes from the code word. I had "gears" in my game, but they've been replaced with "vaccuum tubes" instead. I keep confusing the illustrators when I refer to gears.
I never know when is the right time, if ever, to change the terminology in the code.
#gamedev #indiedev

2024-09-08 12:29:06 CEST

I'm starting to think the reason rougelikes have custom game runs is just so the developer can test the various items and combinations. I'll likley need the same thing in my new game.
I might just use a YAML file... though not as fun...
#indiedev #gamedev

2024-08-24 18:21:19 CEST

Just imagine this dropping and unfolding from the top of the screen...
...so much gameplay to worry about prior to these animations though. But you can see all the pieces are prepped for it!
#indiedev #gamedev #screenshot
https://s3.wasabisys.com/pmg-media/media_attachments/files/113/017/911/574/804/428/original/ee1b2d6a0434e235.png

2024-08-24 17:34:44 CEST

I'm making good progress on the new graphics for my upcoming game. Chips, tubs, and font simply not done yet. Then there'll be many deatils to fix as I get the animations in place.
#indiedev #gamedev #screnshotsaturday
https://s3.wasabisys.com/pmg-media/media_attachments/files/113/017/725/911/124/696/original/85573065ac85887d.png