-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Whiplash
-
-
2 minutes ago, Zyner said:
So then what's the point of this suggestion?
Changing it to Stealth Operations thats the point
-
Just now, Fizzik said:
-1 this suggestion was done without BCMD approval.
Why is that bad?
-
Just now, Zyner said:
Shadow Clone Troopers are a thing and are basically what SO is. Blackout, Jet & Spark are Stealth Operators which I believe actually deals with either flying or overseeing stealth operations, hence their very Pilot-Like armor, whilst not actually being in the battlefield.
Shadow Troopers were their own division so there was no actual label to them, it could be called Shadow Company to amend that.73rd Shadow Battalion is 100% fanon - http://swfanon.wikia.com/wiki/73rd_Shadow_Battalion
Whilst Shadow Troopers are real, there do not actually fall into a Battalion or unit, they are a division.
Cool then if they are a division the there would be no point in changing the name to Shadow Company.
-
Just now, Spooky said:
they did do it in the first place tho
Then why did they change it.
-
1 minute ago, Spooky said:
it's used all over, because it's an actual lore thing
we used to have it and it made sense, why not have it again?
Talk to the Synergy higher ups about it then because they would of done that in the first place.
-
1 minute ago, Zyner said:
Why not Shadow Company?
I do not think shadow company is an actual thing. It is actually called the 73rd battalion and that is being used on icefuse.
-
1 minute ago, Spooky said:
this is literally just a name change
-1
Not a valid reason for a -1 but ok.
-
Name: Karma
Suggestion: Changing Special Operations to Stealth Operations
Implementation: Replace anything in the server that identifies as Special Operations and Change it to Stealth Operations.
Lore: Currently as a reconnaissance battalion we have Special Operations. The reason is because they did not want this battalion in the SOBDE Regiment. This is why we should change the name. Special operations is actually called the 44th Special Operations Division under the SOBDE Regiment (http://starwars.wikia.com/wiki/Special_Operations_Brigade). So if SO is not going to be identified as an SOBDE Battalion then it should not have this name. Next is that Special Operations Utilize stealth cloaks unlike any other battalion. The 44th Special Operations Division is not known for that. There is barely any lore for that battalion. There is a Battalion that utilizes cloaking devices called Stealth Operations lead by Commander Blackout. Putting aside that they operate cloaked ships and not cloaked Armour (http://starwars.wikia.com/wiki/Stealth_operations_clone_trooper) . And there is my third point is that in the job menu the Commander Job for Special Operations is called Commander Blackout (http://starwars.wikia.com/wiki/Blackout/Legends). How does that make sense? You are literally using another commander for a battalion even though the commander has their own battalion that they operate. Stealth Operations has lore to their battalion unlike the 44th Special Operations Division. So if Special Operations has a commander from stealth operations, utilize cloaking technology like stealth operations, has more lore to them then Special Operations, and is not part of SOBDE unlike Special Operations then we should just change the name and job names to Stealth Operations because they are stealth troopers. Also do not suggest Shadow Company
-
Name: Event Idea - 4 day Scheduled Event
Event Name: Operation (Insert)
Summary of the storyline (The Game Maker who chooses to run this event should contact you for more info):
Event Idea - 4 day Scheduled Event
-
4 days long with each day dedicated to a certain event
-
Each day the event will be at a scheduled time given the whole day if needed to plan
-
Each Battalion will be used on different days
-
Gives GM(s) multiple days to plan out each event
Day 1 - Mission Briefing
-
GM will come to Naval with the Objective they are given, the planet it will be on, and any information they know off hand or want to RP to get access to at GM’s discretion.
-
Naval will go to the event server on the planet that the event will be placed on and then they will start creating a plan with the resources they were given and have already. You can do multiple places on multiple maps for each day and they can plan for each part: Recon, Attack/SOBDE, Specialized.
-
Naval will meet with Reconnaissance battalions to plan out what they will do for recon.
Day 2 - Reconnaissance
-
Naval with their information will send out Recon Battalions to recon the area(s) for the event and relay the information back to the Naval. They might have there own mini-event to make sure they get the information they need without possibly alerting enemies
-
Naval receive information and meet with the Commanders of the next day operations. They would plan out what they are going to do with the attack and SOBDE battalion commanders and give them orders of what they will complete the next day
-
Battalion commanders will brief there troops on what there objective is and maybe train for the event that will happen tomorrow.
Day 3 - Commence operation (Naval can come up with name)
-
The operation with Attack/SOBDE/104th Battalions will commence and they will attempt to complete their objectives.
-
Naval will overlook operation as it happens and help plan with anything that goes wrong. Commanders will communicate and cooperation is key to completing objective.
-
While the naval are overlooking they are speaking with the defense battalions on what they are going to do the next day concerning defense of the FOB.
-
Depending on whether the Attack/SOBDE battalions complete their objective(s) will decide whether the possible retaliation on the FOB will be easy or hard for the defense Battalions.
Day 4 - Defense
-
As stated on day 3, the Special Battalions (DU/CG/) will have to protect the FOB from whatever the gamemasters have planned for them. Whatever happens depends on how good of a job the Attack/SOBDE Battalions did on their objective.
-
They will have to protect the naval while the naval come up with plans on how to hold the planet. ( This will not be an event but just some RP to see if this invasion was successful)
Jobs Required: Gamemaster(s) Discretion
Vehicles Required: Gamemaster(s) Discretion
Map being used (If applicable for event server): Gamemaster(s) Discretion
Any additional information:
Once this is done everyone will report back to the ship and they will discuss what happened. How and Why it happened. And how everyone can improve themselves from their possible mistakes. Also Gamemaster(s) can get feedback from everyone on each day. Side note: after every day the battalions used will go back to main and have a debrief and do as was stated above. This gives ample time for Gamemaster(s) to take the day to plan the events at hand, get event jobs which since each day uses only some battalions the other ones not being deployed will give more resources for event jobs. *EDIT* High Command will be participating in planning and might even control the troops on the ground when their battalions get deployed.
-
1
-
-
Who's Online 8 Members, 0 Anonymous, 31 Guests (See full list)
4 day event - Day 2- Recon event
in Events
Posted · Edited by CollinTheMarines
Name: Karma
Who helped (If applicable): Scorch, Prince, val dour
Event Name: Recon Event -Day 2 of operation
Summary of the story: Recon Battalions were deployed to A CIS stronghold on planet Mygeeto and were to infiltrate and extract data from 3 consoles without getting noticed and if they did to get data before CIS forces were alerted and data was wiped. They had to avoid patrolling droids and tanks/aircraft patrolling the area
What was the result of the event?: Recon Battalions recovered 3/3 parts of the Data and failed to complete the event without alerting CIS Forces on the Base. Generally did a good job with their jobs assigned to them during operation.
Was this more of a role play oriented or "shoot em up" oriented event: Role Play at the beginning and shoot them up once the battalions were spotted.