Merrill

4/10 -Good Idea, Connected with Clone Wars Story -Game Helpers were spawning droids on top of players -Droids were not given proper health -Droidekas in tiny hallways on one-lifes is not a good combination. -Objective did not feel feasibly completable due to prementioned obstacles. -Rockets from the frigate fired way too quickly considering we had no way to eliminate it quickly. -Lack of Droid Pods meant that droids were literally being spawned anywhere.

Name: Merrill Helpers: Agent, BigLarge, Techno Event Summary: Medical personnel from a nearby outpost arrive with some medical specimens that seem to be suffering from a form of mutating virus. Needing a second opinion on the findings, they came to Outpost Ironwood with the specimens, prepared for examination. Event Outcome: The samples were dropped off at the base, where damage was found on the outside of the crates. It got into the vents while being transported, and mutated some of the smaller critters hiding inside. Eventually, the clones cleared out the ventilation system through fire and manual purification, purging their base of the virus, for now. Event Type: Mixed

Name: Merrill Helpers: McFisher, Black SOBDE CLASSIFIED INTEL Planet Mygeeto, Location 25°33' N 148°11' E Operatives will be deployed on unmarked transport vessel, codename "SECOND SKIN", where they will be set up with the equipment to complete the mission. Target: Storage site for a corporation known as "MIXED REPAIRS GALACTIC", which has been found to be sneaking CIS trackers and listening devices onto Senator ships, as well as repairing CIS ships under the table despite having a contract with the Republic. Owner is a Bith by the name of Tsa Galur, but will not be on site. However, the Assistant of Operations will be on site, and is marked for Elimination during this mission. The assistant is a Trandoshan by the name of Qurang Das'Mal. Additionally, all security forces on site will be labelled as ACCEPTABLE CASUALTIES. Additional Info: More data towards how and when the target will be eliminated will be given on board SECOND SKIN. A Gotal, codename TRUST, is not to be harmed under any circumstances. He is acting as our mole in this corporation, and was to leave the site on paid leave 30 hours ago. However, intelligence has not yet received confirmation of his absence on site, so TRUST may still be in the line of fire. DO NOT HARM. Additionally, do not blow his cover, or he may fall under the target of the CIS. BRIEFING HAS BEEN ENCRYPTED, DELIVER TO THE REST OF SOBDE IMMEDIATELY. Event Summary: SOBDE are deployed to Mygeeto to frame the CIS in an assassination of one of their business partners. It will be up to SOBDE to breach the security and eliminate the target, whilst ensuring not to harm their mole on the inside. Event Outcome: SOBDE fought against heavy resistance and unforeseen obstacles, but eventually fought through using their wit and tactics. They eliminated their target successfully, and rescued codename TRUST. Event Type: Mixed

Name: Merrill Helpers: Nade, Wagner, Caulin, Assassin Event Summary: A emergency short-range transmission comes in to Outpost Redwood from a surviving member of the Republic Medics. A nearby base had been attacked, suffering many casualties. This Medic is transporting the injured to Redwood for treatment, as his own base no longer had the ability to do so. Event Outcome: The first trip was successful, although one trooper died during medical procedures. On the second trip, the Medic was shot down, and Commando droids tracked the ships data back to Outpost Redwood. Redwood managed to fend off the heavy attack, but suffered major damage casualties. Event Type: Mixed

Name: Merrill Helpers: Maverick, Nade Event Summary: On Endor, it has reached that time of year. A certain species of local fauna is migrating South along their usual route. However, this year, the fauna find a large, concrete obstacle in their path. On a positive note, they seem to have found food covering in multicolored scales living within. Event Outcome: Caves erupted from the ground in MHB, Courtyard, Meeting Room, and more, releasing hordes of the local fauna looking for a nice meal. Slowly but surely, the beasts were pushed back. Caves were destroyed, and the repairs needed were completed. Event Type: Focused Shoot 'em Up

