dr_null @dr_null@mastodon.gamedev.place

To make rust debugger work in neovim I had to apply patch from somebody's else fork on rust-tools.nvim. Now it kind of works. Maybe it would be better if I just downgraded DAP extension from vscode.

Continue my adventure with new Unity version. Google dependency resolver needs java, but java isn't available inside of sandboxed environment. It can't see JDK installed with Unity of course, needs proper JAVA_HOME. So we need to install special flatpak version of it. But not just any java, only openjdk11 works. And then override JAVA_HOME for unity flatpak.

So, java from JDK supplied with Unity 2021.3.4 doesn't have "executable" flag by some reasons. Just like sdkmanager and other executables.

And I moved to Fedora as my distro, from Arch. Didn't have problems with Arch, just want to use same disto on every machine in home.

So, project that included HTN planner that I was working on was frozen for better times.
But in meantime I moved to Perm because of all uncertainty caused by stupid war. It's nice to be back after 6 years in Moscow. And least COL here is much lower.

Did some basic implementation for HTN planner. Got a lot of insights. If Context (which is world state for actor) is struct then we don't need any sort of cloning. So planning can be easily multi-threaded. But it limits state to POD types.
And I decided to split tasks and actions, so actions can have state and tasks are stateless and just create actions when needed.

Using HTN planner for characters in mobile management game sounds like a good idea.

Started new little project. Some sort of support program for bubblewrap, so sandboxing programs on Linux won't be that painful. Basic idea is to create declarative profiles and then combine them into profile for concrete program with overrides.

My "mp3 player", which I've bought to cut reliance on smartphone, don't want to play ogg vorbis trough bluetooth. Strange decision.

So, there's a way to buy games on Steam even under sanctions, bought "Stellaris: Overlord" yesterday. Which means I won't miss second part of "fault: Milestone two".

Mechanical keyboards are really nice to use tbh.

Creating architecture for our next game. Initial plan was to create clear layers, where model and view totally separated. But designers want to use existing tools that can only work as Unity components. So new architecture is compromise of some sort - model layer have to live like MonoBehaviour in GOs, not separated from Unity. It isn't perfect, but I think it's nice compromise. At least I don't need to implement pathfinding and behaviour tree with editor.