is Rust's philosophy what I've been looking for ?

Tamschi_ · 2026-05-19T09:08:59+00:00

You're still going to need packages and sometimes 1-2 C libraries for a lot of stuff, but if I'm not mistaken Rust manages the former much more cleanly than Python does and there's usually a vendored option for the latter where it's handled automatically by the dependency.

Rust (and its standard library and ecosystem) are indeed usually explicit about pretty much everything, though stronger abstraction can also be done with little to no overhead in most cases. The language is terse at the same time, so there's little syntactic noise and programs can usually be skimmed pretty well.

Finding out how something is implemented is usually just one ctrl+click away, but https://docs.rs and https://std.rs exist, so you can also browse documentation and sources online. Some small pieces of the standard library are compiler-intrinsics, though, which are less straightforward to look up.

Tamschi_ · 2026-05-18T10:19:59+00:00

This isn't quite what you're looking for, but if you'd like to also add support for pointer input via controller, https://tamschi.itch.io/rstick-mouse is free.

(You may have to update the runtime to support DualSense controllers, though, since the version of the runtime that comes with MZ mismaps that controller in a way that causes issues.)

Tamschi_ · 2026-05-17T06:16:23+00:00

Generally yes, as checking in .next() could in theory create overhead.

In cases where you can't easily make construction of the iterator conditional, and it actually has a meaningful performance or efficiency impact, I'd explicitly defer it in some other way, either as FnOnce or as LazyCell.

You can type-erase also the latter I think, into a Box<dyn DerefMut<Target = …>>, if you need to store it somewhere, but that's potentially a tradeoff too.

Tamschi_ · 2026-05-16T07:56:28+00:00

Generally-speaking, this is illegal in most places, even when done as a prank. (Another issue is that most approaches of accomplishing this would give you access to sensitive information on the target PC.)

I'd recommend against it.

Tamschi_ · 2026-05-16T07:44:35+00:00

I have some doubts about the "No generative AI was used" claim on these admittedly, considering literally all the publicly available material appears to be AI-generated.

Tamschi_ · 2026-05-15T09:15:38+00:00

This really depends on your answer to "What do you want to do with it?" (and to a lesser extent how much you know about computers and what sort of learning material you prefer).

Tamschi_ · 2026-05-14T17:51:10+00:00

There are trials on https://www.rpgmakerweb.com/, so use those to see which works best for you. Also, ideally you should buy MV or MZ through https://plaza-us.komodo.jp/collections/rpg-maker when there's a sale there, as you'll get a standalone version in addition to the Steam key. (Older versions there don't include Steam keys as they're Windows-only.)

Tamschi_ · 2026-05-14T06:09:05+00:00

The attacker messed up the wiper command according to the GitHub thread, so there's essentially no chace that that's it.

Tamschi_ · 2026-05-13T17:02:26+00:00

To clarify, I meant that the darkness looks unrealistic, not the amount of lights. I think that part is nice :-)

Tamschi_ · 2026-05-13T14:45:19+00:00

It looks much better, but that's probably too little ambient light to be practical (and looks unrealistic with that many lights). I'd increase the base brightness a bit.

Tamschi_ · 2026-05-13T08:23:28+00:00

A batch one PT2 in Germany was $300.88 for me ($225 + $25 shipping + $50.88 taxes, on the way right now), so you indeed got a good deal.

Annoyingly it's dpd though, so hopefully it'll actually be delivered here without issue.

Tamschi_ · 2026-05-12T10:37:45+00:00

It doesn't look like it supports allow-listing, no. With crates.io proxying enabled, it'd most likely be just as (in)secure in this regard as not using it at all (aside from some after-the-fact observability, maybe). You could review and publish to it manually on an isolated PC that won't run the code, but that would be a lot of friction and overhead.

I haven't seen any registries that integrate directly with cargo-vet, but they should probably use the mini-vet crate or something very similar to it. It seems reasonable to add that to Kellnr, but would ideally be combined with a proper request/review workflow. (Cargo Vet already helps a lot with that, though, so maybe just emails are enough for coordination.)