Is it really that hard to say in Comms "Hey, we might have a cloaker, checking now." before doing just that? Players already call out potential cloakers, so that acts as a sign that troopers are activating their detection equipment. GMs would also be monitoring for this and would be able to tell their Event Jobs that the devices are on.

+1, would really help solve staff sits faster

Even if it is a staff member flying through a door, that would count as reasonable suspicion to check since the doors only open when someone either presses a button or moves next to it. The range to press buttons or activate the doors is relatively small, so if you are looking at the doors or buttons, you should be able to see whether a trooper has touched it or if it is opening on "its own". It will be up to RC/SO to recognize these odd situations occurring (aka using logic/ common sense) to activate the cloak detection systems they have in place. 1. We are simply adding a condition where you have to have a reason to turn on detection equipment, then do "/me turns on sensitive headphones/detection visor" Complication is certainly perceived differently by different groups, but a rule change that can be described in one compound sentence and one simple sentence does not seem to be "overcomplicating" things. 2. It hasn't worked, as BigZach pointed out, most GMs either just put up with it or just don't use cloaked enemies. Frankly, from my personal experience of being a GM and GH, the difficulty in using cloak with RC/SO around has led to quite a few deployments where RC/SO were denied to avoid ruining the stealth needs of GM through the cloaker.

I have never had issues with Bio Cloaked and Lords, since they actually RP it out and it makes sense in terms of lore, not to mention it only works against a specific type of cloaked enemy, meaning it has counters. In that case, SO would only be able to exactly pinpoint a droids location or existence when in a quiet setting, since their headphones pick up ALL noise, as that is how hyper-sensitive microphone typically work. Explain how this would cause event jobs claiming meta gaming? If SO/RC are given a reason to search for cloakers (such as doors opening on their own or randomly appearing bombs) , the cloaking detector would see right through cloak when turned on. Metagame will probably happen either way, but it would be actually easier detect with the new rule proposed since it gives exact conditions for activation of the cloak detector and how exact the cloak detector would be.

Name: Merrill RP Rank: Commander Suggestion: Change the rule for SO/RC detecting cloak is done through the activation of equipment upon the suspicion of cloaked enemies being around rather than instantaneous spotting whenever a cloaked enemy is around, always active. Implementation: Just a change of rule related textscreens and addition of specifics to the rule document. Lore: https://starwars.fandom.com/wiki/Cloaking_device Only references to cloaking devices I was able to find shows that the only way to detect cloak was via either tracking of the objects magnetic fields (which could possibly done via handheld or mounted scanning device) or by interdictions fields (created by gravity well generators, only found when dealing with starship cloaks). Purpose of this change is to give GMs more ability to use cloaked enemies to accomplish objectives before an event begins without having to simply place bombs/communicators/etc whilst in staff mode. This would make events involving cloaks go more smoothly for the GMs and increase player immersion by not forcing GMs to create conflict while in staff mode. Workshop content if applicable: NA

Name: Merrill Helpers: Harte, Sonny, KnightVR, Trijim Event Summary: A senator and his guards come by for an Audit of Outpost Redwood, to determine where funds and supplies should be focused for the best operation of the base and its other facilities nearby. A successful visit would mean increased funding for all base functions, but if something were to go wrong... Event Outcome: Many troopers were hostile to the Trandoshan Senator, and a brief scare for a supposed spy left everyone frightened. The Senator continues on with his base evaluation, only to be interrupted by a physical threat: a knifing and bombs. A secondary squad shows up to finish the job, only to be wiped out. Event Type: Mixed.

Sorry Forgot to actually send confirmation that I was back on the 18th

Name: Merrill Staff Rank: Senior Admin Length of LOA (Please specify date if possible): 5/2-5/15 Reason: Finals and finishing up the school year Do you understand that if you go LOA on a named Jedi Character for more than two weeks, go on LOA on any RC character, or go LOA while being clone commander, you will be removed from that position: Yes Do you understand that if you are going on LOA for more than two weeks you may lose your leadership position?: Yes

