Diff

I've never snowballed myself, but I did watch a youtuber snowball the other day, and they had traders spawning in. Caused a small problem on that run cause one of the few rare pieces of grass was protected by the trader's claim.

Seems fun

Another game with similar mechanics (and more tuned to wilderness survival (which was mentioned briefly but I want to throw more spotlight on it)) is The Long Dark. Certain actions cause or risk injuries, animal attacks, walking on steep ground while overloaded, getting too cold, eating spoiled food, not eating enough fruits. Minor injuries might cause nothing but pain, and threaten to progress to a major injury if aggravated further. And major injuries often just temporarily reduce your max health, speed, carrying capacity, or stamina and unlike Zomboid often don't need any ongoing attention as long as they're treated. At least on the max health front, I think that vibes pretty well with VS's current system of balanced diets boosting max health.

Up at the top of the site, there's a glowing tab labeled "Client Area." The answers you seek lie there.

So recently I was trying to join a server that was locked at an older version of VintageStory for Reasons. On the Steam Deck, installing stuff from the Discover store is relatively easy, but installing something like from the Client Area can quickly become A Pain, especially on a mostly-immutable system like SteamOS. If Only There Were A Better Way! Thankfully we live in the future, but it requires popping open the terminal. We need to find the ID of the old version, then we need to "update" to that specific version. 1. Find the ID of the old version. Run this command in the Konsole or your terminal of choice. It's filed under System in the main menu in Desktop Mode. We have tab completion, so for much of these you can press Tab to autofill things in after typing a few letters. flatpak remote-info --log flathub at.vintagestory.VintageStory This command reaches out to the store and requests a log of versions. It's a bit messy, but this has all the info we need. It'll look something like this: Vintage Story - Wilderness survival sandbox game ID: at.vintagestory.VintageStory Ref: app/at.vintagestory.VintageStory/x86_64/stable Arch: x86_64 Branch: stable Version: 1.20.12 License: LicenseRef-proprietary Collection: org.flathub.Stable Download: 68.2 MB Installed: 121.9 MB Runtime: org.freedesktop.Platform/x86_64/23.08 Sdk: org.freedesktop.Sdk/x86_64/23.08 Commit: 8773e8f47f7a40082f592d2a43e6529c74f5ba4d195f556bc1ef1cf063b234f8 Parent: 41e459b2897b423e671fa69aca87746440f6a4d82a2964703f655eca96718d41 Subject: Merge pull request #100 from flathub/update-master-2902b25 (b82373a574c8) Date: 2025-06-08 18:19:42 +0000 History: Commit: 41e459b2897b423e671fa69aca87746440f6a4d82a2964703f655eca96718d41 Subject: Merge pull request #99 from flathub/update-master-1105e90 (3fc1695f107d) Date: 2025-05-28 11:00:07 +0000 Commit: 787cd31e0c48c0c1d74d818f04cc2f029fed330183e06845271ec0cd3bc2075d Subject: Merge pull request #98 from flathub/build_only_x64 (a551f57ad9f7) Date: 2025-05-05 16:35:23 +0000 Commit: bb5e55b971c5efc4d6283559575b7934fc718ad2d7539a0e9aa85be663fcfead Subject: Merge pull request #97 from flathub/update-6a4bf05 (cf894ec7dabe) Date: 2025-05-05 14:32:38 +0000 Commit: 37cb7ce575de3536f8c1e4b8cf1e50e37ace32a0d06bc280745cd30b698f66b6 Subject: Merge pull request #95 from flathub/update-12e60a9 (fe8cf1b55f9a) Date: 2025-04-22 14:45:34 +0000 Commit: ae78911920852de61d6f5b33312e3246d54ab684506ac9b395e0f0dece5666ef Subject: update description (0aceb070) Date: 2025-04-01 13:22:29 +0000 Commit: 1129910a81ecffb94387bc40bd6e432355ba99009f30cf9b2a351ec4d32695a1 Subject: need to use raw links (ae6a7700) Date: 2025-03-24 13:15:46 +0000 Commit: a6aaf77dc6e3273c8b4e489d2a65819ba34be4ad588715b82e8558755c562c4f Subject: Add 1.20.5 release description (7b7300f5) Date: 2025-03-18 17:19:46 +0000 It starts off with some info about the app, then launches into the change log. Each entry has a Commit ID, a Subject, and a Release Date. Now this unfortunately isn't super consistent, but if you're lucky, the VintageStory version you want will be explicitly mentioned in the Subject. If not, you might want to compare the dates here to the release date of the version you're looking for. But once you find the right entry in the log, copy its Commit ID. In this example, if I wanted 1.20.5, I'd copy "a6aaf77dc6e3273c8b4e489d2a65819ba34be4ad588715b82e8558755c562c4f" for the next step. 2. Install the ID of the old version. Installing is fairly straightforward: sudo flatpak update --commit=INSERT_COMMIT_ID_HERE at.vintagestory.VintageStory Two things to pay attention to, replace INSERT_COMMIT_ID_HERE with the commit ID you copied earlier, and notice the sudo at the start. Flatpak doesn't allow installing specific versions as a normal user, so we need sudo, which will ask you for your sudo password. If you haven't set one up yet, you'll need to. You can do this by running the "passwd" command in Konsole. Don't forget it, because there is no "Forgot My Password" system here. After you enter your password, it'll ask you to confirm the backwards update, and after a few moments it should be installed. Pop it open, verify you've got the right version, and you're all set.

