I just realized that my (coming soon) skill tree could be an incremental game in itself.
I once said that I hate node-based skill trees. Why? Because they're the perfect balance of great results and low effort (excluding the balancing part).
#gamedev#indiedev#steamgames
Frankly, a unit test can be a little bigger as long as it serves its purpose of testing expected behavior. Pure unit tests that test logic just for the sake of testing logic are useless as-is if they don't provide any real value. But this is a potato, potahto situation. These tests can be called unit tests, module tests, etc.
Integration tests, in my case, cover huge chunks of UI flows, including transitions between maps, achievements, and so on. But yeah, these could still be considered module tests. In my case, this is simply the smallest type of test.
You're not wrong, though. In my case, these are just the smallest units of testing, and a visual pass actually tells me something, whereas a text "pass" doesn't really tell me anything.
This is my unit test, running at the actual resolution of 1024Γ1024, so I can run tests much faster.
Why is this a proper test?
β¬οΈβ¬οΈβ¬οΈβ¬οΈβ¬οΈ
I have replaced all procedurally generated map skins with handcrafted ones.
I learned a lot, especially in terms of how much detail you need to put on smaller maps vs. bigger maps so as not to overwhelm the eyes with details.
Over 200 copies sold.
I found out that 2 content creators are going to feature my game soon - I wanted to give them keys, but they said they already have the game and they like it :D
I don't need to make a living out of it, but seeing this:
Median time played: 4 hours 7 minutes
Average time played: 6 hours 20 minutes
makes it worth the effort.
Did I flop the release?
Kind of yes and no.
Did I make mistakes I will take into my next projects?
Oh yes.
I've never learned so much in such a short period of time in my life, and I am a software engineer.