diff --git a/LICENSE-2.0.txt b/LICENSE-2.0.txt
new file mode 100644
index 0000000..d645695
--- /dev/null
+++ b/LICENSE-2.0.txt
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/admin/admin_colist.php b/admin/admin_colist.php
new file mode 100644
index 0000000..96db4e0
--- /dev/null
+++ b/admin/admin_colist.php
@@ -0,0 +1,75 @@
+
+
+
+ include("conf/config.php");
+ $coid = $HTTP_COOKIE_VARS[$randomstr2];
+
+ $qry = "SELECT co.id, co.charname, co.email, co.admin,
+ ships.id, ships.name, ships.co, ships.lastmreport,
+ co.password
+ from co left join ships on co.id=ships.co";
+ $coqry = mysql_query($qry,$link) or die(mysql_error());
+ $cos = mysql_fetch_array($coqry);
+?>
+
+
+
+
+
+
+
+
Welcome to the Administration Tool for the echo $taskforce_ab; ?> Website
As a CO in Task Force 86, maintaining your ship's entry in the Commanding Officer's
+Lounge Menu is one of the
+most important things you, as a CO, can do OOC. Your ship's entry must be kept
+up do date at all times. This guide will help you understand the abilities you
+have, and what they are intended for.
+
+
+
+
Logging In
+
+The first step in doing any task in the
+Commanding Officer's Area is logging in. To do this, select CO's Lounge on the
+menu. On the page that is accessed, enter your username and password in the
+indicated fields. If you
+do not remember your password, email
+Admiral
+Wolfeso that he can retrieve it
+for you. Once the fields are filled, click Login. This will bring you to the
+main page.
+
+
+
Adding/Deleting Crew
+
+The CO's
+Lounge contains a manifest of your crew which must be kept up to date. This
+manifest will be applied to your monthly reports. To add
+a crew member to the manifest: (This includes you, the CO) At the bottom
+of the crew listing, fill out the three available fields. The first field is the
+character's name. Second field is their position. Third is their email address.
+Do NOT type in a rank, the software does that automatically. Click the [Add] link.
+This will place your crewmember into your manifest, and assigns them a rank of
+cadet. You need to click on [Edit] and update their rank.
+To update their rank, select the correct color and rank from the drop down box. NOTE: Make sure to use
+the appropriate color. The colors are as follows.
+
(Starfighter) - Starfleet Fighter
+Pilots (Carrier) (Grey) - Intelligence Officers
+(Red) - Command, Flight
+Control, Strategic Operations (Purple) - Diplomatic Corps (Blue) -
+Medical, Science, Counseling (Green) - Marine Corps Cadet / Civilian - Use for Cadets and
+Civilians (Gold) - Operations, Tactical / Security, Engineering
+
Once the
+crewman's new information is entered, click Edit again. To delete a
+crewman from the manifest, simply click the Delete button at the end of that
+crewman's row on the main page.
+
+
+
Editing Crew Information
+
The
+edit information already entered for a crewman, click the edit button at the end
+of that crewman's row on the main page. This will return you to a page exactly
+like the one you originally used to enter that crewman's information. Simply
+edit what you wish, and click Edit.
+
+
+
Editing CO Information
+
This is where you can update
+your own information, such as email address and password. This will not change
+your entry in the crew manifest though. Be sure to update it there as well.
+
+
+
Editing Sim
+Information
+
Much
+of the information displayed with your ship/station's banner on the website is
+controllable by you. The things you can edit are Mission Title, XO, MCO,
+COB/CMC, website, # of Posts, and # of awards. Just update what ever information
+you need to, then click edit after that field.
+
+
+
Assigning XO, MCO, COB/CMC
+
On
+the Task Force website, your sim's Executive Officer, MCO, COB/CMC are displayed below
+yourself. What member of your crew is displayed there is controllable by
+you. Before you can assign a crew member to the one of
+these
+positions, they must first be entered into the crew manifest on the TF site. For instructions on doing
+this, see Adding/Deleting
+Crew.
+Once the XO, MCO, and COB are added to the manifest, select the crewmember to
+fill the needed postion, and then click the [Assign] button next to the entry.
+The MCO and COB position has an option in the drop down box for ships that do
+not want these positions on their ship. Just select No MCO (OR COB) Postion - Do
+Not Display. This can always be changed at a later time.
+
+
+
Filing A Monthly Report
+
To
+file your monthly report, click the [File Monthly Report] link at the bottom of
+the main page. This will present you with the report form. Your sim's name, status, website address, and manifest are automatically
+entered. You simply have to fill in the remaining fields with the requested
+information and click Submit Report.
+
Ship
+Awards: Note any awards your
+ship may have received in the past month. Also, any BH HoH awards that you
+are submitting your crew for go here.
+
Crew Promotions
+Performed or Planned for Next Month:
+Mention any promotions you have handed out to your crew in the
+past month, and any you plan to hand out next month.
+
Website Changes in the
+Past Month: Note any changes
+(major or minor) you have made to your ship/station's website in the past
+month.
+
+
+
Post Announcement
+
By clicking this link, you can post an announcement to the TG
+site. On the main page, the last several annoucements show up. There's also an
+actual annoucement page that shows all fo them. This is NOT a place to post any
+type of recruiting messages. This is more for general simm news. Welcomes and
+promotions, etc, are ok, as well as brief mission updates.
+
+
+
+
Add Ship / Edit the Open Position List
+
This can be a great recruiting resource. There's a link to this
+on the main site, but only to browse and/or modify. You need to come here to add
+your ship to the list first. Basically, the open position list (OPL) will allow
+a site visitor to see what positions may be open at a glance. They can search by
+position names, by ship classes, or by individual simms themselves. Once you add
+your ship to the list, you can add up to 9 positions of crew that you are
+looking for. If you forget your password, or the ship entry wasn't deleted from the old CO, please email
+Admiral
+Wolfe so he can reset it. This will require you to readd your ship, there's no retrieving passwords
+from the OPL.
diff --git a/co/edit_co.php b/co/edit_co.php
new file mode 100644
index 0000000..70a685d
--- /dev/null
+++ b/co/edit_co.php
@@ -0,0 +1,71 @@
+
+
+
+ $qry = "SELECT id, charname, rank, email, password, realname, race, tfrole FROM co WHERE id=" . $coid;
+ $coqry = mysql_query($qry,$link) or die("Can't get co");
+ $co = mysql_fetch_row($coqry);
+
+ $qry = "SELECT rankid, rankdesc, image, color FROM rank";
+ $rankqry = mysql_query($qry,$link) or die("Can't get ranks");
+ $rank = mysql_fetch_row($rankqry);
+
+
+
+?>
+
+
diff --git a/co/edit_crew_engine.php b/co/edit_crew_engine.php
new file mode 100644
index 0000000..76faba6
--- /dev/null
+++ b/co/edit_crew_engine.php
@@ -0,0 +1,51 @@
+
+
+
+ }
+
+ if( $name != "" && $email != "" && $position != ""){
+
+ //header("Location: switchboard.php");
+
+ $qry = "SELECT id FROM ships WHERE co=" . $coid;
+ //echo "$qry\n ";
+ $shipqry = mysql_query($qry,$link) or die("Can't get ships id");
+ $ship = mysql_fetch_row($shipqry);
+
+ $qry = "UPDATE crewlist SET charname='" . addslashes($name) .
+ "' WHERE id=" . $crewid;
+ //echo "$qry\n ";
+ $update = mysql_query($qry,$link) or die("Can't update values");
+
+ $qry = "UPDATE crewlist SET rank=" . $rank . " WHERE id=" . $crewid;
+ //echo "$qry\n ";
+ $update = mysql_query($qry,$link) or die("Can't update values");
+
+ $qry = "UPDATE crewlist SET email='" . $email . "' WHERE id=" . $crewid;
+ //echo "$qry\n ";
+ $update = mysql_query($qry,$link) or die("Can't update values");
+
+ $qry = "UPDATE crewlist SET position='" .
+ addslashes($position) . "' WHERE id=" . $crewid;
+ //echo "$qry\n ";
+ $update = mysql_query($qry,$link) or die("Can't update values");
+ ?>
+
+
+
+ }
+ else {
+ echo "You did not enter all required information. Hit your BACK button and try again";
+ }
+
+ mysql_close($link);
+?>
+
+
diff --git a/co/edit_ship.php b/co/edit_ship.php
new file mode 100644
index 0000000..4ec8d4e
--- /dev/null
+++ b/co/edit_ship.php
@@ -0,0 +1,96 @@
+
+
+
+SEARCH ~ Bravo Fleet
+
+
+
+ $subtitle = "Ship Maintenance"; include("htinc/header.php") ?>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Edit Ship's Information
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ include("htinc/footer.html") ?>
+ mysql_close($link) ?>
diff --git a/co/edit_ship_engine.php b/co/edit_ship_engine.php
new file mode 100644
index 0000000..8dcc805
--- /dev/null
+++ b/co/edit_ship_engine.php
@@ -0,0 +1,30 @@
+
+
+
\ No newline at end of file
diff --git a/co/index.php b/co/index.php
new file mode 100644
index 0000000..03bc782
--- /dev/null
+++ b/co/index.php
@@ -0,0 +1 @@
+
diff --git a/co/login.php b/co/login.php
new file mode 100644
index 0000000..31832e0
--- /dev/null
+++ b/co/login.php
@@ -0,0 +1,57 @@
+
+
+ $coid = $HTTP_COOKIE_VARS[$randomstr];
+
+ if($coid != 0){
+ $pageref="switchboard";
+
+ }
+?>
+
+
+
+
+
+ Please enter your e-mail address and password to access the CO's Functions
+
+ if($code==1){
+ ?>
+ Invalid E-mail/Password Combination
+
+ }
+ ?>
+
+
+
+
+
+
+
+
+
+
diff --git a/co/loginvfy.php b/co/loginvfy.php
new file mode 100644
index 0000000..2884e03
--- /dev/null
+++ b/co/loginvfy.php
@@ -0,0 +1,24 @@
+
diff --git a/co/month_report.php b/co/month_report.php
new file mode 100644
index 0000000..74019a9
--- /dev/null
+++ b/co/month_report.php
@@ -0,0 +1,103 @@
+
+
+
+
+
+
+
+
+
+
+
+ mysql_close($link) ?>
+
+
+
diff --git a/co/month_report_engine.php b/co/month_report_engine.php
new file mode 100644
index 0000000..d37d03d
--- /dev/null
+++ b/co/month_report_engine.php
@@ -0,0 +1,69 @@
+
$qry");
+
+ $qry = "insert into monthrep values(NULL,'$ship[1]','$ship[4]','$ship[9]',
+ '$shipawards','$promotions','$websiteupdates')";
+ mysql_query($qry,$link) or die(mysql_error());
+
+ echo "
You report has been submitted to the Admiral.
";
+ echo "RETURN";
+
+ mysql_close($link);
+?>
diff --git a/co/month_report_engine.php~ b/co/month_report_engine.php~
new file mode 100644
index 0000000..10b6a8f
--- /dev/null
+++ b/co/month_report_engine.php~
@@ -0,0 +1,62 @@
+You report has been submitted to the Admiral.";
+ echo "RETURN";
+
+ mysql_close($link);
+?>
diff --git a/co/post_announcement.php b/co/post_announcement.php
new file mode 100644
index 0000000..94affb9
--- /dev/null
+++ b/co/post_announcement.php
@@ -0,0 +1,20 @@
+
+ Enter your message to be posted to the Announcements page. Valid HTML tags
+ are br,b,i,u and a.
+
+
+
+
diff --git a/co/shipedit.php b/co/shipedit.php
new file mode 100644
index 0000000..6d6104d
--- /dev/null
+++ b/co/shipedit.php
@@ -0,0 +1,64 @@
+
+
+
\ No newline at end of file
diff --git a/co/status.php b/co/status.php
new file mode 100644
index 0000000..497a0a0
--- /dev/null
+++ b/co/status.php
@@ -0,0 +1,3 @@
+
COID: =$email?>
+
Select:
+
Query: =$qry?>
diff --git a/co/switchboard.php b/co/switchboard.php
new file mode 100644
index 0000000..e9d2305
--- /dev/null
+++ b/co/switchboard.php
@@ -0,0 +1,288 @@
+
+
+
+
+
+
Welcome to the CO's Administration Interface for =$taskforce_sn?>. Here you can maintain your crew
+ list, post announcements and submit your monthly reports.
+
You can no longer change your ships status through the
+ lounge. Ship status changes must go through either your
+ TFCO or TFXO. Plese contact them to have this change
+ made.
Star Trek, Star Trek: The Next Generation, Star Trek: Deep Space 9, Star Trek: Voyager and Star Trek Enterprise are registered trademarks of Paramount Pictures, Viacom and their respective owners. No revenues are generated by the use of the Star Trek trademark and no copyright violation is intended.
+
This role-playing game and associated websites are purely for entertainment purposes. Some images used on this site courtesy of DevilsWorld6 and/or Collective 359.
+
This site is operated by Task Force Management System Copyright 2000-2004 SPMSDev Team. Originally created as a joint project of Ed Smith, Ben Lindstrom and Jason McCormick.
+ If you're site offers an award we'd love to apply for it. Send us mail and let us know.
+
+
+
diff --git a/tf/co_apply.php b/tf/co_apply.php
new file mode 100644
index 0000000..05c624a
--- /dev/null
+++ b/tf/co_apply.php
@@ -0,0 +1,332 @@
+
+ include("conf/config.php");
+
+ $qry = "SELECT id,name,class FROM ships WHERE co=0 and grp!=100";
+ $shipsqry = mysql_query($qry,$link) or die("Bad ships fetch query");
+ $ships = mysql_fetch_row($shipsqry);
+ /*
+ 0 = id
+ 1 = name
+ 2 = class
+ */
+?>
+
+
+
+
+
+
+
+ 1) As a CO of a ship in Bravo Fleet you are required to follow all the guidelines of running
+ such a ship as outlines on the Bravo Fleet website at www.bravofleet.com
+ under the CO's Training section of the Bravo Fleet academy. If you are not familiar with these rules and
+ regulations, look there first before you apply for a ship. In addition, all CO's in BravoFleet are required to attend
+ and graduate from the BravoFleet CO Academy before assuming independent, active command of their ship. If you
+ feel that your qualify for an exception to this (i.e. previous CO's training in another sim), please note that in your application below.
+
+ 2) As a CO of a ship in Bravo Fleet you are required to maintain a website for your ships and
+ actively update and maintain said site. Failure to do so can result in dismissal from command.
+
+ 3) When applying for a ship, be certain that you are applying for the ship name and class that you really want. There
+ is no possibilty to transfer your command to another ship.
+
+ 4) You are only allow to have one command in Bravo Fleet at a time. Having more than one command is gounds for
+ dismissal from BravoFleet. In addition, one person may only have 5 characters in Bravo Fleet, including your command
+ character.
+
+ 5) Resigining from command of a ship in Bravo Fleet comes with a 90-day suspension from command. If you resign
+ from a ship for whatever reason, you cannot apply to command another ship for 90 days.
+
+ Complete all information in the form. Incomplete applications will not be considered and summarily rejected. Please
+ take your time with this form and think it through. Your success at getting the position you are requesting depends
+ primarily on this application.
+
+
As a CO in Task Force 72, maintaining your ship's entry in the Commanding Officer's
+Lounge Menu is one of the
+most important things you, as a CO, can do OOC. Your ship's entry must be kept
+up do date at all times. This guide will help you understand the abilities you
+have, and what they are intended for.
+
+
+
+
Logging In
+
+The first step in doing any task in the
+Commanding Officer's Area is logging in. To do this, select CO's Lounge on the
+menu. On the page that is accessed, enter your username and password in the
+indicated fields. If you
+do not remember your password, email
+VAdm Chadwick so that he can retrieve it
+for you. Once the fields are filled, click Login. This will bring you to the
+main page.
+
+
+
Adding/Deleting Crew
+
+The CO's
+Lounge contains a manifest of your crew which must be kept up to date. This
+manifest will be applied to your monthly reports. To add
+a crew member to the manifest: (This includes you, the CO) At the bottom
+of the crew listing, fill out the three available fields. The first field is the
+character's name. Second field is their position. Third is their email address.
+Do NOT type in a rank, the software does that automatically. Click the [Add] link.
+This will place your crewmember into your manifest, and assigns them a rank of
+cadet. You need to click on [Edit] and update their rank.
+To update their rank, select the correct color and rank from the drop down box. NOTE: Make sure to use
+the appropriate color. The colors are as follows.
+
(Starfighter) - Starfleet Fighter
+Pilots (Carrier) (Grey) - Intelligence Officers
+(Red) - Command, Flight
+Control, Strategic Operations (Purple) - Diplomatic Corps (Blue) -
+Medical, Science, Counseling (Green) - Marine Corps Cadet / Civilian - Use for Cadets and
+Civilians (Gold) - Operations, Tactical / Security, Engineering
+
Once the
+crewman's new information is entered, click Edit again. To delete a
+crewman from the manifest, simply click the Delete button at the end of that
+crewman's row on the main page.
+
+
+
Editing Crew Information
+
The
+edit information already entered for a crewman, click the edit button at the end
+of that crewman's row on the main page. This will return you to a page exactly
+like the one you originally used to enter that crewman's information. Simply
+edit what you wish, and click Edit.
+
+
+
Editing CO Information
+
This is where you can update
+your own information, such as email address and password. This will not change
+your entry in the crew manifest though. Be sure to update it there as well.
+
+
+
Editing Sim
+Information
+
Much
+of the information displayed with your ship/station's banner on the website is
+controllable by you. The things you can edit are Mission Title, XO, MCO,
+COB/CMC, website, # of Posts, and # of awards. Just update what ever information
+you need to, then click edit after that field.
+
+
+
Assigning XO, MCO, COB/CMC
+
On
+the Task Force website, your sim's Executive Officer, MCO, COB/CMC are displayed below
+yourself. What member of your crew is displayed there is controllable by
+you. Before you can assign a crew member to the one of
+these
+positions, they must first be entered into the crew manifest on the TF site. For instructions on doing
+this, see Adding/Deleting
+Crew.
+Once the XO, MCO, and COB are added to the manifest, select the crewmember to
+fill the needed postion, and then click the [Assign] button next to the entry.
+The MCO and COB position has an option in the drop down box for ships that do
+not want these positions on their ship. Just select No MCO (OR COB) Postion - Do
+Not Display. This can always be changed at a later time.
+
+
+
Filing A Monthly Report
+
To
+file your monthly report, click the [File Monthly Report] link at the bottom of
+the main page. This will present you with the report form. Your sim's name, status, website address, and manifest are automatically
+entered. You simply have to fill in the remaining fields with the requested
+information and click Submit Report.
+
Ship
+Awards: Note any awards your
+ship may have received in the past month. Also, any BH HoH awards that you
+are submitting your crew for go here.
+
Crew Promotions
+Performed or Planned for Next Month:
+Mention any promotions you have handed out to your crew in the
+past month, and any you plan to hand out next month.
+
Website Changes in the
+Past Month: Note any changes
+(major or minor) you have made to your ship/station's website in the past
+month.
+
+
+Post Announcement
+
By clicking this link, you can post an announcement to the TG
+site. On the main page, the last several annoucements show up. There's also an
+actual annoucement page that shows all fo them. This is NOT a place to post any
+type of recruiting messages. This is more for general simm news. Welcomes and
+promotions, etc, are ok, as well as brief mission updates.
+
+
+
+Add Ship / Edit the Open Position List
+
This can be a great recruiting resource. There's a link to this
+on the main site, but only to browse and/or modify. You need to come here to add
+your ship to the list first. Basically, the open position list (OPL) will allow
+a site visitor to see what positions may be open at a glance. They can search by
+position names, by ship classes, or by individual simms themselves. Once you add
+your ship to the list, you can add up to 9 positions of crew that you are
+looking for. If you forget your password, or the ship entry wasn't deleted from the old CO, please email
+VAdm Chadwick so he can reset it. This will require you to readd your ship, there's no retrieving passwords
+from the OPL.
diff --git a/tf/index.php b/tf/index.php
new file mode 100644
index 0000000..dd674fe
--- /dev/null
+++ b/tf/index.php
@@ -0,0 +1,74 @@
+
+ Welcome to the home of Bravo Fleet's Task Force 72 - S.E.N.T.I.N.E.L. Here you will find information on the various ships in this TF, as well as any other relevant information. The Task Force is continually growing and expanding, so check back often for updates!
+
27 Starships and 1 Deep Space Station form Task Force 72, with the mission of tactical interdiction and exploration. We invite you to take a look at some of these ships, and maybe even join the crew. We're always looking for new talent to add to the game! If you feel confident and experienced, you can also try applying for command of a ship. We still have a few ships in need of Commanding Officers and Executive Officers. Use the apply forms on the left frame. With your help, TF72 and Bravo Fleet can continue to provide quality simming to everyone. Thanks!
+
Task Force 72, and all of our simms (Ships) are active members of Bravo Fleet. Currently, Bravo Fleet is one of the largest and most active Star Trek Simming organizations on the internet today. At last count (Febuary 2002) We had almost 160 simms with staff on board. Each day that number continues to grow. Along side that news is the even more important fact that we need crews to staff all those ships. It only takes a few players to create an active and thriving simm. Evey single player counts. So if you feel the call, and would love to be a part of the adventure Enlist now! Live the Adventure Today!
+
+
Task Force 72 Live Stats:
+
+ $qry = "select count(id) from ships where status = 'active'";
+ $activeqry = mysql_query($qry,$link);
+ $active = mysql_fetch_array($activeqry);
+ print "$active[0] Active Ships ";
+
+ $qry = "select count(ships.id) from ships inner join co on co.id=ships.co where grp <> 100";
+ $activeqry = mysql_query($qry,$link);
+ $active = mysql_fetch_array($activeqry);
+ print "$active[0] Staffed Ships ";
+
+ $qry = "select count(email), count( distinct email) from crewlist";
+ $activeqry = mysql_query($qry,$link);
+ $active = mysql_fetch_array($activeqry);
+ print "$active[0] Active Characters $active[1] Active Players";
+?>
+
+
+
+
+
+
+
+
+
+ $qry = "SELECT * FROM announce order by stamp desc limit 5";
+ $annqry = mysql_query($qry,$link);
+ $announce = mysql_fetch_row($annqry);
+
+
+ $ANNOUNCE = 1;
+
+?>
+ Announcements can be posted by all CO's via the CO's Lounge.
+
+
+ while($announce != 0) {
+ $qry = "Select * from co where id=" . $announce[3];
+ $coqry = mysql_query($qry,$link) or die("Bad CO's query. Did you Delete this CO?");
+ $co = mysql_fetch_row($coqry);
+
+ $qry = "select * from rank where rankid=" . $co[2];
+ $rankqry = mysql_query($qry,$link) or die("Bad CO's rank query. Did yo udelete this CO?");
+ $rank = mysql_fetch_row($rankqry);
+?>
+
+
Instructions: This is the official application form to apply for service in echo $TF ?>.
+ Please keep in mind the following guidelines for new members:
+
+ 1. Please take your time on the application. You getting the position you're applying for depends in part on
+ the quality of character that you design here on this form. It will also partially depend on your ability to
+ proofread what you have written.
+
+ 2. At all times, you as a Starfleet Officer or Crewmember are required to maintain the dignity of the position
+ and to act according to the rules governing the simulation. More plainly: flaming, trolling and profane-filled
+ tirades will not be tolerated by any member of the simulation. In addition, the mailng list for the the ship you belong to
+ is not to be used in any way other than for e-mail simulation traffic. Warez, serialz and porn are not welcome.
+ Any person who engages in these activities will be warned once and then summarily dismissed from the simulation.
+
+ By submitting this form, you acknowledge you have read and agreed with the above.
+
+ Okay, enough of the leaglize, on to the good stuff!
+
+
+ Items marked with * must be completed or your applicaiton will be ignored. For Character Names, a last/common/family name is required
+ however a first and middle are optional since many characters from Star Trek only have one name.
+
+
+
+
+
+
+
diff --git a/tf/join_engine.php b/tf/join_engine.php
new file mode 100644
index 0000000..bfde785
--- /dev/null
+++ b/tf/join_engine.php
@@ -0,0 +1,69 @@
+
+ include("conf/config.php");
+
+$qry = "SELECT ships.id,ships.name,co.email FROM ships, co WHERE ships.co=co.id AND ships.id=$ship1";
+$shipsqry = mysql_query($qry,$link) or die("Bad ships fetch query");
+$ships1 = mysql_fetch_row($shipsqry);
+//echo "$ship1, $ships1[0], $ships1[1], $ships1[2] ";
+$qry2 = "SELECT ships.id,ships.name,co.email FROM ships, co WHERE ships.co=co.id AND ships.id=$ship2";
+$shipsqry2 = mysql_query($qry2,$link) or die("Bad ships fetch query");
+$ships2 = mysql_fetch_row($shipsqry2);
+//echo "$ship2, $ships2[0], $ships2[1], $ships2[2] ";
+$ship1email = $ships1[2];
+$ship2email = $ships2[2];
+if ($ships1[0] == 20)
+{
+ $ship1email = "";
+// echo "
These are sites that we feel are helpful to our members. If you have a site that you feel would benefit from having a link here please contact VAdm Robert Chadwick, and request a link exchange.
+
+
diff --git a/tf/sample.php b/tf/sample.php
new file mode 100644
index 0000000..99990ea
--- /dev/null
+++ b/tf/sample.php
@@ -0,0 +1,300 @@
+
+
+Crew app | CO app
+
+
+Crew App:
+
+Character name: Maximillian Hunter
+
+Race: Human (Non-Earth)
+
+Birthlace: Alpha Centauri Colony
+
+Birthdate: 11-AUG-2345
+
+Gender: Male
+
+Rank type Commisioned
+
+Desired Ship: USS Belvior
+
+Alternate Ship: Starbase 99
+
+Desired Position: Executive Officer
+
+Alternate Position: Chief Engineering Officer
+
+Have you attended Bravofleet Academy? Yes
+
+Physical Description:
+
+Height: 2.1 Meters
+Hair: Brown
+Eyes: blue
+Average Build
+
+
+Bio: (Your starting rank is based on this!)
+
Max grew up on the Alpha Centauri colony world. His father was an engineer for the capital city's main power facility. Due to this Max grew up understanding the basics of power generation and distribution at an early age.
+Max grew up care free and easy going on Alpha Centauri, his love for the engineering discipline just could not be satisfied. He decided early on that he would study things dealking with energy.
+
+
Max progressed through Starfleet Academy and made several tours on Starships during his early carrer. After the dominion war Max was offered a move from Engineering to ops. One which he reluctnatly took. To this day he generally keeps to himself the reasons for this, but it seems to stem back to his time on the Ganymede research base. His time there apparetnly was a turing point in his life.
+
+
His first Command Duty was aboard the USS Belvior, when long time friend Captain Alexander Grant asked him to take the step from Ops to Command. He gladly followed and has now served with Alex aboard three seperate Starships.
+
+
+Bigraphical Data
+2367 - Graduated from Starfleet Academy, Major-Engineering, warp core theory
+2367 - Received rank of Ensign. Assigned to USS Achillies, Engineering.
+2368 - Promoted to Lt, J.g. and assigned to lead a damage control team aboard the USS Achillies
+2369 - Transfered to USS Yuengling as warp core specialist
+2369 - Promoted to Lt. and transfered to Ganymede as Design Engineer
+
+ * Worked on integrating new power systems into front line combat craft.
+
+2372 - Promoted to Lt Commander while at Ganymede after completion of numerous successful projects
+2372 - Assigned to USS Pharris as Chief Engineer during Dominion war
+
+ * Continued warp core research onboard the TAC Frigate Pharris
+ * During his time on the Pharris, one of his Power distribution theories was rejected by Starfleet R&D and Max Considered himself the "Laughing Stock" of the R&D division.
+
+2374 - Assigned to USS Lexingtion as Strategic Engineer after the Dominion war.
+
+ * Brought several prototype fightercraft for testing from his previous position.
+
+2376 - Promoted to Commander
+2376 - Assigned to USS Belvior as Executive Officer
+
+ * Given outstanding recomendation by previous CO.
+
+2377 - Promoted to Captain and Transfered with the rest of the Belvior crew to the new USS Denmark.
+2378 - Followed Alexander Grant once again to the newly commisioned USS Belvior.
+
+ * Max has once again found need of his Engineering skills as he assists the new crew of the Belvior in installing new prototype modules to the Belvior's warp core.
+
+
+
+
+
+Scenario:
+
Please reply to the following situation as you would as your first desired
+position in post form. Please delete all of this text when doing this.
+
+
"It's 0330 hours and you are asleep in your quarters. The room is dark, quiet, and you're in the middle of a great dream... when
+suddenly you hear the ships alarm, and someone comes over the comm and says
+"Red Alert!!"
+
+
Max, a light sleeper, bolts upright in bed. Quickily realizing the situation he
+reaches for his Comm badge on the night stand and contacts the Bridge.
+
+
HUNTER: +TAPS+ Hunter to the Bridge, What's the situation?
+
+
CONCOLOR: =/\=Max this is Concolor, We've encounted some kind of Quantum
+String Fragment. You'd better come to the bridge right away, and bring a
+engineering kit too.
+
+
HUNTER: On My Way!
+
+
Hunter Pulls his uniform on quickly He looks quite unlike his usual Clean
+Shaven and neatly pressed self. He leavs his quarters and heads straight for the
+bridge stopping only once to pick up an Engineers Field Kit out of a side
+bulkhead. He guesses there is some damage on the bridge of Concolor wouldn't
+have asked for a repair kit.
+
+
HUNTER: * Stepping into the Turbolift * Computer, Bridge.
+
+
computer: Turbolifts are inoperative above deck 4.
+
+
HUNTER: Well then, Deck 4. Center section. I guess I'll have to crawl the
+rest of the way.
+
+
Max, leaves the turbolift and heads straight for a Jefferies Tube. This
+particular one will drop him off near his own office on Deck 2. He can use the
+access ramp through the Observation lounge at that point to reach the Bridge.
+
+
When Max Arrives on the Bridge things are fairly well in hand. Captain Grant
+has arrived and is Coordinating damage Control With Colquhoun the Ops Officer.
+
+
GRANT: * Noticing Max enter the bridge * Max, Excellent can you help Concolor
+repair the tactical station. We should be able to restore sensors and weapons
+through there. We'll likely need both ASAP to get out of this one.
+
+
HUNTER: Aye, sir. * Max heads over to TAC and opens the Kit and begins
+working. *
+
+
+
Off:
+
+Role-playing experience:
+The Adventure Continues - Astrometrics Officer 1992-1993
+USS Melbourne - XO 1998-1999
+USS Toranado - Chief Engineer 2000
+Assorted Table RPG Games:
+D&D
+Palladium
+Robotech
+Magic: The Gathering
+
+
+How did you learn about TF72 and Bravo Fleet?
+
+A friend pointed me at Bravo Fleet.
+
+
+
+
+CO App:
+
+Character name: Sorac Dunar
+
+Race: Bajoran
+
+Gender: Male
+
+Birthplace: bajor
+
+Rank type Commisioned
+
+Desired Ship: USS Constantinople
+
+Alternate Ship: USS Rodi
+
+
+Character Description:
+
+Height: 1.85 Meters
+Hair: Brown
+Eyes: Blue
+Build: Average
+
+d
+
+
+Bio: (Your starting rank is based on this!)
+
+
+Dunar is an easy going person. He tries to not let the everyday stresses of life get to him, and tries to always have a smile on his face. He consideres the best way to motivate his crew is to keep them laughing. While he is not overly funny, or into body humor he will when needed come up with a witty one-liner, or strut out of a room in dramatic fashion.
+
+
+
+
+In Command Dunar generally expects a certain level of professionalism from those under him, but like to keep things light at the same time. He has been known to indulge in a few card games with his crew before. He seems quite fond of the games Black Jack, Eucher and Sabac.
+In times of crisis Dunar attempts, and typically succeeds, in keeping a level head, and a confidance that he will finish a winner. While confident, he tends to consult his most trusted senior staff members on major descisions if the situation permits.
+
+
+
+
+As a child his family escaped the cardassian controlled Bajor to the refugee camps. His father\'s skills with mechanical equipment proved a blessing to the family which helped them raise money for food and eventually earn them a trip away from the camps.
+The Sorac family took the opertunity without even asking where the ship was heading. They later found out that the destination was Earth\'s moon Luna. Once there Dunar\'s father began working in local shuttlecraft maintanance yards. He eventually wound up earning a spot on the prestiegious McKinnly Ship Yards team. It was from here that he was able to get Dunar a chance to take the Starfleet entrance exams.
+
+
+
+
+Dunar applied to the academy wanting to be in Engineering.
+However, before being accepted he switched his major to Science. It was always
+his first love.
+While he excelled at the sciences much of the theoretical
+math required of him was beyond his understanding. It took much work,
+and many late nights with his peers to help him in his understanding
+of his subjects. While his grades were by no means spectacular
+ ( they were fairly average) he always made it though.
+
+
+
+
+After graduating from the academy Dunar loooked forward to getting away
+from Earth, and out into the stars. Although he is far from home most of t
+he time he tries to return to Tycho City to visit his parents whenever he
+can. In fact just before taking commmand of the Constantinople he returned
+from a pilgrimage with his father to Bajor, where they were able to be in the
+presence of one of the orbs of the prophets.
+
+
+
+
+2361 - Graduated from Starfleet Academy, Major-AstroPhysics
+2361 - Received rank of Ensign. Assigned to USS Eclisiaties, Stellar Cartography department.
+2361 - Promoted to Lt, J.g. and assigned as small group leader aboard the USS Eclisiaties
+2363 - Transfered to USS Tuvo in Astro Physics Research.
+2367 - Promoted to Lt. and given position of Senior reasercher
+Began exploring Command alternatives.
+2370 - Promoted to Lt Commander and transfered to USS Enterprise during her travels in the Gamma Quadrant after the war. Assigned as Head of Stellar Cartography
+2375 - Promoted to Commander - Assigned to USS Melbourne( Gamma Fleet ) as Executive Officer. Where he served under Captain Ben Maxwell.
+2376 - After 6 months on the USS Melbourne Dunar was given Command of the USS Constantinople in TF86 of BravoFleet.
+ Given outstanding recomendation by previous CO (Ben Maxwell).
+2376 - Transfered to S.E.A.R.C.H. After the retirement of RAdm GreyStone, and Promoted to Captain
+ Promoted to Comodore and made Task Group Commander of the Cochrane Group.
+2377 - Transfered to Task Force 72. Given the rank of Rear Admiral and Made the Executive Officer of TF72.
+2377 - Given Command of Task Force Seventy-Two after the loss of the USS Hood
+with all hands, including Vice Admiral Anon.
+2378 - Promoted to Vice Admiral.
+
+
+Scenario:
+
Dunar wakes up groggy. This is not a good time to bother him. It had better
+be damn important or somebody was going to get it. Dunar, is NOT a morening
+person and Has a terrible time with missing sleep.
+
+He reaches for the Comm link on his nightstand.
+
+
SORAC: Sorac, here. What's the problem. * He rubs his head to get rid of the headache.*
+
+
BOND: Sir, There seems to be something wrong with our Klingon Escourt ship.
+They are having power grid fluctuations and sensors are picking up weapons fire
+throught the ship.
+
+
SORAC: On my way. Alert Hancock and Hunter to join me on the bridge.
+
+Sorac, gets up and puts on his uniform. Almost walking out without attaching his
+comm badge. He grabs his Phaser from his desk, just in case. Klingons, even as
+allies can be very unpredictable.
+
+
Sorac, reaches the bridge, and finds Hancock(XO), Hunter(2nd) and Markov(Ops)
+already there. Of the three Hancock looks worst for wear. The Ex Special Op
+vetran doesn't even have Jumpsuit on. He's in casual pants and a black T-shirt.
+his Comm badge attached to the waist band of his pants.
+
+
SORAC: Status?
+
+
MARKOV: We're showing weapons fire on board the kla'Benga.
+
+
HANCOCK: * Who serverd with the Klingons during the Exchange Program * It's a
+coup. One of the Senior Officers is trying to take command.
+
+
HUNTER: We should try and find out who started it and put an end to this. We
+need their help for this relief mission to succeed.
+
+
HANCOCK: You'll never know who it was. One side WILL destroy the other.
+Unless Commander Turre himself lives, which is very unlikely. We'll never know
+who was on which side, and to be perfectly honest. The klingon high Command
+won't care either. Torre has no family in any important positions.
+
+
SORAC: Well I"ll have to defer to Scott on all Judgements, but I Think it's
+best that we raise shields to prevent this spilling over onto the
+Constantinople. Asside from that I want someone to monitor the situation and
+alert us when the kla'Benga restores comm with us. Mr. Bond the Bridge is yours.
+alert me if the situation changes. Be prepared for anything. These are Klingons
+we're dealing with.
+
+
Off:
+
+
+
+Role-playing experience:
+The Adventure Continues - Astrometrics Officer 1992-1993
+USS Melbourne - XO 1998-1999
+USS Toranado - Chief Engineer 2000
+Assorted Table RPG Games:
+D&D
+Palladium
+Robotech
+Magic: The Gathering
+
+
+
+How did you learn about TF72 and Bravo Fleet?,br>
+I am the XO on the USS Belvior in TF93.
+
Many people help make Task Force 72 what it is, too many to name them all. However, the following people are those who participate in the day to day runnings of this TF.
Click on the left to see the various organizational subunits of TF72's ships. If you see a ship that interests you, you can find out how to join up with that ship from their website. Or alternatively, you can submit an application to the CO of the Task Force by clicking the JOIN link at the bottom of each page and they will place you with a ship needed a crewmember with your qualifications.
+
+
+ }
+ else{
+?>
+
+
echo $group[1]; ?>
+ Click on the graphic to visit the ships's website. Click on the
+ CO's name to e-mail that CO.
+
+ if($group[1] == 'Open Commands'){
+ echo("
Task Force Seventy-Two is made up of five Task Groups.
+
Click on the left to see the various organizational subunits of TF72's ships.
+ If you see a ship that interests you, you can find out how to join up with
+ that ship from their website. Or alternatively, you can
+ submit an application to the CO of the Task Force by clicking the JOIN
+ link at the bottom of each page and they will place you with a ship
+ needed a crewmember with your qualifications.
+
+
+
+ }
+ else{
+?>
+
+
echo $group[1]; ?>
+ Click on the graphic to visit the ships's website. Click on the
+ CO's name to e-mail that CO.
+
+ if($group[1] == 'Open Commands'){
+ echo("
Click on the left to see the various organizational sub-units of TF86's ships.
+ If you see a ship that interests you, you can find out how to join up with
+ that ship from their website. Or alternatively, you can
+ submit an application to the CO of the Task Force by clicking the JOIN
+ link at the bottom of each page and they will place you with a ship
+ needed a crewmember with your qualifications.
+
+
+
+ }
+ else{
+?>
+
+
echo $group[1]; ?>
+ Click on the graphic to visit the ships's website. Click on the
+ CO's name to e-mail that CO.
+
+ if($group[1] == 'Open Commands'){
+ echo("