Honestly would love customizable crafting of functional items in general. Like, smith out your own sword or knife blades, as long as it's close enough to the existing pattern. Clayform custom storage vessels as long as it's watertight and has enough interior empty voxels. Or being able to add decorative chiseled elements and accessories to armor or clothes.

Am I looking at macOS running on a Lenovo laptop?

Welp. That's this thread for me, see y'all in the next one.

True, every person affected by the global recession did in fact live in a society, but that's quite the leap to get to "this is your fault, actually." Let's assign blame where it's clearly due rather than shrugging our shoulders at big problems because big solutions are hard to come by. I learned in middle school that the antidote to plagiarism is attribution. It's not enough to say "hey yeah I stole this," you must cite where you draw from. Man those are some funky nonstandard definitions you've got there.

What are you wanting out of a mod manager that we don't have now? One-click installs from the ModDB and being able to enable/disable things in the game itself seems pretty snazzy, but maybe I've been playing/modding too many 2010s games with awful modding support lately to know what's good.

It's something we'll have to deal with sooner rather than later. If we can automate all jobs, what do the people do? Right now we're (according to silicon valley) on the path to automating the creative work and leaving only limited drudgery, tedium, and manual labor for the humans. And eventually, not even that. By having AI gated behind large companies, we divert the pay that would go to the workers instead to the executives and an increasingly small numbers of people working to put themselves out of work, like you say. The goal here isn't enhanced creation or the transformation of jobs through the assistance of AI. It is explicitly the elimination of jobs to reduce workforce costs and squeeze more work out of fewer employees, and ideally no employees except an executive giving orders to agents who give orders to sub-agents, the same as it ever was, except with the AI industry collecting everybody's paychecks for them. This isn't pain in service progress any more than the 2008 recession was. It's profit-chasing whose critical long term faults are being ignored in favor of short term gains. There are negative externalities that won't bear to be ignored for very long. A post-scarcity world demands radical social change, as our current social structure would see us all unemployed and on less-than-subsistence government assistance with no prospects or opportunity for growth. Introducing a post-scarcity world into our society is not something that can tolerate Silicon Valley's sacred dogma of "move fast and break things."

The difference is that this isn't some sort of influencer grind hustle. Concept artists, character designers, texturers, 3D modelers, animators, product designers, graphic designers, package designers, motion designers, their art is their work. They work a 9-5 and that's how they get paid. Every product you use and interact with must be designed. Someone has to make that stock art on that food product. Somebody has to design the cereal mascot and animate them for ads. Somebody has to do the VFX work to composite an animated character into live footage. Somebody has to do the color grading on that footage to make sure it doesn't look like a high school A/V club project. These are all individually, actual, full-time jobs, it's worth not feeding it into the unholy silicon valley torment nexus.

Both. It goes out and searches and grabs everything, distills it down into a statistical model during training, and then coughs up images based on that model which can often include whole existing images at a high degree of fidelity. It can't generate from nothing, but it doesn't actively search the internet, the searching is already done.

