What does this suggestion change/add/remove:
Some form of limits to CI operations within the site during low-pop hours. I recently endured a 5-hour on-and-off raid of disguised D-class and CI nearly taking over the entire site, killing people who are making chems in a secluded area, kidnapping the same people 3+ times in a row within a 2-3 hour window, and holding people for over an hour.
I suggest either a rule limiting operations to once every [SUM OF REASONABLE TIME when BELOW CERTAIN PLAYER COUNT] or making hostile frontal assault raids on site not allowed under a certain PLAYER COUNT instead of the ridiculous rule I heard when discussing this issue of "4+ mtf units = raidable" (esspecially since apparently, they can flag on mtf units, take a picture of that, and then flag back onto ci and use that picture as proof there are enough mtf to raid?), as this rule does not take into account the amount of CI that can raid. The current setup allows a disproportionate amount of CI to enter the site, like what we had today with 10+ CI sitting in medbay, completely oppressing site personnel, while there were maybe 10 combatives in total, some of whom we were spending their time decorating checkpoint charlie.
Has something similar been suggested before? If so, why is your suggestion different?:
Not that I could find within recent threads. Please let me know if I am incorrect.
Possible Positives of the suggestion (At least 2):
Server health in the low-pop and even medium-pop environment
Possible Negatives of the suggestion:
Complaints from CI members who regularly play low-pop hours.
Based on the Positives & Negatives, why should this suggestion be accepted:
Yes. I just watched an extremely dedicated consultant rage quit from the server after being kidnapped 2-3 times within the same raid and dying when someone attempted to kidnap him again while holding a fresh batch of expensive and rare chemicals. Not because he was armed or defending himself, but because a d class who had teamed with the CI felt a little trigger happy and decided to shoot the consultant for fun.
Allowing this to happen regularly is not good for server health.
Some form of limits to CI operations within the site during low-pop hours. I recently endured a 5-hour on-and-off raid of disguised D-class and CI nearly taking over the entire site, killing people who are making chems in a secluded area, kidnapping the same people 3+ times in a row within a 2-3 hour window, and holding people for over an hour.
I suggest either a rule limiting operations to once every [SUM OF REASONABLE TIME when BELOW CERTAIN PLAYER COUNT] or making hostile frontal assault raids on site not allowed under a certain PLAYER COUNT instead of the ridiculous rule I heard when discussing this issue of "4+ mtf units = raidable" (esspecially since apparently, they can flag on mtf units, take a picture of that, and then flag back onto ci and use that picture as proof there are enough mtf to raid?), as this rule does not take into account the amount of CI that can raid. The current setup allows a disproportionate amount of CI to enter the site, like what we had today with 10+ CI sitting in medbay, completely oppressing site personnel, while there were maybe 10 combatives in total, some of whom we were spending their time decorating checkpoint charlie.
Has something similar been suggested before? If so, why is your suggestion different?:
Not that I could find within recent threads. Please let me know if I am incorrect.
Possible Positives of the suggestion (At least 2):
Server health in the low-pop and even medium-pop environment
Possible Negatives of the suggestion:
Complaints from CI members who regularly play low-pop hours.
Based on the Positives & Negatives, why should this suggestion be accepted:
Yes. I just watched an extremely dedicated consultant rage quit from the server after being kidnapped 2-3 times within the same raid and dying when someone attempted to kidnap him again while holding a fresh batch of expensive and rare chemicals. Not because he was armed or defending himself, but because a d class who had teamed with the CI felt a little trigger happy and decided to shoot the consultant for fun.
Allowing this to happen regularly is not good for server health.
Last edited: