Content Suggestion 966 change

[CourageousNico]

What does this suggestion change/add/remove:
966 can not go through doors. Adds the ability for him to break standard doors but not bulks.

Has something similar been suggested before? If so, why is your suggestion different?:
Not from what I believe.

Possible Positives of the suggestion (At least 2):
Stops the 2+ hour long chains of breaches being caused by 966 just being able to run to surface and hide.
Easier to contain 966.

Possible Negatives of the suggestion:
SCP mains will be mad.
966 contained easier.

Based on the Positives & Negatives, why should this suggestion be accepted:
Despite 966 being able to contained easier because of this, it makes sense since 966 isn't able to go through doors in lore. This also adds more strategy and interesting game-play, making it harder to play as 966 but in a fun way.

 

[Sule Goodman]

+\- support

Personally I think him going through regular doors are fine. But I would argue BULK doors (or other heavily fortified doors) he shouldn’t be able to get through.

 

[fyzar]

Despite 966 being able to contained easier because of this, it makes sense since 966 isn't able to go through doors in lore. This also adds more strategy and interesting game-play, making it harder to play as 966 but in a fun way.

966 just wont ever be used, hes a terrible scp as of current and this wont help that. whilst it might not make sense in lore, it doesnt have to

 

[Emilia Foddg]

Stops the 2+ hour long chains of breaches being caused by 966 just being able to run to surface and hide.

...What? If 966 got to surface, then turrets were down.

 

[Cloudblade]

-Support

It would make 966 useless, he would get contained instantly.

 

[Sneefo]

966 is my fav scp to play but he really is the worst scp in the game and its not even close

-support

 

[conspiracycarl]

-support

was this made after the crazy 966 breach eariler lmao

 

[CourageousNico]

-Support

It would make 966 useless, he would get contained instantly.

Not sure how, could you explain?

 

[CourageousNico]

...What? If 966 got to surface, then turrets were down.

Basically 966 would be breached, run to surface and be there doing God knows, then get captured by CI or press F2, and before E-11 can even sweep or call off the code, another breach happens.

 

[Cloudblade]

Not sure how, could you explain?

He would get stuck behind a door and then get blasted by E-11.

 

[CourageousNico]

He would get stuck behind a door and then get blasted by E-11.

Well since he's invisible he has a high chance of escaping or being able to break the door, having a high chance of dodging shots while being invisible, allowing him to escape easily.

 

[CourageousNico]

He would get stuck behind a door and then get blasted by E-11.

966 breaking doors would not break his cloak.

 

[Emilia Foddg]

Basically 966 would be breached, run to surface and be there doing God knows, then get captured by CI or press F2, and before E-11 can even sweep or call off the code, another breach happens.

...And the turrets in lobby would kill 966 before it gets to garage.

 

[CourageousNico]

...And the turrets in lobby would kill 966 before it gets to garage.

Turrets don't shoot 966.

 

[Emilia Foddg]

Turrets don't shoot 966.

...They should?

 

[Sneefo]

Turrets don't shoot 966.

they 100% do, going for surface as 966 is almost guaranteed death

 

[Froggo]

-Support

966 going through doors is a balance thing. This post was made after the 966 breach earlier as i was there. he got RC'ed twice even after being at 95% health to start. The only reason it lasted 2 hours is because of 1. MTF just let him go for some reason and 2. i tried to give him back but no one wanted him back so i had to let him go due to kidnap rules. if you know 966 is out, he is fairly easy to contain.

This also doesn't suggest a compensation buff since it would literally just a be a invisible SCP with 6.5k health