Not quite, it doesn't change it enough to be unique. It just throws the whole thing out and tries again. Changing things just a bit in general is not good enough. And the copyrightable image elements embedded inside image generation models are quite lossy and can't easily be matched, I don't believe that's been done before. Well-structured text like code is very simple to detect matches across, and the technology for that is time-tested. Instead, for images current copyright protections are limited to seeing if you put "mickey mouse" in the input prompt. "Cartoon mouse with gloves," however, gets you right through. Ignoring all that, in your hypothetical, it's the same amount of plagiarism, but there is the additional bonus of the color change and distortion making it obvious that plagiarism was intentional and not incidental. There absolutely is a ton of flexibility, and even creativity that is possible in code. Like I said, there's several sane ways to write Hello World, let alone anything more complex. But there's substantially less freedom than you have when you put digital brush to digital canvas. The comparison there was in amount of degrees in freedom, I don't believe there's any bar you could reach that could make a bit of code as expressive as a post-it note doodle. Code just doesn't have the information density to have the fingerprints embedded in it the same way. So in programming, the plagiarism is much more straightforward and use basically the same anti-plagiarism systems that we built up for humans. Text is nice and well behaved, and the existing plagiarism systems are perfectly capable of looking past slightly changed variable names. "Code plagiarism" isn't dependent on lines of code, it's dependent on whether this segment of generated code is too closely related to existing code. So there's two issues here that I think are being conflated. 1. The fundamental ethical issues with AI ripping off things without permission in order to try to put people out of a job and then sell the product of those jobs back to us. And 2. The legal copyright issues that arise because language models do encode a fair share of copyrighted material that is encoded faithfully enough to get you in legal trouble if it's ever output by the model. When we talk about output, we're talking about the legal hot water you'll get in. When we talk about the ethical issues with AI, it's about using people's work to put them out of a job, or at least sell the idea of putting them out of a job to people. Yes, it's also unethical to launder FOSS-licensed code or someone's collection of art through an AI, but it's also illegal enough to get you in some hot water.

Yo, tell that to the 2008 recession. The foolishness is not always limited to just their own selves, these are jobs, people, and entire interwoven economies that we're talking about. And the AI bubble is certainly big enough to threaten more than just its own self and its marks. Asking AI for code, and copying and pasting the errors back into the prompt in a loop until it works. It's only suitable (being extremely generous with that word) for crappy weekend projects that will never see the outside of your own local computer. So if you go up to a software engineer who builds systems that can survive trials like "someone put an apostrophe in the username box" and equate their job to a lazy, self-destructive programming fad that can't survive those trials, they will correct you. Just like if you reduce the work a graphic artist does to just "generating images." That's not being emotional. And it's not limited to creative work.

It is wild that you keep going on about this emotional artist trope, all because someone rejected their craft being referred to as "generating." Again, call up the programmer, ask them if they can teach you how to vibe code like them. The trope you seek will rapidly leave the demographic you're pinning it on.