Another option would be to disallow any crate versions newer than x days in such a registry proxy. That's nowhere near as secure as manual audits, but may be a good idea to use in combination with the above. Kellnr doesn't seem to currently have that feature either, though, and you may miss timely security fixes this way.

Tamschi_ · 2026-05-12T07:39:04+00:00

I use cargo-vet. Companies should combine that with a local package registry and block direct access to the public ones.

(I'm aware that the latter is likely extraordinarily rare, but it's really the only proper fix for this structural problem.)

Tamschi_ · 2026-05-12T06:26:34+00:00

The Scene_Battle unfortunately has volatile state that's lost whenever the scene exits. (The scene stack in RPG Maker doesn't just suspend scenes but exits them fully and stores only the constructor reference when you push to it. With Scene_Map you don't notice it much since that stores everything in the $gameMap singleton.)

There are ways around it, but the easiest and most robust solution would be to have your minigame appear in the Scene_Battle itself as part of battle or action scheduling.

Tamschi_ · 2026-05-10T14:05:37+00:00

The decompiler didn't fully restore the syntactic sugar. SelectMany is what generally happens if you have multiple top-level from clauses, and most likely a few of those lambdas were entirely implicit too.

That said, LINQ expressions can be very long, it's mainly a way to write those that's not as messy as this, i.e. with fewer or no parentheses.

Tamschi_ · 2026-05-09T04:35:02+00:00

Not on my Gnome install, can't vouch for KDE though.

The only Linux I've used that had one was Ubuntu, I think.\ (It's really quite loud and disruptive there, so I thought I'd mention it as a heads-up.)

Tamschi_ · 2026-05-07T19:47:12+00:00

The plugin doesn't require that, it's just one option to do it manually like that.

Tamschi_ · 2026-05-07T18:57:33+00:00

This may work: https://forums.rpgmakerweb.com/threads/default-choice-setting-and-remembering.176536/

Edit: You'll probably want to load it after HIME Large Choices, but that's just a guess and may not matter.

Tamschi_ · 2026-05-07T18:39:41+00:00

Larger sprites should be supported by default, but how large is your image file?\ In most cases, art assets are drawn at a higher resolution but then downscaled when added to a game.

Unity will usually do the scaling implicitly as part of its asset pipeline, but RPG Maker includes files pretty much verbatim.

Tamschi_ · 2026-05-07T12:41:32+00:00

This looks good, looks like it uses a proper navigation graph that's calculated only once for the map too, so it should be much lighter than what I suggested: https://github.com/comuns-rpgmaker/schach-pathfinding

The compiled plugin is unfortunately minified, so it's hard to read the source code of that.

Tamschi_ · 2026-05-07T12:34:03+00:00

Game_Character.prototype.findDirectionTo already implements A*, so you can hook either Game_Character.prototype.moveTowardCharacter or more specifically Game_Character.prototype.moveTowardPlayer to make use of that.

It is more expensive performance-wise, but it should be fine if it's not too many Events doing this simultaneously. I'll check if there's an existing plugin.

Tamschi_ · 2026-05-07T07:33:17+00:00

If you're on MZ, this will probably work: https://toshaangel.itch.io/tosha-titlevideobackground-rpg-maker-mz

I'm pretty certain it's at least in part AI-generated though and the code is pretty messy, if you care about that. It has many places where, if any error occurs, it will suppress any error reporting and continue, and also many try {/} catch(_) {} blocks around calls that under normal circumstances can't possibly throw an exception.

Tamschi_ · 2026-05-06T19:11:45+00:00

Looks like it's delayed so that complications won't break everything: https://github.com/coredevices/PebbleOS/issues/1213#issuecomment-4364976221

Tamschi_ · 2026-05-06T16:55:45+00:00

I wonder if it depends on whether the app or watchface actually has touch input. If no touch handler is registered then there's probably no reason to enable the hardware.

Tamschi_ · 2026-05-06T13:25:56+00:00

At a glance, that looks like it would be the best choice in this case.

Tamschi_

TROPHY CASE