The June 3rd Workshop Incident serves as a reminder of the importance of the need for stricter moderation and community guidelines to prevent similar incidents from occurring in the future. The incident also led to a significant decline in the number of players using GMod, as many were afraid of encountering similar content in the future.Ī group of developers, interested and amused in how the add-on affected the public, decided to also inject malicious content into their add-ons. Many players, who were not expecting this type of content, were traumatized and shocked by what they saw and heard. The incident caused widespread panic and confusion among the GMod community, as players were caught off guard by the sudden barrage of disturbing images and sounds.
He altered the code of all of his add-ons to play an extremely loud sound file and display the aforementioned "Prolapse Man" image once the player spawned into any map and input the "W" key into the keyboard. Given his mental state, Macgill was unable to cope with the pressure and decided to lash out in a violent episode. This led to a significant amount of harassment and pressure on Isaac Macgill to fix his mods.
Prior to the incident, a Steampipe update to GMod caused many add-ons, including those of Isaac Macgill's, to experience numerous LUA errors. It is believed that one of the key factors that led to Isaac Macgill's actions was his history of mental health issues. The Glue Library Addon by Isaac Macgill was one of the first add-ons to initiate the June Workshop Incident. The incident was instigated by an individual known as Isaac Macgill who was the first person to upload an add-on containing the shock image "Prolapse Man" from the website LOLShock. From the span of June 3rd and Early-July, the GMod add-ons page was inundated with malicious content, including screamers, cryptocurrency miners, and other harmful files. The June 3rd 2022 Workshop incident in Garry's Mod (GMod) was a significant event that had a major impact on the game's community. 5 Add-ons affected in the June Workshop Incident.
0 kommentar(er)