The problem isn't actually being replaced, the concern at the table is management being taken in by the hype. It's easy to believe the big smart tech men (who totally could have been physicists, it's really important to them that you know they could have done theoretical physics) who extol its virtues to anyone with cash in their pockets. But the risk of AI here isn't even AI. It's management thinking AI can replace jobs that they don't even fully understand. That brings up a whole other issue with AI, the de-skilling of humanity as people offload more and more of their brains to a model that's actually incapable of thinking, but I don't think I'll launch into that particular rant right now. Sorry, this is going to be another wall because I never get to talk about this, but no, actually, that was a huge issue when GitHub Copilot launched (and is still an ongoing one in the background, MUCH lower key though), that they used OSS-licensed code to train models that would generate license-free code, effectively collecting money every month to launder open source code. Caught a lot of flak for it, but as it's more structured and easier to identify, code generation models have features to do exactly that, and identify when a segment of code generated is too similar to an existing segment of code. There's nothing like that for general LLMs or image generation models. The other difference is a social one. Your average programmer is a lot closer to the silicon valley tech bro "fr*ck the consequences, move fast and break things" mentality. Code also has the unique quality that it's finished artifact is more of a liability than an asset, the stories keep rolling in of "My vibe coded SaaS app leaked all my users' information, ate my cat, and revealed my OpenAI key costing me thousands overnight." Another part of the difference is in like - I don't have a good phrase for this - "the degree of scale of influence"? between a function that fills a face and a directly generated face. When you paint, you have a million degrees of freedom. What brush you use, what paint you use, exactly how that paint is loaded onto your brush or knife, the angle, speed, pressure, twist of the brush across your canvas. There's a billion trillion ways to draw a cloud, and whether it's Photoshop or a cave painting, you have that control. Generating a function that draws a face on the other hand, well, we're basically talking about SVG. And AI doesn't make good SVGs. There's less control there, and artistically, basically no influence at all from any existing artist. There is often only one sane way to implement a function, one way to lay out your boilerplate. You don't have those degrees of freedom, and actually AIs are far more effective when they have fewer degrees of freedom, that's why every single Lovable clone all insist on using React+Tailwind. Anyway, that's where another difference creeps in. In programming, code is largely faceless. People have styles, absolutely, but the expressiveness is extremely limited. In that way, the plagiarism is a lot less "substantial" than in art where there are so many more degrees of freedom that people use to create an endless array of unique visual styles. You can draw fruits in a bowl a million ways. You can only write Hello World relatively few (sane) ways.

In all good humor, if you're confident about that, then it's because you do not grasp how it works. Here, take a much simpler example: pixels. Just pixels. This is a highly desired, highly trained on, and highly used example. But image generation models can't do it. It can't even keep the pixels square. It cannot commit to an "internal" grid size to align the pixels to because each part of the image is done practically independently. This conflict with the underlying way that AI image generators work means that despite the demand, despite the simplicity of the requirements, and despite the amount of time that has passed, there are NO models in existence that can generate pixel art assets that would be usable or acceptable in a real project. And that's just due to one of the fundamental issues with these models. There are others. Tiling takes that up to 11, for a laundry list of additional reasons that all boil down to a similar "the way that this must be done is just fundamentally, entirely at odds with how the technology operates at its most primitive levels," but with the difficulty curved ramped up exponentially. There's no waiting around for this to get better because this is baked into the foundations. It's part of the basic premise of how the technology operates that this *can't* work. Abusive's a strong word. It sounds like it's for the best that you got out of the business, then. Regardless, there's been no abuse here and I'd maintain that it's entirely reasonable for someone to insist on the earlier distinction between artists and the latest silicon valley hype fad whose stated purpose is to obsolete them. If you described a systems engineers job as vibe coding, unless they're a doormat, they'd correct you.

I exclusively play VS on my Steam Deck. Or any game, really. Analog movement and trackpad+gyro camera is nearly the best way to control a game imo. For VS specifically, I've got the grips set to Ctrl and Shift, I've got one grip set to toggle Alt on and off, Dpad for frequently-used functions like dropping, handbook, and switching tools, and you can bind the left trackpad and right joystick to menus to fill in the less used buttons.

It doesn't work like that. That's not *really* a thing you can do. You don't program an AI like that, AI's fundamentally not really capable of understanding tiling well, and in general the more requirements you lay down, the more it will just ignore you. Smooth tiling is also difficult to add as a post-processing layer, and even if you accomplish that, all you can do is re-roll and cross your fingers because you cannot make the AI understand what you have just programmed, you can only pass/fail the output and hope that by pure chance one makes it through the barrier while you keep racking up increasing bills. As someone who spans both graphic design and programming in their career, AI really cannot automate anything you care to. It's good at demos. It falls flat immediately on contact with reality. And with something like a texture pack, AI is going to be fighting you every step of the way. With the fundamental issues with the way image generation works being at odds with tiling, and the fundamental issues with the way image generation works being at odds with getting a cohesive visual style, and the fundamental issues... don't believe the hype. Ah yes, snap firings based on trivialities like using correct terminology in a professional setting, definitely a good way to keep your employees from walking on eggshells...

One of my favorite things to do in games is to bind the left trackpad to a scroll wheel with counter/clockwise rotations bound to scroll up/down. Depending on the game, it can also be nice to bind it to a radial menu with items for 0-9 to hop to specific spots on the hotbar.

Anyone else running into issues with the on screen keyboard on Deck? Lately pressing the Steam+X chord, or even creating a brand new binding for it, doesn't work. The keyboard summoning sound plays, and if I bring up one of the overlays, it'll be there, but not when the actual game is focused.