Diff

It's not flipping the question, it's addressing the elephant in the room. We can't just say "ignore the elephant for the moment" if you actually want to understand why people are acting weird. That is why it needs to be disclosed, that is why they are "worse." Of course, if a human and an AI write the same line of code, there is little difference (mostly, see below). If you develop a car that has a 1% chance of being assembled improperly and self-destructing after 3 months, you have a bad car. Cars with higher failure rates get the reputation even if a specific instance is fully working. If you could screen for an improperly manufactured car, maybe we can work with that. But we can't. Mods are often closed source and screening code for correctness is intensive. So instead, it's better and wiser to avoid the models of car with that flaw in their production line. We don't have an oracle that can identify "working" vs "non-working," so it's unreasonable to ignore it. The other half of it is more philosophical and social. I have two main issues with code generation AI models. 1. Code generation models are trained on vast swaths of open source (and even closed source) code that was released under certain licenses. These models can reproduce those swaths of code readily. That's not surprising, so can every other flavor of model. But by doing it here, big corporations are being given the ability to launder open source code into closed source code against the wishes of those who made it. A swarm of agents can rewrite software in a new language and a new license, allowing people to take advantage of the hard work of others without abiding by the license that they accepted that code under. I don't think this benefits anyone to gift corporations with the ability to embrace, extend, extinguish in bold new ways. 2. Use of AI is seductively self-destructive. It can be used well. It can be used as an effective learning tool. It can be a nice rubber duck to debug against. But using it without exercising your own skill or by letting it shortcut your own struggle is already showing signs of diminishing the skills backing it. If you're using it to make mods as a fresh newbie, if not used properly as a learning tool, it can sabotage your own education. I'm not saying this in a "back in my day we had to walk to school uphill both ways" kind of way. Even for using AI, a clear view and a clear mental model of the program is important, and AI itself can interfere with both of those.

Yes. As someone who has published one (1) AI-developed mod. I like to explore AI tools to keep an eye on them, but I usually come away with nearly the same understanding every time. The problem with AI mods is what you pave over in this line: The problem is that it's far more likely that an AI-authored mod doesn't work the way it should. AIs frequently hallucinate and non-determinstically just wet the bed. The one AI-developed mod I've published was a lottery win. For chunks of my daily programming work, I have to explicitly disable even AI auto-complete in my IDEs because they don't understand my style, my language, my situation, or my environment and constantly make basic mistakes. The pull of the training data is too strong in large swaths of niches out of the mainstream. Even safely inside the mainstream, we're still getting headlines with AI agents wiping production databases. Mods are low-stakes, but it still sucks to deal with poorly written software that was churned out carelessly and never reviewed by a human. There is, theoretically, a "right" way to do AI-assisted development. By gluing it to strict guardrails, giving careful, explicit instruction, and reviewing all output rather than smashing in a prompt and vibecoding it. But without any sort of disclaimer, it's impossible to know. So it's uncool to waste people's time and potentially screw them over through your own carelessness by not at least disclosing it. And without an explicit disclosure, AI thumbnails become the next best thing to hint at this possible undisclosed carelessness and the threat of wasted time. Besides all that, there's plenty to gripe about the social ramifications of AI (even just specifically in regards to programming) that aren't just "AI bad" but I'm going to cap myself at 2 paragraphs.

You got it. As long as you create a copy of the shortcut to point at your copy of the data folder, there's blessedly little footgun potential here.

I will never not say no to more Vintage Story content. Would love any videos on your first impressions on building/anything in VS. Basically the short you linked but long.

One workaround you could pull is two separate data folders, one with modpack, one without modpack. I don't know how technical you are, but Vintage Story supports having those passed in with a command line argument. The process would basically be like this, but without actually installing a second version of the game.

Alright so there were a few things that I've got customized about my setup in my earlier recording that seem to have confused things, because the reason the de-quarantining isn't working is that none of those commands are correct. Here's a new recording with all of my nonsense stripped out, so the whole process should look exactly like this: CleanerDragNDrop.mp4

New version 0.6.5 just dropped. Mostly for one new feature to enhance usability. Right now a lot of sounds, especially ambient and weather sounds, just live forever in the list. I didn't want to fully hide those, so I added a similar list of throttled tags that will get hidden after a configurable amount of time. By default, it only applies to ambient and weather sounds. Going to continue refining this feature, but this has been useful enough for me at reducing clutter that I wanted to go ahead and publish. Two other small changes, fox growls aren't marked as dangerous anymore, and some small changes/tag additions have been made to the caption metadata files.

