Kissaki

I found the announcement (quoted in the article) interesting and worth sharing, even without knowing or seeing the game.

Excerpts (I recommend reading the full thing):

My primary inspirations were the Japanese living doll myth and my experiences urban exploring in Germany (many backgrounds were crafted from photos I had taken).

The final act obviously deals with a difficult topic, sexual assault. I wanted the ending to be shocking, that was intentional, but never to cause harm. Instead, I thought I had crafted things in a way that would act as a jumping off point for some difficult discussions.

Secondly, the girl was never meant to look underage. In retrospect, I should have been more careful to ensure there was no ambiguity. Because she’s a doll (not human), I didn’t consider the possibility of misinterpretation as thoroughly as I should have.

This was also written long before the #MeToo movement, and I was a lot less educated on all the nuances of topics like these at the time.

If I had written it now, in my mid-30s, in 2025, it would be very different. Still, some choices I stand behind:

Do you have experience representing difficult topics in art? Weighing or deciding on respectful or acceptable representations, on the degree of deliberately shocking or uncomfortable representation?

Or do you remember scenes in games or otherwise in art that you found uncomfortable or shocking? In a good (well-represented or tactful) way or a bad way?

Even after users change their account password, however, it remains valid for RDP logins indefinitely. In some cases, Wade reported, multiple older passwords will work while newer ones won’t. The result: persistent RDP access that bypasses cloud verification, multifactor authentication, and Conditional Access policies.

That last part - optimistic move application with what games people sometimes call “rollback” - is about 1,600 lines of code that took me a ~7 days of fulltime work to write. I don’t remember the last time I wrestled with a problem that hard!

Developer Information / Release Notes

Developer Information / Release Notes

My home PC is still on Windows 10 22H2, while my work machine is on Windows 11 23H2, and, to no surprise, neither machine reproduced the issue – Skimmer spawned on the water just fine, creating one via script and putting CJ in a driver’s seat worked too.

That said, I also asked a few people who upgraded to 24H2 to test this on their machines and they all hit this bug.

I have a likely explanation for why Rockstar made this specific mistake in the data to begin with – in Vice City, Skimmer was defined as a boat, and therefore did not have those values defined by design! When in San Andreas they changed Skimmer’s vehicle type to a plane, someone forgot to add those now-required extra parameters. Since this game seldom verifies the completeness of its data, this mistake simply slipped under the radar.

What made the game work fine despite of this issue for over twenty years, before a new update to Windows 11 suddenly challenged this status quo?

GitHub

Theia IDE is compatible with VS Code APIs and can install and use VS Code extensions. Has additional APIs for customizations not available in VS Code.

Have you tried Theia IDE? Any assessments or experiences to share?

For those familiar with Git terminology:

The simplest way to assemble a triangular workflow is to set the branch’s merge key to a different branch name, like so:

[branch “branch”]
   remote = origin
   merge = refs/heads/default

This will result in the branch pullRef as origin/default, but pushRef as origin/branch, as shown in Figure 9.

Working with triangular forks requires a bit more customization than triangular branches because we are dealing with multiple remotes. […]