Jump to content

NeoID

Member
  • Posts

    797
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by NeoID

  1. I think it’s fine, our SOPs state our Chain of Command pretty well. I’m more focused on the descriptions of each, rather than branch specifics
  2. +/- Support leaning - - I understand that the current 939 rules are very vague, similar to how 096s used to be. Theres no real way to determine it, and it all comes down to staff discretion in the end. Everyone sees it differently. - I don’t know man. He didn’t really “jump” more just accidentally uncrouched and immediately crouched again. There was also a 5 second gap from him sneaking away. See, if he had jumped, then I might be tempted to agree, but it doesn’t seem thay way. To me, I feel this warn was justified, as I don’t really think he made enough sound by simply crouching and uncrouching and crouching again, looks like he got scared when he opened the door, which we’ve all done lol.
  3. What are you suggesting? - On the back of the CI Debrief room, there is a Training Room. I think it’d be cool if D-Class could “self-inform” themselves on both of CIs Branches in that room, and what better way to do that than place the brief description decals inside that room. On either wall, the Decals ill put at the bottom of this suggestion should be placed on either side for D-Class to view at any point. How would this change better the server? - D-Class can get a full description of each CI branch just by reading without an FTO present, making their decision more accurate, considering every FTO can put it differently. Are there any disadvantages of making this change to the server? If so, explain. - Not that I could imagine Who would this change mostly benefit? - D-Class, CI FTOs Please link any workshop content, screenshots, or anything that you think may be helpful to those who view this suggestion -
  4. So, our previous Branch Update resulted in a couple... Errors. The most recent Bio Model turns out that the person who made it was very experimental, and failed to provide the necessities of a proper playermodel. For this one I TESTED THE HELL out of it. Even contacted the owner to be certain. After I fix this Bio Model, I intend to never touch it again. Finding a Hazmat model thats not already in use has been a right pain in the ass. Which I deeply apologize for, there's only 1 minor fix here, the other was simply a late request made by the Field Research lead Team which was to have a Gravity gun like every other job, and Sleuths base model looks weird in the menu with it just being Nu7, Dang had stated he'd rather it be another model, so we agreed maybe shoot for the Tau-5 Model, when considering the current Nu7 model is used on too many jobs, which is entirely understandable, also some added complaints about the Sleuth job looking weird having an MTF on the cover in the menu, so adding a model to fix that as well.so I thought I'd knock out several birds with one stone. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Name of Job: CI Bio-Engineer Job Model (Model Paths): models/kuma96/gta5_gorkasuit/gta5_gorkasuit_pm.mdl Remove Job Model (Model Paths): models/ninja/hazmat.mdl Job Description: N/A Job Weapons: N/A Job Salary: N/A Job HP: N/A Job Armor: N/A Extra Info (Ex. Workshop link for models): ADD THIS MODEL: https://steamcommunity.com/sharedfiles/filedetails/?id=1376326689&searchtext=Suit REMOVE THIS MODEL: https://steamcommunity.com/sharedfiles/filedetails/?id=123522934&searchtext=Hazmat ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Name of Job: CI Field Researcher Job Model (Model Paths): N/A Job Description: N/A Job Weapons: weapon_physcannon Job Salary: N/A Job HP: N/A Job Armor: N/A Extra Info (Ex. Workshop link for models): N/A ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Name of Job: CI Sleuth Job Model (Model Paths): models/scp_mtf_russian/mtf_rus_09.mdl , models/player/Suits/robber_tuckedtie.mdl Remove Job Model (Model Paths): models/bread/bo2_sealscp_masked.mdl Job Description: N/A Job Weapons: N/A Job Salary: N/A Job HP: N/A Job Armor: N/A Extra Info (Ex. Workshop link for models): ENSURE THE MODEL " models/player/Suits/robber_tuckedtie.mdl " IS THE FIRST MODEL ON THE JOB, TO HAVE IT APPEAR AS THE ICON IN THE F4 MENU
  5. NeoID

    Dark's LOA

    Wrong place, fill this out for your LOA https://docs.google.com/forms/d/10LBLD6OTctI_hHOhoy8jXcqRs7GD7ksUD1nCjsvZP0c/edit
  6. NeoID

    Ap p li ca ti on

    Wha- He got to it before anyone else? This is not ok. I’m contacting my lawyer
  7. Lmao. Yeah, for Analyst, I support this. He does fine understanding RP Testing, and Utilization Rules as well. Combat, well, I got no idea, but theres a first for everything.
  8. +/- Support -App is decent -Active enough -The Idea is meh, it ending with a nuke is a nono, only Mega-Events should ever lead to that, and even those can get obnoxious -I’ve said it before, but you have failed to meet expectations in the past over long periods of time.
  9. +Support Please stop. I’ve trained you for this too many times ;-;
  10. What are you suggesting? - The current wording of the rules are too vague, specifically with starting negotiations before a raid, and too many people get in trouble, or get in arguments with CI because of a misunderstanding of the wording. Which is currently: Mobile Task Forces are permitted to raid the Chaos Insurgency base. For a raid to be authorized, one of the following must be satisfied: Actionable intelligence that CI have captured a SCP and CI refuse negotiate its release, or negotiations have failed. Actionable intelligence that CI have captured Foundation Personnel and refuse to negotiate their release, negotiations have failed, or the captured personnel is Level 4 or above. MTF Stealth Operatives and Pathfinders may be used to infiltrate the CI base to confirm the presence of SCPs or Foundation Personnel. This constitutes the beginning of the raid. If the Stealth Operatives and Pathfinders are killed or voluntarily leave the base the raid is concluded and the raid cooldown timer begins. Upon the presence of SCPs or Foundation Personnel being confirmed the main body of MTF forces may move in at the direction of their raid leader, pursuant to SOP guidelines. MTF Stealth Operatives and Pathfinders are prohibited from terminating a hostage or SCP until the main body of the MTF forces arrive. A raid is concluded once all MTF personnel either are killed or voluntarily leave the CI base. At this point a 10 minute raid cooldown timer begins.A member of MTF must state in MTF Comms: "MTF Raid Beginning" at the start of the raid. If there are less than 6 CI military personnel online this must instead by adverted. A member of MTF must state in MTF Comms: "MTF Raid Concluded" at the end of the raid. However, with how SCPs/Hostages currently behave when being captured/escaped the foundation, it should be reworded to accommodate the complications that have arose under these rules. I understand that a suggestion is currently up to prevent SCPs from being able to enter CI base, but this will still minimalize issues even further, rules should state the following: Mobile Task Forces are permitted to raid the Chaos Insurgency base. For a raid to be authorized, the following must apply: -Raid must be authorized, and lead by a WO+ - Actionable intelligence that CI have captured a SCP or Hostage. (Such as a living whiteness to the SCPs/Hostages arrest, Stealth OPs in CI base, or scouts spotting them on surface with the SCP/Hostage) - Negotiations must be attempted if the goal is an SCP/Hostage. (Unless the Hostage is of Level 4 Clearance) - After the first Negotiation attempt is sent to CI, MTF must wait 5 minutes, if CI fails to respond to the request, they may raid, however, once negotiations start, a price must be agreed on that satisfies both branches. Once a negotiation price is agreed upon by any MTF person(s) over Open Comms, they must meet with CI to exchange the SCP or Hostage, they may not attempt to raid, or alter the price after any MTF person(s) has said yes to a price. MTF Stealth Operatives and Pathfinders may be used to infiltrate the CI base to confirm the presence of SCPs or Foundation Personnel, if actionable intelligence is uncertain/unconfirmed. This constitutes the beginning of the raid. If the Stealth Operatives and Pathfinders are killed or voluntarily leave the base the raid is concluded and the raid cooldown timer begins. Upon the presence of SCPs or Foundation Personnel being confirmed the main body of MTF forces may move in at the direction of their raid leader, pursuant to SOP guidelines. A raid is concluded once all MTF personnel either are killed or voluntarily leave the CI base. At this point a 10 minute raid cooldown timer begins. A member of MTF must state in MTF Comms: "MTF Raid Beginning" at the start of the raid. If there are less than 6 CI military personnel online this must instead by adverted. A member of MTF must state in MTF Comms: "MTF Raid Concluded" at the end of the raid. A simple fix, but I believe it should resolve a much more stable rule on what MTF must do before preforming a raid. Which will prevent CI and MTF from arguing in OOC, and accusations being tossed at both sides. How would this change better the server? - Minimalized complications post-MTF raids. Are there any disadvantages of making this change to the server? If so, explain. - Absolutely not Who would this change mostly benefit? - MTF, CI, Staff Please link any workshop content, screenshots, or anything that you think may be helpful to those who view this suggestion - N/A
  11. + Support. Rules are vauge on it. Need reworded, though, I still think he should have reached out to CI via comms, either to negotiate, or talk to us about 682s status before he had raided, I understand from his side the lack of understanding on the situation at the same time. Normally I would -Support this as Rektify put it, but this is an awkward case.
  12. This does not put a smile on my face. Was good having you dude.
×
×
  • Create New...