Jump to content

Vesk Aida

Vintarian
  • Posts

    9
  • Joined

  • Last visited

Everything posted by Vesk Aida

  1. Shockingly awful opinion. It is pretty disrespectful to call others "angry kids" and "absoutely nuts" when you clearly are either trolling or have no clue what has transpired. Crash Code is not inherently malware, but the implementation of it in this Maltiez situation is flagrantly malicious even by his own admission. Do some basic research in the future before spouting wild accusations about others. Rude.
  2. I hope it doesn't have an impact on Vintage Story's development, sales or reputation (e.x. "that game which had malware in it"). Overall I feel this crash code situation would not have been serious or even worth mention had Maltiez been honest and transparent about documenting the code and its function, or even making it as a feature for a stand-alone mod (e.g. "Maltiez's Anti-Cheat"). The deliberate lack of documentation to hide this 'feature', and by his own admission with the purpose of the code 'being' crash code is pretty inexcusable. My fear from all this drama and nonsense is that many/all of Maltiez's excellent mods (e.g. Maltiez's "Firearms" mod) might never get updated as VS continues to receive patches and support, and will inevitably fall by the wayside. Hopefully Maltiez either is allowed back into the community with more scrutiny/code checking, or a more transparent maintainer is able to keep the mods functioning.
  3. Its been mentioned a number of time, though from what I've seen even Maltiez has never attempted to implement any such feature. Though, given the inherent lack of transparency about code being present, maybe 'that' should be taken with a grain of salt: but I've yet to see any evidence it was ever acted upon: merely mentioned as a possibility.
  4. I have been a fan of Maltiez's Vintage Story mods for many years: he is an excellent modder with a high standard for quality content along with him being a Vintage Story team-member makes this betrayal shocking. This is case is far more severe than that of a similar case of malicious code inserted into mods for the game "Star Sector", the "Lost Forest" mod feuding with the "RJW" in Rimworld, or others. It is completely inexcusable to include malware (deliberate crash code) in software you are transmitting to other users who are not both aware of and consenting. The fact that Maltiez freely admits to this in Discord and commit notes is shocking. This is not 'white hat' code, e.g. crashing the Vintage Story program if it detects an infinite loop, memory leak, or similar serious problem with functionality. Protecting the user from harm. This is not 'grey hat' code, e.g. 'defensively' crashing a program to stop hackers from accessing a server. Causing harm for justifiable reasons, e.g. 'ends justify the means', or in legally/morally vague ways. This is clearly 'black hat' code, since it is undocumented, obfuscated, and can operate on legitimate paying Vintage Story customer's devices simply because of their modding choices, let alone any bugs which may have caused the malware to fire inappropriately. Causing harm deliberately and consciously, for harm's sake. Yes, this malware merely causes 'a hard crash', so it is not particularly severe outside of disrupting the Vintage Story application, but either is it excusable.. To deliberately add this code to multiple versions of a mod shows a clear pattern of intent that this was intended behavior. To hide the existence of this crashcode (not documenting it) shows clear understanding that this behavior is unethical and 'needs' to be hidden. Obfuscating the code shows further proof this author knew their behavior was unethical. Edit: Does not appear any of the mod's code was obfuscated. The fact Maltiez defended his actions shows a clear lack of repentance and level his commitment to this behavior. That Maltiez described his intent to add further code which would have harvested and/or transmitted client-side data, despite his inability to implement such a feature, shows a clear violation of user's privacy and trust, as well as potentially violating laws. Edit: This was merely discussed, with no proof it was ever developed or implemented. Though given the lack of transparency about this crash code, perhaps that should be taken with healthy skepticism. Furthermore It is particularly frustrating to see so much sustained and juvenile behavior from the official Vintage Story server's Discord Moderators. Harassing and insulting users who are acting reasonably and are understandably upset about this situation is inexcusable; including telling users to stop discussing this malware situation in a thread dedicated 'to' that mod, accusing them of being "off-topic", etc. Frankly, these moderators should resign, be fired, or be re-trained to a much higher standard. Very unprofessional and completely tone-deaf to the situation and seriousness, for the sake of 'internet moderator' "I'm an important person on the internet" bawking. It is also painful seeing users in the Vintage Story official Discord server defending Maltiez's actions, especially antagonizing, trolling, and harassing other users. I understand some of these users may not have the technical understanding or context of what happened here, or are acting merely out of emotion for a beloved mod author, but this behavior is completely out of touch and shows serious ignorance to what has transpired and should be condemned. It upsets me that most of these conversations are still present in the Discord server, and there seems to be no moderation action taken against them. In Conclusion The Vintage Story community deserves a clear and direct response from Tyron once the team has decided upon a course of action. I feel strongly that: All of Maltiez's mods should be removed from the official Vintage Story website, if only temporarily pending manual code review. But until then the risk and severity of this case is too high for an author who so deliberately hide crash code from his own userbase over such a long period of time. All of Maltiez's contributions to vanilla Vintage Story should require a manual code review. Anything less would seriously undermine the community's trust in that product.
  5. Experiencing a hard crash to desktop with A Cullinary Artillery 1.2.5 and Expanded Foods 1.7.4 on Vintage Story version v1.20.7 (Stable) when attempting to move 60 "Dried Lingonberry" into an empty Barrel from a nearby Storage Vessel (normal player-made coloration). This hard crash occurs however the items are attempted to be moved into the Barrel's item slot (either by LMB on the stack of Dried Lingonberry, moving the mouse, and placing the stack in the Barrel's 1x1 inventory slot; or by opening both the Storage Vessel and Barrel's inventories and pressing Shift+LMB on the stack of Dried Lingonberry in the Storage Vessel's invantory). This crash can be avoided by having a liquid inside the Barrel (e.x. 10L of Water), and only occurs if the Barrel is completely empty when attempting to move the berries into it. Haven't tested it with other types of Dried Berries.
  6. Maybe I'm misunderstanding how this "Scrap Detector" skill works or I'm encountering a bug with it, since I'm unable to get it to proc when digging multiple stacks worth of sand. It's supposed to be a 4% chance when your character breaks a Sand block, like digging it with a shovel? My character has Collecting > Digging > Scrap Detector 2/2 and Scrap Specialist 1/2 on Xskills 0.8.5 on VS v1.19.8, and haven't received any procs after hundreds of attempts, listed below: 3 stacks of Andesite Sand with a Tin Bronze Shovel 3 stacks Andesite Sand with a Flint Shovel 1 stack of Andesite Sand with "Bare Hands" (holding no item)
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.