PBS VS BSC WAR: PBS VS BSC - 29/06/2025 20:30

[Anonymous]

I wish to propose to establish some command codes which can further improve responsiveness on the field:

• broken arrow: all squads not on the currently defending sector have to immediately redeploy in defence, the point is being lost and is useless to further engage the enemy anywhere else on the field. This applies to everyone but recon squads (not sure if that has to apply to specops or not)
• tomahawk: all attacking squads must manoeuver toward the next capture point without any further hesitation, issued by the commander after an effective bombing run or when he sees a point is surrounded or we are competing for a capture/loss and we must ensure maximum pressure
• catapult: preceded by a message like “squads able, baker and charlie prepare for catapult”, upon the command they immediately redeploy on the airhead which will be available in the next 20 seconds

Those commands should not be debated (“ok, commander but…”) nor discussed: if they are issued we all respond automatically and without questioning. This implies the commander has to consider their use sparingly and without expecting any delay or additional intel from the field.

SLs have also to train their squads to respond to those commands without further notice: “guys… BROKEN ARROW, BROKEN ARROW!” and the squad has to respond as fast as possible.

What do you think?

[Finalsalute]

i like this idea, this would speed up defensive reinforcements massively, which is an area we struggle in and can improve, a great idea mate

Join Our Discord!
Upcoming Wars!
How YOU Can Help Support PBS

[Jenko]

I really like the idea and can see ‘broken arrow’ as the most useful one. I agree with Callum, I’ve noticed our delay in getting back to defend can be an issue in trainings. There could be a number of reasons for this, though this could certainly help with some of them in my opinion.

If using I think it’d be good to explain the code too. E.g. rather than just saying “broken arrow”, saying “broken arrow – all squads deploy to defend”. Use of code could be not challengeable / shouldn’t be queried.

 

Interested to hear commanders / SLs thoughts on the idea and whether they can see any benefit / likelihood of use

 

[Anonymous]

Jenko wrote:

If using I think it’d be good to explain the code too. E.g. rather than just saying “broken arrow”, saying “broken arrow – all squads deploy to defend”.

My consideration about this variation is it can partially defeat the purpose: if a code is established and understood at least by all the SLs then it shouldn’t require any explanation. I can understand some explanation can be required within squads as we have a constant flow of new entries and rotation, but I would also consider the creation of a sticky post reporting all the information a recruit should read: terminology (zone, sector, strongpoint, etc…), code of conduct (do we have one? if we don’t, we should set one up because the actions of each member reflect on the entire clan), command codes, etc… It might require a few minutes to read and a few days to sink, but also strengths up our image as a well established clan.

I too wish to hear the opinion from the commanders and SLs, but I’m also interested into the opinion of our comrades.

[Powerbits]

Anonymous wrote:

I wish to propose to establish some command codes which can further improve responsiveness on the field:

• broken arrow: all squads not on the currently defending sector have to immediately redeploy in defence, the point is being lost and is useless to further engage the enemy anywhere else on the field. This applies to everyone but recon squads (not sure if that has to apply to specops or not)
• tomahawk: all attacking squads must manoeuver toward the next capture point without any further hesitation, issued by the commander after an effective bombing run or when he sees a point is surrounded or we are competing for a capture/loss and we must ensure maximum pressure
• catapult: preceded by a message like “squads able, baker and charlie prepare for catapult”, upon the command they immediately redeploy on the airhead which will be available in the next 20 seconds

Those commands should not be debated (“ok, commander but…”) nor discussed: if they are issued we all respond automatically and without questioning. This implies the commander has to consider their use sparingly and without expecting any delay or additional intel from the field.
SLs have also to train their squads to respond to those commands without further notice: “guys… BROKEN ARROW, BROKEN ARROW!” and the squad has to respond as fast as possible.
What do you think?

Quote

I like it!

[Anonymous]

@Frank, if you like it and you believe we should do it than this needs your sponsorship to move forward:we might want to include it in the next training and we must inform the squad leaders during the briefing.

[Dee]

Even though i do not act as a Squad Leader during trainings i fully support reduction of chatter on Officer Voice Chat. It is usually huge problem in Public matches.

Squad Leaders are under constant Audio pressure (Officer channel often overlap with Squad channel) and sometimes cannot communicate with Squad Members in time efficient manner or miss important squad intel being said.

Shortening audio commands especially for time sensitive objectives can cut the unecessary clutter.

ie. “Broken Arrow!” (about 1 second of broadcast time) versus “Guys, our previous objective is under heavy attack and we are about to loose it, i need all squads that are not already defending to retreat or redeploy to our previous objective!” (about 11 seconds of broadcast time)

[Powerbits]

Dee wrote:

ie. “Broken Arrow!” (about 1 second of broadcast time) versus “Guys, our previous objective is under heavy attack and we are about to loose it, i need all squads that are not already defending to retreat or redeploy to our previous objective!” (about 11 seconds of broadcast time)

Quote

 

You are right, but its more a repetition as commander . Broken arrow could sound like a broken plate! However I like your ideas, pls keep them coming.  And we will test this out monday 🙂

[Dee]

As G.Threepwood already pointed out. In many tactical operations. Time is of the essence. Delay (may it be from debate or discussion) in executing the task may result in unecessary failure and loss.

And also simple “COPY!” as an answer after receving command from Commander in Office voice chat is usually sufficient 😉

(Many times i have heard “short story” on public Officer Chat instead of an short confirmation – ie. “I am sending an AntiTank guy from my squad to deal with the annoying Tiger tank parking at South West forest on Able Tank Marker. He is now redeploying on our Garrsion at C6 located to the North East!” … if you get my point 🙂 )

[Dee]

Powerbits wrote:

t, but its more a repetition as commander . Broken arrow could sound like a broken plate! However I like your ideas, pls keep them coming. And we will test this out monday 🙂

Quote

We should maybe have a small vote or discussion as to what the actuall “Call outs” would be for given the commands/scenarios. As to avoid miscomunication or confusements. Dont even have to be something non-ordinary. Maybe a simple relatable “Cancel the offensive!” or “Everyone retreat to Defense!” (under 2-3 seconds of broadcast) 🙂

[Powerbits]

sure

[Anonymous]

Anonymous wrote:

broken arrow: all squads not on the currently defending sector have to immediately redeploy in defence, the point is being lost and is useless to further engage the enemy anywhere else on the field. This applies to everyone but recon squads (not sure if that has to apply to specops or not) tomahawk: all attacking squads must manoeuver toward the next capture point without any further hesitation, issued by the commander after an effective bombing run or when he sees a point is surrounded or we are competing for a capture/loss and we must ensure maximum pressure catapult: preceded by a message like “squads able, baker and charlie prepare for catapult”, upon the command they immediately redeploy on the airhead which will be available in the next 20 seconds

 

I believe this is a great idea and it definitely needs to be put into practice, be it in this or in any other form.

[Powerbits]

Lets give it  a try

[GrimTeK_303]

Yep I defo agree with this it will make comms a lot clear too.  And to be fair it won’t take that long to pick up. Before you know it we will be doing in our sleep. 👍

[Dee]

As Grimtek pointed out. Implementation of this system shouldnt be that hard to pull off. It usually only concern Command Chat/Radio and Squad Leaders are intelligent bunch 😉

Simple warning/announcement from Commander at the start of the match should suffice as a first step towards clean comms

[Author]

Posts