Hacker News Reader

Comment by azhenley | Hacker News Reader

"command line"

There's a terminal window in the game which you use to control your robots

I even found some shell constructs to work beyond what the game documented/ explained to me

Doom and Quake had drop-down command consoles too that let the user change the game's state -- I've included such features in some of my GUI, realtime engine games too. but I would never promote any as a "command line" game

Doom, Quake, and assumedly your games don't use their command line as primary input like this.

The primary way to play Duskers is via scripting in a CLI

fair enough

a cli game that only runs on windows ... very funny

I just installed Steam on Ubuntu yesterday, and I'm impressed at the progress so far. A HUGE number of titles run flawlessly.

Author's latest title has enormous memory leaks in linux through proton (and in macos through crossover) [0]. I hope the author puts effort in non-windows platforms for this one during development, because the first duskers was indeed a great game.

[0] https://steamcommunity.com/app/1883920/discussions/0/6897422...

> Author's latest title has enormous memory leaks in linux through proton...

If this is something the dev can reasonably fix by changing their game, then it'd be good for them to do so. Looking at the discussion in the thread, it looks like the dev is actively working to fix this for everyone, and not just the subset of folks that he fixed it for.

However, if this doesn't happen on Windows, I'd argue that it's a bug that needs to be reported against and fixed in Wine/Proton/Crossover.

Maybe. But also imo it happened because the author was not testing proton/crossover at all until the beta was released, and even then only later that did people started reporting it. Developing in one platform and then post-release fixing bugs in others that the game is not actually meant to be played is probably not easy.

The bug is still there, disabling assisted moves helps a lot and it triggers less but it still happens if you are unlucky.

Just to note that the author seems in general very nice and helpful, and one can choose what platforms they want to support, I just wish we could get native builds for more platforms like with duskers 1, which had native macos and linux, or at very least to have wine supported so that there is less of windows monopoly in games.

> Developing in one platform and then post-release fixing bugs in others that the game is not actually meant to be played is probably not easy.

...except that the promise of Proton/Wine/Crossover is that -for user-mode stuff- it works at least as well as Microsoft Windows. Any undesirable behavior that happens in Proton/Wine that doesn't happen in Windows is a bug that should be squashed. IMO, it's generally incorrect to think of it as "a platform", as changes in Microsoft Windows absolutely introduce gamebreaking bugs.

> ...I just wish we could get native builds for more platforms like with duskers 1, which had native macos and linux, or at very least to have wine supported so that there is less of windows monopoly in games.

When I was much younger, I held this same opinion. Now that I'm older, I'm 100% fine with the "Windows Subsystem for Linux" [0] that is Proton/Wine. I see it as yet another cross-platform library for doing development on *nix systems... albeit a very large one.

Given how incompetent and user-hostile MSFT has been proving themselves to be over the past few years, it seems quite possible to me that in ten years, the only place you see Microsoft Windows being used by "consumers" is inside an XBOX [1] or Azure.

[0] Well, it's not just for Linux, but I can never avoid an opportunity to note that Microsoft WSL is misnamed.

[1] ...assuming that the XBOX division is still making hardware...

Reply on news.ycombinator.com