Dilan Rona

Same here, I actually do appreciate the game, and everything the developers have done for us.

Also having a bit of stuttering on my laptop. But in my case, its probably the large animal farm, and a rather large waterwheel setup with 3xspeed gear setup (that only runs when I actually need it). Away from my home, it is relatively smooth.

Same here. A huge thank you from me to the devs, and moderators of the game. They did an amazing job.

It should have been posted to the forum as well. I agree.

I for one do not blame the devs of VS for what had happened. Could it have been handled better? Yes. What everyone is forgetting is this is not an AAA company and cannot be held to the same standard. I'm literally seeing worse stuff coming from Sony, and Nintendo and all the other AAA companies that is a lot worse. I am holding Maltiez responsible for what happened however. He did damage to his reputation, that of his mods, and by association that of VS devs (known, or not doesn't matter). It should never have been attached to foundation mods, that's on him. But as far as I'm concerned, it's been dealt with. And I'm willing to let the matter rest now. I'll keep playing Vintage Story, will keep recommending it, and will get the supporter add-on as soon as I can. Something like this was bound to happen sooner or later, so consider this a learning moment.

good point

I agree. Before this topic gets locked like the rest.

Emphasis would then be on advice. Not that he is a part of the vs team itself. But because of what happened, any existing code he contributed will be checked again, and all future contributions will be picked with a fine tooth comb.

That horse has bolted allready, mod was forked as of today.

It has blown out of proportion. Lets hope things settle down now.

Or like their mass ban hammer purge of a lot of users for the "crime" of wrong think. Lots of people never got their accounts back after it was stolen and deleted by Discord T&S. Announcements need to be on the forum, where they belong. And I agree, this whole situation could have been handled better, instead of just banning people off the vs discord, and sweeping the matter under the rug.

I'm going to continue playing Vintage Story. I still trust the devs, and will wait for proper feedback. As far as Maltiez and his mods, I removed them from my modlist, and will not be installing them again. Mods that rely on config lib and imgui unfortunately had to be removed as well, due to their dependency on config lib and imgui.

What I said was to let the topic rest, and let the devs get their side in. If they fail to address the matter, then that itself is a response (a lack of a response in itself is a response). So from my side, i'm going to adopt a wait and see stance. And let the story unfold itself.

For the time being, and until we get an official response, how about we let this topic rest. Yes the damage was done, but now we need to wait for the devs to get their side in.

@Mrozak is correct in this instance. We cannot ask that maltiez be fired. But what he did with some of his mods (the fact that he removed the code doesnt change what happened) cannot be ignored either. And cannot be allowed to happen again, especially since he is on the dev team, and is held on a higher standard.

So the sooner the devs get on this, to soothe the matter over, the better. And it cannot be on discord only, it has to be on the forum as well. And if the team maintains a reddit as well, it needs to be there as well.

Does not in the least bit restore the trust that was destroyed in the first place. People lost trust in his mods as a result, and because he is on the dev team, the fallout is reflecting on the rest of the devs (known or not known doesnt matter either way), and as a result affects the trust in the core game itself. This is something that should never have happened in the first place with that mod, and should have been done in a seperate mod, as any sensible person with a modest amount of coding skill should have known. Not shoehorn code that doesnt belong in a trusted mod to do a task said mod was never designed for originally, straying outside of its core function.

Still not fully in the loop myself. I stand to be corrected here, but from what I understand (it was said other places), maltiez wanted anti cheat measures in the client, and it was denied. So he added it in his mods (3 of them), which I add here had no business having that level of code. Its not the mods job, and should have been placed in a seperate, DEDICATED anti cheat mod. Then there would have been 0 flak, 0 fallout. Just a casual search yielded 3 mods for anti cheat. The whole issue stems from maltiez shoe horning anti cheat code into mods that is not meant as anti cheat mods, and was trusted mods to begin with. Mainly meant for making managing config files easier for example. That is the purpose of the mod in question. Anything else is stepping out of its lane.

Thank you for the update. That should have been posted to the forum as well though, from the start. Not everyone is on discord, and people have their reasons.

I still trust the dev team and will continue to play VS. As far as anything mod related made by maltiez, his mods will never be used by me again, and in the unlikely event it does happen again, it will be a very long time. So unlikely.

Imo, asking for a refund is a bit of an overkill, but it is probably the only way to get the attention of the devs when the mods on the vs discord is actively banning people from discussing the problem in the first place. And what happened? It blew up on the forum. Getting the attention from those that are not on the discord as well.

Outright banning people from the vs discord is not the solution. It only draws more attention to the problem itself (Streisand effect). As @Stoney Hawk, and @Vratislav stated. some information can only be obtained on the discord (which is a major problem in itself). It hasnt been solved. Not by a long shot. Yes, the code that caused the drama was removed, doesnt change the fact that he did it, and that he is on the dev team. And you are right there, a proper response will take time. But the sooner the devs get a response out, the better cause the fallout will not stop, but accelerate.

I for one will always play vintage story. But I will from now on be a lot more carefull with installing new mods from the mod db. As for maltiez? Any mod made by him will be nuked from my installs, and will not be installed on my server. Any mods using config lib will be affected as well unfortunately, as I will be looking for alternatives to those mods.

For example, here is an example of an anti cheat mod, done the Right way (Yols Ore Obfuscator (Anti-Xray) - Vintage Story Mod DB). Here is another one (ModIntegrity — allowlist client-only mods - Vintage Story Mod DB).

You got a point there, @MKMoose. I myself are not against obfuscated code (Especially with valid use cases). I am however against the method used by Maltiez. obfuscated the cause of the crash, and using a known and TRUSTED mod to do the dirty work, instead of doing it the proper way by means of a dedicated anti cheat plugin. If server owners dont want players to cheat, then install an anti cheat plugin. End of story. Authors that feel the need to add an anti cheat to a plugin that has absolutely NOTHING to do with detecting obfuscated code, or cheat mods in the first place is clearly crossing the line. And if not for this forum topic, I would have been oblivious to the drama and arguments. Maltiez may have had good intentions with that version, and to highlight a very real concern (cheat mods). He should have done it the right way with an anti cheat mod. Not shoe horn it into a mod intended to make config files easier.