Jump to content

Make 610 unable to infect the original 610 [Completed]


Dodo278

Recommended Posts

 

What are you suggesting? -  I'm suggesting to change the 610 swep so it cannot infect the JOB "SCP 610." It is way too easy for 610 instances to accidentally infect the main 610. To the point that it happens almost every time 610 breaches. An instance of 610 always spams its swep or misses a human, infecting the original 610 and dooming it to die unfairly and in an unintended way to its own infection. This especially happens often because a human is holding left click to shoot 610 and then when they get turned they will still be holding left click causing them to hit the main 610 with their swep.

How would this change better the server? - This change would make 610 actually viable instead of always just dying to its own instances.

Are there any disadvantages of making this change to the server? If so, explain. - Could possibly be hard to code the swep to not affect 610 but once it is implemented no.

Who would this change mostly benefit? - SCP 610

Please link any workshop content, screenshots, or anything that you think may be helpful to those who view this suggestion - N/A

Edited by Dodo278
Link to comment
Share on other sites

  • 1 month later...
Guest
This topic is now closed to further replies.
×
×
  • Create New...