Last week,
I talked about a fairly sophisticated attempt at solving my
2D discrete physics problem,
which ultimately turned out to have unfixable flaws. But I need this problem
solved for my game, so I decided to relax my requirements for the time being.
As I previously wrote, I
recently fell in love with the Kotlin language. It’s been over four months
since that post, and my enthusiasm has not diminished. In this post, I’ll show
how I combined some of Kotlin’s best features to write some extremely readable
unit tests.
In the last
post, I
described my requirements for a 2D discrete physics system I’m working on. Now
that I’ve laid out what the system should do, let’s turn to the implementation.
For a new game I’m working on, I need some 2D “physics” that work in discrete
time and discrete space. In other words: every object consists of one or more
blocks aligned to a square grid, and time advances in turn-based steps. If
you’re thinking of Sokoban, you’ve got
the idea:
As of just now, https://frozenfractal.com is a
thing. This means you can browse my site securely, knowing that the NSA can
probably not see which pages you are viewing. Sort of.
If you’re developing a game for mobile devices, chances are you have run into
the words “texture compression”. Texture compression helps to keep video memory
usage down, reduce download sizes and loading times, and may even reduce power
consumption. In this article, I take a comprehensive look at what the options
are.
Kotlin is a programming language developed by
JetBrains (the makers of IntelliJ IDEA), which compiles down to Java bytecode.
I got over my initial aversion for the ugly name, and decided to give it a try.
Now I never want to go back to Java. Here’s why.
This weekend, November 5th and 6th (and actually yesterday as well), Twistago has a stand at one of Germany’s largest board game fairs, Spielwies’n, in the MOC in München. Come visit us if you’re in the area!