Regarding asset squads
5 posters
Page 1 of 1
Regarding asset squads
So this has been bugging me for quite a while.
The rules say (as per our forum and in-game scrolling text):
---
NAME YOUR SQUAD AFTER ITS JOB/ROLE
First named squad gets the asset. Do not be to generic with squad names eg.. naming your squad pilot does not entitle you to own all aircraft naming your squad transport does not entitle you to all trans helis and trans trucks etc..
---
We've probably all seen it happen. A squad layout like this:
[1][Tank]
[2][CAS]
[3][Random Infantry]
[4][APC]
[5][Mumble Infantry]
[6][Cache ninjas] (<-- curry)
(anyone care to guess the map? :!: )
It looks good, no? Every squad has their own asset and are getting along just fine.
Now the inevitable happens. The [3][Random Infantry] squad breaks up due to no communication, no leadership, whatever. Leaving the number [3] squad an open spot in the list.
Now some random grievers come along and create: [3][Stryker] squad. That Stryker squad is the first APC/armoured transport squad, as per the rules yes? What happens if those guys in squad [3] now claim the Strykers from squad 4, who formed the original APC squad? Unless an admin/member was on the team and knew squad [4] was the first created APC squad, it is very hard to track who has claim over the asset.
Now it doesn't happen often, but I have seen it occur with less than desirable results and once even having squad [4] disbanded for duplicate squads, because no one was sure which squad was create first.
What is common sense in such a situation? Ask the server population who was first? Or is there anything else that can be done to verify these things?
The rules say (as per our forum and in-game scrolling text):
---
NAME YOUR SQUAD AFTER ITS JOB/ROLE
First named squad gets the asset. Do not be to generic with squad names eg.. naming your squad pilot does not entitle you to own all aircraft naming your squad transport does not entitle you to all trans helis and trans trucks etc..
---
We've probably all seen it happen. A squad layout like this:
[1][Tank]
[2][CAS]
[3][Random Infantry]
[4][APC]
[5][Mumble Infantry]
[6][Cache ninjas] (<-- curry)
(anyone care to guess the map? :!: )
It looks good, no? Every squad has their own asset and are getting along just fine.
Now the inevitable happens. The [3][Random Infantry] squad breaks up due to no communication, no leadership, whatever. Leaving the number [3] squad an open spot in the list.
Now some random grievers come along and create: [3][Stryker] squad. That Stryker squad is the first APC/armoured transport squad, as per the rules yes? What happens if those guys in squad [3] now claim the Strykers from squad 4, who formed the original APC squad? Unless an admin/member was on the team and knew squad [4] was the first created APC squad, it is very hard to track who has claim over the asset.
Now it doesn't happen often, but I have seen it occur with less than desirable results and once even having squad [4] disbanded for duplicate squads, because no one was sure which squad was create first.
What is common sense in such a situation? Ask the server population who was first? Or is there anything else that can be done to verify these things?
Nixy23- Registration date : 2011-05-01
Re: Regarding asset squads
Map is Karbala. Being that it is karbala, the only APC's on there are strykers, so its common sense to call the [APC] squad "Stryker" in the first place, then the problem wouldnt arise.
Bounty- *NwA* Admin
- Registration date : 2010-09-13
Re: Regarding asset squads
to sort this out just takes common sense, if you ask the relevant squads you'll soon realise who's who.
@ bounty, what other APC's are on Karbala ? makes no difference, in fact i've seen almighty arguments when a squad has been named too specifically, over the time Namer, CROWS, MTLB, have all caused a lot of confusion, 30mm or .50 cal MTLB ?
not everyone knows military acronyms or Hebrew for that matter, but admins do have to take into account who was first with the most appropriate / correct name for an asset squad.
often asking for a 'friendly' merging of the squads can work wonders as well, after all they all felt like 'doing' armour for example.
@ bounty, what other APC's are on Karbala ? makes no difference, in fact i've seen almighty arguments when a squad has been named too specifically, over the time Namer, CROWS, MTLB, have all caused a lot of confusion, 30mm or .50 cal MTLB ?
not everyone knows military acronyms or Hebrew for that matter, but admins do have to take into account who was first with the most appropriate / correct name for an asset squad.
often asking for a 'friendly' merging of the squads can work wonders as well, after all they all felt like 'doing' armour for example.
speedhound1-WYD-- Registration date : 2010-02-20
Re: Regarding asset squads
I know its gonna happen so im gonna say it before anyone else does
if the apc was on mumble you could 3 apcs in one squad and the others in another no need for squad 1 = apc 1 squad 2 = apc 2, seen it before, wasted space!
if you got a bit of common sense and speed says then all will be ok, but common sense isnt so common anymore :/
if the apc was on mumble you could 3 apcs in one squad and the others in another no need for squad 1 = apc 1 squad 2 = apc 2, seen it before, wasted space!
if you got a bit of common sense and speed says then all will be ok, but common sense isnt so common anymore :/
Naytdawg- Nayt
- Registration date : 2010-01-05
Re: Regarding asset squads
"First named" is chronological, not as per the squad list.
deadly22sniper- *NwA* Clan Member
- Registration date : 2008-11-30
Similar topics
» Asset squads in mumble
» 1-man locked squads - The conspiracy
» Suggestion about early squads
» Joining squads to get your favorite kit
» PR@IDF wokinstorm asset stealing
» 1-man locked squads - The conspiracy
» Suggestion about early squads
» Joining squads to get your favorite kit
» PR@IDF wokinstorm asset stealing
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum