|
Change Log
[3-43] Battlefield 2 SOP v1.2
1.
General.
A.
Purpose. The purpose of this Standing Operating
Procedure is to ensure that members of [3-43] (new
and old) are familiar with the procedure and
requirements for gameplay.
B.
Updates. This SOP is a living document and will be
updated as is necessary/relevant. Member input to
the SOP is encouraged. Submit change requests
through the EDL or in the on-line forum.
C.
Use of alcohol, tobacco and (legal) stimulants are
authorized for use during play.
2.
Pre-requisites for Play
A.
Software (Required)
(1)
Battlefield 2. Available in both CD-ROM and DVD-ROM
versions.
a.
Current patch:
v1.03 patch.
b.
Profile should be created with the “[3-43]” clan tag
prior to your callsign (e.g. [3-43]PROFESSOR
).
(2)
Xfire. This program facilitates the finding of
teammates online and joining games. It also has a
one-click, one-kill option to join TeamSpeak Server
and Battlefield 2 Server that on-line teammates are
in. See Communication section for amplification.
(3)
TeamSpeak. See Communication section for
amplification.
B.
Software (Optional)
(1)
Server Administrators will be required to download
and install the
Battlefield 2 Command and Control GUI client in
order to perform administrative tasks on the [3-43]
server. Use of the BF2CC GUI requires the
Microsoft .NET Framework extensions v1.1.
(2)
Disc imaging software (Alcohol
and
Daemon Tools) will allow you to make an image of
your play CD/DVD and run it in a virtual CD/DVD-ROM
drive, alleviating the need to find the disc each
time you play.
(3)
Fraps. Fraps is a Windows application that can
be used with all games using DirectX or OpenGL
technology for Benchmarking, Screen Capture, and
Video Capture. Using Fraps in conjunction with the
Battlefield Recorder will allow for distribution of
game video for After Action Review (and bragging)
purposes.
C.
Hardware (Required).
(1)
Microphone Headset. It is highly recommended that
you purchase and use a microphone headset for use
with TeamSpeak while playing. Most [3-43] members
have stated best results (performance and voice
quality) are achieved with USB headsets.
(2)
DirectX 9.0 compatible video card. Check system
requirements on BF2 homepage for
recommended/compatible graphics cards.
3.
Communication
A.
Email Distribution List (EDL).
(1)
Summary
a.
EDL address is
desertcombat(at)scudbuster.com
b.
EDL forwards messages to all current, active members
c.
EDL is maintained by PROFESSOR. New members should
send a message through the EDL with a request to be
added.
(2)
Use. The EDL is a Not Real Time (NRT) means of
communication, intended to spread non-time-sensitive
information to all members. Examples include, but
are not limited to
a.
Software Upgrades
b.
Practice and Game Schedules
c.
Questions and Concerns
B.
Web Site.
(1)
Web Site address is
http://www.scudbuster.com/desertcombat
(2)
The purpose of the website is to post pertinent
information about [3-43] and its members.
Currently, the website includes the following
information
a.
News Page. Any important news or status changes
will be posted here, as well as distributed through
the EDL.
b.
Member Roster. Member roster is used to display
email, Instant Messenger and Xfire contact
information for [3-43] members.
c.
TeamSpeak status and IP address.
d.
Screenshots. Still picture screen captures from
games will be posted, if deemed worthy.
e.
Forum. The forum houses a message board for
members of [3-43] to discuss different topics. In
order to gain access to the “members only” group,
members must register and request membership in the
“Desert Combat” members group. Once membership has
been established, users may post and read messages
in the “Members Only” section.
C.
BF2tracker.com
(1)
General. BF2tracker.com is a web site which uses
the BFHQ stats from the game and displays them in
various different ways. The site also has
a.
Forums with different subjects regarding BF2 (tips,
tricks, tactics, troubleshooting, etc).
b.
Buddy List. To see when teammates/friends are
online or last online.
c.
Clan Tracker. Tracks the stats of the entire clan.
(2)
Registering with the site is optional, but
recommended. Members should use their player name
IAW naming convention in para 2A1b. Once registered
users will have their stats signature displayed on
the 3-43 roster page.
(3)
Register with the Clan. Members can register with
the clan on the site via the “User CP” button and is
located in the Tracker Control Panel. The clan is
listed as “3rd of the 43rd Air
Defense Artillery”. Password to join the clan
tracker is the default password with capital first
letter.
D.
Xfire. Xfire incorporates the following into one
application:
(1)
Friend Tracker. Allows you to see who is online and
what/where they are playing.
(2)
One-click Join. Once you're ready to join members
in a game, simply select the member’s name and click
the Join button. Xfire also incorporates the
launching of TeamSpeak and connection to the
TeamSpeak server in this one-click.
(3)
Server Browser. Xfire's server browser is built
right into the client so you don't need yet another
app running while gaming. Xfire also keeps track of
your most recently visited servers, your favorites,
and even member’s favorites.
(4)
Instant Messaging (in and out of game): Unlike
other IMs, you can run Xfire while playing games. In
fact, you can actually send and receive messages
from inside games without having to minimize or
switch the game window.
(5)
File Download. The latest mods, patches, and can be
downloaded via Xfire using the exclusive, flexible
and convenient peer-to-peer file network.
(6)
Statistics Tracking. Xfire automatically keeps
track of your gaming stats, such as the games you
play and how many hours you've played them, and
displays them on your profile page.
E.
TeamSpeak (TS).
(1)
Summary.
a.
TeamSpeak is a real-time Voice over Internet
Protocol (VoIP) application.
b.
Teamspeak will be used in tandem with Xfire to
coordinate server IP addresses and actions on the
battlefield.
(2)
Use.
a.
TeamSpeak has two components: Server and Client.
The server application allows clients to connect and
communicate. [3-43] members are encouraged to
install both the server and client in order to
facilitate VoIP when PROFESSOR’s TS Server is not
active.
b.
[3-43]
TeamSpeak server status is displayed on the Web
Page.
c.
Anyone can run a TS server. If the [3-43] TS server
is not active, and you are trying to initiate a
game, start your own and publish the IP address thru
the EDL and/or Xfire. See help file included with
the application for specifics on its use.
d.
Channels. TeamSpeak has the ability to create
different channels on the server. This is useful
when members of the [3-43] are on opposite teams or
operating vehicles. The [3-43] TS server is
currently experimenting with vehicle channels for
attack and transport helicopters as well as.
Switching channels is possible via hot-keys: See
TeamSpeak help file for more information. Default
channels on [3-43] TS Server are:
(i)
“Lounge.” This is the default channel for the
server. When all members of the DCC are on the same
team, this channel should be used.
(ii)
“Opposition.” Channel for use by [3-43] members on
a non-USMC team.
(iii)
“Coalition.” Channel for use by [3-43] members on
USMC team.
(iv)
[Trial Vehicle Channels: Attack Helicopter,
Transport Helicopter, Special Ops which will become
SOP upon validation of their usefulness by 3-43
members]
(v)
[Trial Squad Channels: Squad channels within the
teams which will become SOP upon validation of their
usefulness by 3-43 members]
4.
Playing
A.
Scheduled Games.
(1)
Predetermined. The founding members of the [3-43]
originally decided upon the following practice/play
times. These predetermined playtimes are subject to
change. Times published are MST(Z-7)/MDT(Z-6).
a.
Thursdays 1800-UTC. This day was originally based
upon previous Post Commander’s “Family Time”.
Although “family time” is no longer policy, this
predetermined day remains in effect; be advised that
start times will vary on Thursdays dependant on
release time for COB for all [3-43] players.
b.
Saturdays 0830-1200.
(2)
Special Schedules. In the event of training
holidays, effort should be made to schedule game
times as appropriate by use of the Email
Distribution List (EDL). These Special Schedules
should be coordinated NLT 24 hours in advance, if
possible.
B.
Pickup Games
(1)
Pickup games are defined as times not previously
scheduled, but two or members are online and willing
to play.
(2)
Procedures.
a.
Run Xfire. Send messages to those members who are
online, asking them if they want to play.
b.
Load TeamSpeak.
(i)
Check the website.
http://www.scudbuster.com/desertcombat If a
TeamSpeak server is active, join that TeamSpeak
session to allow for vocal coordination for the
game.
(ii)
If no TeamSpeak server is active, start one.
c.
Join server. Join server thru Xfire and continue to
let Xfire run so that others can find and join you.
C.
[3-43] Battlefield 2 Server (12-player, Public,
Unranked).
(1)
General. PROFESSOR has converted old computer parts
into a BF2 server which is physically located at his
house. This is an unranked server that is open to
the public. Primary use of this server will be for
[3-43] members to practice/develop procedures,
tactics and techniques prior to playing on public
ranked servers.
(2)
Maps. Map lists will be dynamic based upon the
needs of the team. The ability to change maps/map
lists will be available to [3-43] server
administrators. Default setting is 1 rotation of
each 32 player map.
(3)
Settings. Server settings will be dynamic based
upon the needs of the team. The ability to change
server settings will be available to [3-43] server
administrators. Default settings are the same as
ranked servers in order to provide a similar
training atmosphere.
(4)
Password. Server password can be enabled/disabled
by server administrators. Default is no password.
(5)
BattleRecorder. The BattleRecorder function of the
server will be active by default and will store the
last ten (10) rounds played.
(6)
Server Administration. The [3-43] server is
currently managed via the Battlefield 2 Command and
Control (BF2CC) system.
a.
Administrators. Server administrators will be
appointed by PROFESSOR on a case-by-case basis.
Priority will go to members with longest time in
service and frequency of play. Requests for admin
privileges will be forwarded thru the EDL ATTN:
PROFESSOR.
b.
Administration. Server administrators will have
special abilities on the server and are hierarchal
in nature. Hierarchal administrative tiers are yet
to be determined. Basic responsibilities of server
admins are the following:
(i)
Keep things Clean. Ensure good sportsmanship and
proper etiquette through use of the “warn/kick/ban
user” scripts. These scripts will be used in the
order listed except in cases of flagrant disregard.
In all cases, reasons for warn/kick/ban will be
stated by admins. In the event that room is needed
on the server by members, users with lowest scores
will be warned and then kicked to make room for
members.
(ii)
Keep players happy. Priority of administrative
tasks default to members’ needs. However, if there
is no team agenda, accommodate players as best as
possible using the “majority rules” settings of the
server (mapvote, user kick, et cetera).
D.
Procedures during play.
(1)
Teamwork. This is how the game is won. Although
the situation on the battlefield is fluid, this
remains a constant. It is essential that members
join and fight in squads.
a.
Team Balancing. Due to the lack of ammo crates and
medical lockers, it is important that a good balance
of player classes are represented within a squad.
This will be METT-T IAW the current
situation/mission but our team will not achieve
objectives if we all spawn as snipers.
b.
Squad Operations. Joining a squad is essential for
communicating events on the battlefield and for
requesting supplies from the commander. If the
situation requires special action (sniper fire,
special ops demolition) personnel should break squad
and join a new one to retain the abilities inherent
with squad-play. Two-man fire team is the smallest
permissible squad size.
c.
Commander Operations.
(i)
Requesting Command. Do not immediately mutiny the
acting commander just because you think you can do a
better job. Ask for command and if denied, apply at
the beginning of the next round.
(ii)
Mutiny. Mutiny against commanders should be
discussed via TS prior to mutiny vote initiation.
Mutiny should be initiated only in extreme cases of
dereliction of duty, fratricide and/or
incompetence. Discussion prior to will allow
members to posture for the mutiny vote, if it is
agreed upon.
(iii)
As commander. When in charge, BE IN CHARGE. Use
all the assets available to you for the benefit of
your squad leaders. Be accommodating to their
requests and be proactive when squad leaders are
silent. UAVs should be flying, supplies should be
dropping, artillery should be firing, and satellite
scan “spotted” messages should be happening all the
time. As commander, your intelligence assets make
the difference between seizing the objective and
failure of team.
(2)
Vehicle use. Lethality of vehicles is directly
proportional to the number of teammates occupying
it. Effort will be made in all cases to load
vehicles and travel as a group.
(3)
Fratricide (Team-Killing) and Friendly Fire.
a.
In the event that a member commits fratricide, the
member will immediately apologize via the commo-rose.
There is no exception to this rule. In the event of
a “n00bish” indirect TK (i.e. running over friendly
mines, running into artillery, chasing after
grenades) light sarcasm is permitted (but
discouraged) through in-game chat after commo-rose
apology. This must be proceeded with additional
typed apology. Example for teammate running over
friendly mines: “Sorry, those big red
skull-n-crossbones are confusing sometimes.”
b.
In the event that a member is Team Killed,
evaluation must be made prior to punishment for Team
Killing. If the Team Kill is determined to be
willful misconduct, punishment is permissible. If
fratricide was self-induced, members will forgive
teamkill. If neither can be determined, members
will allow the server’s punish settings to decide by
waiving the vote.
5.
Etiquette. [3-43] members are not only experts, but
also professionals. Therefore, proper etiquette
will be observed while playing on-line.
A.
In-game chat.
(1)
Name-calling, profanity, abusive/racist/sexist
comments, and arguing through the In-game chat are
prohibited.
(2)
“Light” Smack-talk is authorized, but discouraged.
Actions speak louder than words, so use your
keyboard time for killing the enemy and executing
the mission.
(3)
References to the power and might of Air Defense
Artillery should be used whenever applicable.
(4)
If TeamSpeak is unavailable, In-game chat and commo-rose
should be used to facilitate coordinated movement
and combined arms attacks and defense designs when
possible/applicable. It is also recommended to use
the In-game chat to make the other non-members aware
of situations on the Battlefield.
B.
TeamSpeak.
(1)
Unnecessary chatter will be kept to a minimum in
order to facilitate effective communication.
(2)
Members will assign a hot key to mute their headset
when mounting and dismounting the device on their
heads. Members will also mute during situations
that will cause disruption to the net (i.e.
coughing, sneezing, talking on the phone, etc).
(3)
Use proper radio procedure.
6.
Change Log:
A.
2005-07-16. Original Publish date.
B.
2005-08-17.
(1)
Added stipulation that “legal” stimulants are
permissible for use during gameplay. Para 1C.
(2)
Added BF2tracker.com information. Para 3C.
(3)
Added description of trial vehicle channels. Para
3E2d.
(4)
Included etiquette requirement for headphone
muting. Para 5B2.
C.
2005-10-04. Patch v1.03 Used.
|
