CanOBeanz

R&D makes sense too, I didn't initially put them in, but they can be added no problem as it makes sense for them to do it as well. But yeah, should only be these listed classes, which I assume would already keep the hacking events limited, considering the circumstances needed for any of these jobs to come across a robotic player that can be safely hacked would be somewhat rare/risky to come by. I'll probably +Support to make this more clear in SOP / raid rules for utility & CI, respectively

Uhhhh Robots should only be getting hacked by E4, Sleuths, and Maynard. This was in the hacking rules as they were first written. I believe these rules are the same for HLPR & CNTN bots. (Im not sure if RIGs are allowed to be hacked, I don't remember any rules being created for them) Are other CI jobs doing these hacks too?

+Support Looks neat Has a face

have a good trip dude!

-support nope

I actually love this idea, Bruce Almighty FTW I can't wait to hear all the bad Morgan Freeman impressions lol +Support, maybe keep the original model too as a secondary option for the job?

-Support It's kinda shocking how many times you said the things you said, I don't honestly believe a couple months is enough to get rid of a habit like that. Give yourself more time to improve

+Support Makes sense for it to have it

+Support No more awkward doing the whole /cmd [Unit] <msg> thing

+Support A valid area of roleplay to explore, i think Medics & surgeons need stuff they can work on when there's no visitors in medbay

+Support I got this exact addon added on SCP-RP and it works very well! Highly recommended for any support branches/classes.

+Support No more jobs for every single rank in Security Makes whitelists simpler to maintain & manage Makes future job updates easier

-Support CI is already doing their best to try to uphold this rule. I empathize with the struggle of needing to kill noncombatants to keep the raid secret or keep positions from getting called, it's kind of just a necessary evil in order for things to still run smoothly. In order for a rule like this to work, it requires compromise on both CI & Utility's side-- For CI, that means getting a raid called out now and then by a pesky onlooker noncombatant. For Utility, that means getting shot in the face now and then by CI agents trying to stop the raid from being called out. If this rule is gonna work we have to accept all of the circumstantial misfortunes that come with it. Also remember, only certain people should be shooting noncombatants after the raid has been announced. TBH, a better use of energy may be just learning how to laugh off getting shot during a CI raid. Or start putting your hands up / moving to a corner / avoiding typing so it's totally clear that you're avoiding interfering in the raid once it's been announced. If a raid hasn't been announced yet, you might just get shot in the butt to keep you quiet. It happens to everyone.

+Support Shades be cool bois

It's platinum rank for some reason which might be why almost nobody plays it

Farewell, Mobile Mop Force Commander Snapple, and Medical Doctor Pepper. It was an honor running the Utility gang with you !! You will be sorely missed, you helped keep order in this chaotic place Chicken pot pie is good indeed Seeya on Sniper Elite again sometime buddy!

Hello! The HLPR Bot Alpha job seems to have been added with a broken model path. Here's the correct model path: models/sligwolf/robot/thirdteen.mdl It seems like the model was added as "thirdtee" instead of "thirdteen". Here's a good comparison of how they look in the player model menu: Player model on HLPR Bot Alpha: Player Model on HLPR Bot CC:

Awesome Thanks for including me!

-Support I haven't seen a problem with ACMs' place on the server, or the things they do, be it from a fairness or a strategy perspective. Therefore I can't honestly support changing their rules of engagement. With the loss of E11 Combat Medics, ACM have grown to fill an important role and they help out a lot to MTF, Medbay, and Gensec personnel, and also give a huge reward for medbay players to look forward to one day unlocking. The main argument I keep hearing against ACMs right now is "They're a utility job", rather than a way they are affecting balance of combat branch interactions. If they're truly unfair in some way in the current way they exist, we can think of other ways to make them more fair-- Be it through armory restrictions, stat changes, d block restrictions, etc. I don't think it's fair to completely rollback this job to self-defense only ROE though.

I blacklisted Peggu, the branch side is dealt with and the punishment seems fair. As for a server warn, i'm +/- support on it. It probably won't make a difference in the situation, honestly.

-Support ACM have same rules of engagement as MTF. They can attack any D class that are out of the holding area. They should be prioritizing healing, but there's nothing against their rules for shooting rioting D Class. ACMs can be countered at long range pretty easily. Just chip away at them with a Falcon or rush with 1-2 other d class.

+SUPPORT GOOD, YES Basically the exact fix this thing needs

+Support these guns are basically just RP guns in their current state

Don't forget HLPR bot, he good boi