Fizzik Posted February 5, 2019 Report Share Posted February 5, 2019 Name: Fizzik Who helped (If applicable): Silvers, Forseen, Miller. Event Name: HVT Kidnapping Summary of the story: The Regimental Commander opened a new firebase and opened himself up for capture. The CIS figured they'd take this opportunity to steal an HVT. What was the result of the event?: The hunters were repelled. Was this more of a role play oriented or "shoot em up" oriented event: Shoot em up. Rule-maker and rule-breaker. Link to comment
Faded Posted February 5, 2019 Report Share Posted February 5, 2019 7 | 10. I shot shit, good enough. 1 Report Link to comment
KillJoy Posted February 5, 2019 Report Share Posted February 5, 2019 7 its wasn't bad just fire base was under staff that was the problem 1 Report Current: Null 10 Jaing Past spots: 501st XO, 501st CMD, 501st WO Appo, TC Hardcase, 332nd Officer , ATK Reg Purge, Keller Unit Vinnie, General Luminara, 41st GCO ARCL Draa, 3rd Crosshair on the Server, Hunter, Sith Marauder TRO, GMM, VA x3. CIS Tac Droid, Guild Cabinet Member, ARCM Colt, Dash 44, Wolfpack Mortar Link to comment
Anime Character Posted February 5, 2019 Report Share Posted February 5, 2019 not only did your event jobs minge their asses off but it intrerupted RP already happening and ruined both encounters, you didnt stop after getting yelled at and didnt communicate to anyone who was trying to figure out what was going on. Spawned your bounty hunters many ships and and had way too much health. 1/10 gonna afk during future events. 1 Report Link to comment
SR_Kangaroo Posted February 5, 2019 Report Share Posted February 5, 2019 7 out of 10: this event as it was a shoot em up and it was fun, -3 points for the reason below: - Too much health - communication: i.e: management of rp's being interrupted (staff side) 39 minutes ago, Anime Character said: it intrerupted RP already happening and ruined both encounters, you didnt stop after getting yelled at and didnt communicate to anyone who was trying to figure out what was going on. To be fair, it is possible for one who was setting up an event and another doing a encounter knowing or not knowing there will be an event is bad communication, something they should work on, so direct blaming one individual shouldn't be the case (even if you didn't mean to make it sound like it). It should be a teams effort of failure to prevent this from occurring in the first place. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now