kbrecordzz company blog (formerly known as "This Is (NOT!) A Car Club - Blog")

260316 2: First, linear story part. Then, free roam part where all events can happen in whichever order the player wants. After that... Well, let's wait and see what comes after that. Which part the player is in currently will be stored in a "progress" variable (the new game is too flexible to use the old "cut value" system for knowing how far into the game you've come).

260316: Added map button to BooN.

260315: For all important events that affect other things in the game:
Where, when, how (does the event start)?
What happens after (the event is done)?
Colorize based on how much it affects the game (doesn't change anything, changes a score value, changes how you play the game continuing, changes how other events can and will happen, ...) - we need this because the raw code has too much text for the human eye and brain to grasp context and importance like this
Mark with "IDEA: sdl klasdlk jk" if something needs to be done, so it's easily searchable
"-- WRITE MORE HERE --" if you're not done documenting a section, so you can stop and continue whenever in the future
Don't document everything. Make it short but clear in human language, involving concepts from the code when needed, don't hide anything but leave things out. To make the document easy to come back to and understand even if you forget about it for 6 months. It shouldn't be too long and boring, it shouldn't be underexplained, it shouldn't assume the reader knows any context or remember what they wrote last time.

260314: my "smart and minimal way to document" depends on the reality not changing, because otherwise the documentation will stop being true. so the case for not changing existing code unnecessarily grows even stronger. i think it's time to document first when something has existed for one year without breaking or changing.

i'm thinking of having a similar "smart and minimal" document for the game content too. where things are, what can happen, what characters do, what event leads to other events, etc. because the game isn't linear and i can't test every single scenario.

260313: BooN got a small change in the level order. Now all 4 episodes have some good levels (but after 3-4 levels the bad levels come. Since this is meant to be a casual web game you sit down and play for half an hour or so without saving and continuing any progress, I think that's okay).

260312: letting ideas/things grow. everything takes its time, don't procrastinate and don't rush it

260311: doing

260310: patience. a smart and minimal way to document what i've done and what's left to do, to not create overhead and administration hell but still keep track. no trial and error - just trial, keep it, make it work, to minimize unnecessary rework.

Jun Togawa: link

I thought my project manager would be quiet, but today he said: "Finish things. Don't start new things." I suppose he means just for today.

260309: My project manager (who is also myself) has minimal involvment in my game, but today he rose up from his hole and said one thing: "Reuse buildings and areas you've already created, for your new ideas." Otherwise the creative team (also me) runs the company by themselves.

260308: work, home, and a third space

260307: showcase

260304: highhouses

260303: rich area

260302: Polish Farm

260301: Kårevik

260228: Tall & fat Hårass. Most wanted Hårass. Respect Women t-shirt.
Just Beaver Things...

260212: rebooting mind

260104: Still haven't managed to fix the overflowing HTML body...
... Now I fixed it. I needed to add "display: block" to the canvas's CSS.

260103: Coming up with solutions to the "common problems" in Meditations for creating things.

260102: Fixing inconsistency in canvas size. It overflows the screen...

260101: Fixed a good way to keep debug functions in the game while still not showing them during a normal playthrough. So that I don't have to remove it every time I publish the game (and then add it back again afterwards for editing...).

251230: pixelated Zamantha

251229: got back a picture

251228: preparing the folder

251227: found it

September - December 2025