Go about downgrading? Go the client download area and click "(Show all available downloads and mirrors of Vintage Story)" to show older versions. Go about backing up worlds? They're stored in your VintagestoryData folder, copy them somewhere safe, and copy them back if you need to revert. Loading a world in a newer version of the game will update it and can make it incompatible with older versions, so backing up is an important step if you might want to go backwards. Code mods are all incompatible between 1.21 and 1.22 so you'll get crashes unless you make sure you purge any that don't belong with whatever version you're currently running. It can be a bit of a mess of things to manage, so multiple parallel installations like dakko said is probably a smoother way to test.

@Zarenth Make sure to back up your world in case upgrading breaks it. But yeah you can downgrade.

Through mods, all things are possible.

What does echo $DOTNET_ROOT say? Based on that, it seems that .NET 10 was never properly installed. Maybe try the official instructions from Microsoft for Ubuntu 24.04: https://learn.microsoft.com/en-us/dotnet/core/install/linux-ubuntu-install?tabs=dotnet10&pivots=os-linux-ubuntu-2404 And maybe just try running the install.sh script. Based on your command prompt, a few things seem not quite right, and I'm not personally aware of any issues with it...

If it's whimsical, I'm in. I could use an ounce of whimsy.

Doing what you did, that one directory was only footgun I ever ran into. If you do want a reset, just delete VintagestoryData and the game will recreate it next time it boots, but at the cost of all your worlds and data. If you got the path fixed and your mods are working, you should be Most Probably Good To Go right now.

What he said. On Windows that works, but on Linux for security reasons the terminal doesn't look for commands in the current directory. You have to use ./ before it to explicitly say that's what you want.

Did you copy the clientsettings.json file? It contains the directory mods load from, so if you don't update that for Linux it'll be looking for a Windows path. Shot myself in the foot with that one a while back. Like you saw, the button still opens the Linux path ignoring what's in clientsettings.json which makes it even more confusing.

If you don't hear anything soon, you've got *much* better odds of getting help if you can upload anything publicly so people can offer drive-by advice.

Try this way instead. Slightly modified command and drag and drop will squish out a few sources of errors. If it says sudo is still running when you try to close the terminal, it's very likely it's still waiting for your password. DragAndOrDrop.mp4

When you say it doesn't work, what are you seeing? It runs successfully but nothing changes, does it spew out any errors saying what went wrong? How are you running install.sh?

https://wiki.vintagestory.at/Installing_the_game_on_MacOS#Known_current_issues First Known Issue on the list has you covered.

AccessibilityTweaks has some controls for this, I believe. https://mods.vintagestory.at/accessibilitytweaks

V odd. If it's a silent freeze and crash without a word, where did/does the error from the first post appear?

Since it's a crash in a specific mod, you might try bringing it up with them. They have active Discord threads for each of their mods in the official Discord server, unfortunately they don't seem to be active here on the forums. There are also a few newer versions than 1.18.3 available for 1.21.4, maybe one of those has already fixed the crash you're running into.

Don't have much time at the immediate moment, but I was poking around and found these. Looks like a decent tree to bark up for starters. https://apidocs.vintagestory.at/api/Vintagestory.API.Common.IInventory.html?q=GetBestSuitedSlot#Vintagestory_API_Common_IInventory_GetBestSuitedSlot_Vintagestory_API_Common_ItemSlot_System_Collections_Generic_List_Vintagestory_API_Common_ItemSlot__ https://apidocs.vintagestory.at/api/Vintagestory.API.Common.IPlayerInventoryManager.html?q=TryTransferAway#Vintagestory_API_Common_IPlayerInventoryManager_TryTransferAway_Vintagestory_API_Common_ItemSlot_Vintagestory_API_Common_ItemStackMoveOperation__System_Boolean_System_Boolean_

Oh, it's not your server? I guess I'd try deleting the downloaded server mods from the VintagestoryData folder, letting it redownload, and seeing if that changes anything. The error log you posted points the blame at OverhaulLib for trying to load assets before the game is ready. What version of OverhaulLib is it?

Looks like a mod did something it wasn't supposed to. Does this crash still happen if you disable all mods? How about if you disable ComatOverhaul/OverhaulLib specifically?