*Rubs hands together maniacally*

Name: Merrill Helpers: Techno, Elijah, Unusual, Goofy, Mave Event Summary: During a mission to capture an outpost featuring a large drilling site for blaster crystals, a drop goes bad. Troopers find themselves in cells with no weapons and only one objective: escape. Event Outcome: A few troopers were lost as they made their escape through the massive facility, picking up weapons and equipment as they went. Along the way, they met the helpful droids FATE, GREEN, and MERC, who helped the clones to escape. In the final fight as the clones prepare a freighter for escape, the droids stayed behind to protect them, revealing hidden weapons as a final protocol to protect the living. Type of Event: Mixed

+1 Support As my time as Rancor HC, I watched Jayarr rise up the ranks as Hammer and move up to Havoc. Every time I was on, he was busy doing trainings and tryouts, discussing topics with the units, and getting our recruits invested into the ARC program. At this time, even though I'd hate to see him go as my fellow Commander in Rancor, I know that with the work and dedication he is willing to put in, he can do great things.

-1 Support A lot has been said and there are arguments for both sides, but with my own personal experiences and the fact that, while a battalion may not need help, the Recon Reg should not focus a sole battalion and ignore interacting with others. Just because there might not be problems on the surface to fix, you can only see underlying problems by actively interacting with all of the battalions.

@Synyster You forgot to tag me for helping with the building

Name: Merrill Helpers: Nade, Harte, Loopy, Synyster Event Summary: A town has released a distress beacon for unknown reasons. The Clone Outpost would not respond to calls, so troopers were sent in to assess the situation. Event Outcome: Troopers discovered a maniacal droid in the sub-areas of city, playing a sick game with the citizens and the newly arrived troops. The droid forced the clones through all sorts of sick games, even forcing them to choose which of their brothers had to die. Ultimately, they pushed through these "games", and beat the ever-living hell out of the droid and its protectors. Type of Event: Mixed

Name: Merrill Helpers: Josh, Elijah, Synyster, Killjoy, Patricia, Dennis Event Summary: Republic Intelligence revealed a CIS stronghold that has been working on frigate power systems, improving them to be more durable in battle. Event Outcome: Troopers pushed a series of checkpoints as 187th dropped from behind, opening up the blast doors to the fortress. To shut down the inner rayshields, they had to reassemble a damaged battery to gain access to the inner generator. Once finished, the clones met with the mastermind of the operation. (And then the server crashed.) Type of Event: Mixed

9/10 A couple of event jobs got a bit out of control at one point, would advise working on that in the future. Otherwise, strong idea and execution.

+1 Support Frees up Base Ops to make the server even more RP focused, might give Shock more to do, and it means that it will be easier for battalions to leave the base in emergencies. The suggestion isn't saying to remove the PTE PTL system, it's just saying to move the buttons.

Name: Merrill Helpers: Omalic, Synyster, Unusual, Shakes, Patricia, Ragen, Loopy Event Summary: Near the city of Nar'Treyat, Republic intelligence has found a CIS Commander who has been working on new technological advancements for droids and ships. A new ship type is on the outskirts and must be destroyed, alongside the CIS Commander. However, due to the weapons on the ground, troops have to make their ways through the city. Event Outcome: The troops had to help out the city before breaching a rayshield to the prototype ship. Once its cooling generators were destroyed, they moved on to meet the commander, who ensnared them in a trap. While his weapons were dangerous and strong, the clnes persisted until victory. The CIS attempted to flank through the city, but ultimately failed once more. Type of Event: Mixed

Glad to see people having real excitement with RP!

Name: Merrill Helpers: None Event Summary: A damaged LAAT crashes into the lake, bearing blaster damage from a recent battle. Event Outcome: The pilot of the LAAT was unable to be saved, having died of asphyxiation before being retrieved. Meanwhile, the CIS had tracked the LAAT and assaulted the nearby outpost, not realizing just how well defended it was. Type of Event: Mixed