It looks like you're new here. If you want to get involved, click one of these buttons!
teams would be ad hoc channels created when needed by characters,
similar to parties. However, fire teams will represent smaller groups
of characters in a common party. Members of parties may be assigned
to individual fire teams on their creation, or may be invited to
existing fire teams. Fire teams will each have a name to serve as an
identifier for easy communication.
group combat strategy sometimes
necessitates peeling off portions of a group to accomplish separate
tasks. Additionally, party channel spam can often be
difficult to keep up with, when parts of the chatter are irrelevant
to all party members.
solution would allow the retention of a common party channel for
communication between smaller groups, while also cutting down on spam
created by other fire teams.
will also represent smaller groups of combat forces that may be
commanded as a single unit. For example, a raid leader may command a
single fire team to perform a certain task. This has the additional
benefit of allowing less-experienced group leaders to practice
leading while leading a smaller strike force.
mechanics exist in other games for management of large groups and
smaller sub-groups. Achaea's culture of scripting and automation
represents an increased reliance on the party channel than many of
these other games (notable example: World of Warcraft and raid with
sub-parties). Yet, we lack this form of organization, despite
our increased reliance on these channels for communication as
compared to those graphical games.
it should be noted that this proposal represents an addition to the
game whose use is optional. Since the Party channel is already in
use, I decided for purposes of this proposal to keep parties as they
presently exist largely unchanged in their purpose and use. People
will not need to change their scripts if they choose not to use fire
particular raid force consists of both melee and ranged fighters.
While retaining a common party channel for coordination, both the
melee and ranged teams will operate on separate channels for tighter
coordination around their separate tasks.
raid force decides that with their greater numbers than their
opposition, they would like to leverage their greater numbers by
taking down two targets at a time, rather than one – forcing the
defenders to split and defend as well.
Verb: FT (replaces PARTY verb in all “existing”
COLOUR FTTELLS pick the colour for your fire team channel
FT ACCEPT accept an invitation into a fire team
FT INVITE <who> invite someone into your fire team (and party, if
FT INVITE FRIENDS invite all online friends to your fire team (and party, if
FT MEMBERS see who is in your fire team
FT QUIT quit your fireteam
FT TELL <message> say something to your fire team
FTT <message> say something to your fire team
FTTOFF stop listening to your fire team channel
FTTON listen to your fire team channel again
FTWHO see who is in your fire team
FT CREATE [name] create a fireteam and specify an optional name. If
is listed; use Alpha, Bravo, Charlie, Delta, etc as names.
PARTY FT ASSIGN <ft> <who> assign a character to specified fireteam “ft”
PARTY FT DESTROY <ft> destroy a fireteam
PARTY FT RENAME <name> <new> rename a fireteam
fire teams have been organized for a given party, the following
changes ought to be made to parties for the purpose of providing
increased visibility to what fireteam a character belongs to:
Party chats should be changed to: (Party): Person ($fireteam_name) says, “message.”
PWHO and PARTYWHO should be changed to display a character's present fireteam next to their name.
Fireteam Related Echoes
have been assigned to fireteam $fireteam_name by $name.
$name has left fireteam $fireteam_name.
The fireteam $fireteam_name has been destroyed by $name.
The fireteam $fireteam_old_name has been renamed to $fireteam_name by $name.
$Name has invited you to join their fireteam, $fireteam_name. (Accepting will change your party.)
SIDE TOPIC: Hard coded party/fireteam leaders and chain of command
Achaea presently treats all party members as equal. As many of us have experienced, this can lead to great confusion about who is actually calling targets, especially when the RP-appointed party leader has died. While off-topic, I think that a mechanic can be created where party and fireteam leaders can be appointed, as well as a chain of command that the game will respect when a leader has died. This was potential need is prompted due to both the experience of being uncertain as to who is calling targets in the present system, as well as authorizing a certain person to create/destroy/rename fire teams, as well as move people between them.