Phoenix
Phoenix: BSE
Phoenix at a Glance
The Game
Sign Up
Nexus Tour
FAQ
Flagship#130 Review
Contact
Resources
History
Wallpapers
IRC and player sites
SubSpace Static Archive
214
Previous Years
Intergalactic News
The Dewiek Special
Issue 31
Issue 30
Issue 29
Issue 28
Issue 27
Issue 26
Older Issues
 
The Daily Run

Daily Running of Phoenix

From the player perspective it just seems a case of create some orders and press submit. The orders are collected, processed along with everything else and the results generated. This can lead to confusion as to why certain things happen as they do.

This is essentially a breakdown of what happens on a given day.

Start - Around 7am
Only turns that have been submitted by 6.50am GMT can be guaranteed to meet the deadline.
Download Emails
This checks a specific mailbox, pulls down everything and deletes them from the mailbox. It then has to decode any attachments, remove spam and check passwords and positions before adding them to the directory for incoming orders.

Possible issues
If the mailbox is not accessible the game will halt until the issue is resolved. We once had an issue with somebody mailing their entire turn directory as an order attachment. This caused the game to crawl as it attempted to download and read it for possible turns. This prompted a limit on the mail size to be set. Early on there were issues with unusual encoding for file attachments. These though have long since been resolved and we haven’t had issues in nearly many years.

Download Nexus Turns and Ancillary Data
While the game engine is dealing with the emails, DBsync shunts down turns that have been uploaded to Nexus from off-line order editors and those created using the Nexus Order Editor. Again there is a fair bit of data checking.

Ancillary data includes new ship designs, votes, changes to relations, mission actions and most importantly any new users (sign-ups).

Possible issues
These are not too common though generally relate to the shunting down of data. Data drop-outs can cause partial data downloads though DBsync has an indicator when this happens and a manual download can be initiated if necessary. This tends to occur when there are world events that are making the internet unstable (ISP maintenance, hacktivists hitting major nodes).
Once this has been done, Nexus is updated with the game status.

Maintenance Run
The next step is purely Game Editor and starts the process of organising the daily run. It updates the game with respect to new accounts and mission requests along with working out votes. There are quite a few steps to this of which the primary output at our end is a list of politicals to be maintained on the day and their current wealth.

Once these steps have been completed, a list of positions due for maintenance is generated. All positions undergo maintenance once per week on a pre-set day. For ships this is merely paying wages and seeing if the ship and its cargo decay a little more. For starbases it includes a full raft of checks, including research, production and merchandising to name a few. For starbases, outposts and political positions it will also process any orders that have been submitted for the position along with any standing orders, these being orders that have been specifically set to run at the time of maintenance (special actions are shuffled out and set for processing later in the day). For other positions, their orders will be processed later, even if they are maintained now.

The positions are processed sequentially from the first position to the last in the list.
Possible issues

The only real issue with this is that when a starbase, outpost or political has been set so that it runs after another position. If this happens to be on its maintenance day, it will remove any sequencing as it processes the orders for the position during this stage.

Orders Run
After the maintenance run is completed, the game editor moves on to create a list of all positions that have orders to process. This includes starbases, politicals and outposts that have not had their maintenance on this day. In the case of these positions, they need to have submitted a request update along with the submission of orders of the results of their orders will be appended to their between turns file to be generated when they next have a turn.

This is the longest part of the day and can account for thousands of positions encountering hundreds of positions. The amount of data that is processed means that a lot of effort has been made to make the code run as fast as possible where the code segments are used a lot. Nowadays, all positions are loaded into memory when they are first called and remain in memory until the game is closed. There are still a few more tricks to pull that Darak is working on though the separating of the run into orders and specials means that turns are sent out much earlier in the day.

Possible issues
This is a robust part of the game. If issues occur then it is highly likely that they are due to a recent upgrade. Positions that enter battles have their turns suspended and the position is removed from the front interface to prevent dozy GM meddling. This means that in some circumstances the submission of a special action will not even be accessible until after a battle is run. This can occasionally prove frustrating for players seeking to issue a mid-battle action.

An issue that thankfully happens infrequently is where a sequence includes a position with a special action. This halts the entire run in order for the GM to deal with the special action. The usual culprit is a ship in the middle of nowhere doing a surface exploration that has inexplicably been sequenced to a bunch of other positions presumably by accident. The other suspect is a base issuing a special action along with build hiport and therefore sequenced before the delivering ship. Occasionally, in fact, very rarely, there is a legitimate reason and the special action will be dealt with there and then.

Generally speaking, a halt in the run is spotted fairly promptly and dealt with. If you have sequenced specials into a run and turns arrived later than usual, then you probably have yourself to blame...

Battles
Battles require little more than selecting the identified battle and pressing a button – though the Game Master may take a closer look at any battle prior to initiating it. This may be done if there is something suspicious about the battle. These sorts of things used to be much more common, before the days of alliances, do not target lists and relations. On more than one occasion I have intervened for example when a Confederate (or was it Brotherhood) starbase and platform mistakenly added everybody to the enemy lists. I think that the pre-combat list indicated that a few dozen starbases, outposts and many more ships would have been pulled in.

Possible issues
This has been something of a minefield over the years as players have always pushed the boundaries. The biggest bugbear to date was the sending of entire warfleets into combat without enemy lists. The reliance on defend and support only resulted in spiralling checks as it looked for anyone willing to attack so that it could assign everybody to following them – over a thousand ships and not a set of balls between them. Something of an inruptus castratum. The code has now been modified to prioritise checks making this issue a thing of the past.

Where we are aware that there could be an issue, such as battles with thousands of ships, we will as a precaution take a battle-back-up. This pulls only part of the game data but reduces the time for a restore considerably. Over the years as the code has become ever more robust, this feature, like many others has become largely redundant and an unnecessary time constraint.

Finish Order Run and Send
After battles and updates to battling positions have been completed the next step is to add the manifests to the positions in the order run and any positions in the maintenance run that are to be sent out. This leaves only the positions with special actions, investigations and explorations outstanding.
At this point the game has generally been running solidly for around two hours and everything should have been received before lunch (in the UK).

This step assigns the turns to the email client and DBsync, freeing up the editor for the Game Master to deal with the remaining positions and their orders. As these are two separate programs they run simultaneously. On a day with few internet issues, the uploading of turns to Nexus will take around an hour while emails take around twice as long. Nexus is updated as to the progress.
As part of the step Nexus is also updated to include changes in markets, squadrons, treaties, stellar transactions, missions and a raft of other things including personal data.

Possible issues
The main issue is internet connectivity. While DBsync attempts retries that cope very well with natural blips, a longer drop-out will cause a halt that needs to be manually reset. This can cause timing issues as a complete fail close to the end of an upload requires it to start again. This is because it is normally a lot faster to upload all the data files (html turn results) then update the database that links them to Nexus accounts.

The email client however deals with turns individually so any drop-out simply requires the client to be started again. These are not particularly common.

Specials Run
Before we separated special actions from the orders run there was always the pressure to try to finish the run as fast as possible, or at least defer special actions if it was getting late in the day. This is simply because players need time to evaluate the results of the day before creating and submitting more orders. In the case of battles getting the results of a battle back in the early evening meant submitting orders for the next day was very difficult.

During this phase the Game Master simply deals with the explorations, investigations and special actions submitted for the positions. This is often very time consuming with the need for breaks (some days can feel like sitting exams). More details about being a Game Master for Phoenix can be found in IGN 5. Breaks in this case are often doing other things for the game such as writing IGN’s, looking at data in the game, discussing game improvements with Darak and answering PM’s – amongst other things.

Possible Issues
There is always the situation where a special action can present itself as part of a sequence of turns. Often this is simply a player getting over enthusiastic with the sequence request and they don’t really need some chaps to examine amphibians before their warfleet teams up with the rest of the armada. When these pop up a quick glance at the sequencing list allows the position to be removed from the list. There is also the potential that the actions of the position could trigger a battle though to date this has not happened in a situation where it is at all significant.

Send Specials and Back-up
The sending of these turns is as above, though rarely takes more than a couple of minutes though this second time there is also turn fee charges included. Following this the game normally initiates back-up.



Weekly Markets
On a Monday, there is an extra step. This calls the routines that sell goods from starbases to the planetary markets. This step also deals with income generated from claiming systems. This is very intensive and takes more than an hour to run though as it is done overnight, has no significant impact on game timing.

Bank Holidays
With Bank holidays everything is effectively run twice, one complete day after the other. The only real difference between the two runs is that in the first run only a couple of hours are spent doing Game Mastering (investigations etc). Sometime after lunch when an hour or so has passed since turns have been uploaded, all remaining positions will have their orders deferred. It is not quite this arbitrary though. The Game Master will have a look at the turns to see if some are urgent and try to give appropriate priority.

Deferred positions will depending on their type, be pushed through the next run or their next maintenance (in the case of bases). Then it is just a case of completing the stages and starting again with a new download.




 
News
Is open for business...
 
user image

*** Inter Galactic News ***
  • DEN assault FEL base and get wiped out
  • CIA Trade fleet caught and destroyed by the DEN
  • Krell denounce worship of the True One

  •  
    user image

    ***** Inter Galactic News *****

    Huge fleet skirmish at the London/Crossley wormhole

    A large fleet of over 700 DEN warships responded to the EMP action in Crossley, where a 4000 hull DEN platform was destroyed. Reports show the DEN ships caught a group of CIA ships napping and inflicted significant losses on the humans. IMP and GTT fleets moved to assist the CIA, matching DEN fleet numbers, but the arrival of over 1200 Hexamon ships seems to have tipped the battle in favour of the DEN-HEX alliance.

    The combined DEN-HEX force pushed through the wormhole into the Heartland area of human space and retaliated, attacking several CIA platforms in response. The outnumbered Empire fleets abandoned the area and fled, they are currently waiting for the larger alien force to make their next move from their hiding places.
     
    user image

    ***** Inter Galactic News *****

    Admiral Lord Simms killed after a long and distinguished service to the Empire.

    The Imperial Services have intercepted and serious damaged several DEN ships on the way to the Empire’s home systems. Unfortunately during the action Admiral Lord Simms was injured and reports from the Viceroy indicate he has passed away, fighting the enemies of the Empire like any true Imperial Officer.

    The Viceroy has stated that the officers and crew of the DEN ships have been captured and are now awaiting trial at a secret IMP base.

    DEN continue to strike at the Empire

    Reports are coming in of multiple engagements between the Empire and the Dewiek Elder Nation over the last week. With several battles taking out Empire ships in the Heartland of the CIA.

    AFT turn to piracy

    The Association of Free Traders have, after a long history of neutrality, turned to piracy this week. AFT Drake boarded an IND ship in the Halo periphery, killing several of the crew in the process.
    Independent trader Jarlebanke Langhofdi immediately took to the public communication channel demanding an answer to why supposedly peaceful traders had killed his crew and taken his ship.

    The AFT remain silent over the attack.
     
    user image

    ***** Inter Galactic News *****

    Combat Special Edition

    Since the DEN started shooting at those lovable FEL fluffballs things have certainly been heating up. So we through it would be prudent to bring you, gentle beings of the peripheries, a special edition in order to keep you updated with all the latest action in regards to who the DEN are shooting and who is shooting them.

    Felini strike back at Dewiek

    Reports have come in of the FEL striking back at the DEN in the Kallisan system. A huge FEL force supported by the IMP and CIA assaulted DEN positions taking both the platform and base called Lucien. There was much rejoicing in the FEL camp as the Felini proved they were not such lovable fluffballs after all!

    GTT get sucked into the war

    A passing fleet of GTT warships got caught in the fighting and this saw the GTT enter the war. When asked about this CEO Fox pointed out they are not warships at all, they are trade defence ships. So how they came to be in the DEN system of Kallisan is a mystery to us. But the GTT CEO was clear that they only engaged using support and defend orders to protect allies. Needless to say, the CEO commented “We found ourselves on the Dewiek Nation’s enemy lists pretty soon after.”

    Dewiek Nation attacks GTT positions in Orion Spur, breaking DOM system rules

    A fleet of DEN warships has engaged and destroyed a significant number of GTT cargo ships and escorts in the DOM system Monument. The GTT immediately took to the public channels to ask why the DOM were not doing something. In reply the DOM issued a statement to stop, which the DEN ignored.

    The DEN newssheet "The HOWL" published a completely unbiased review of the attack shortly after.

    DOM make a choice

    After the above incident and then further raiding by the DEN, taking out a few GTT cargo ships in the DOM system of Coptuv, the DOM seemed to have been faced with a choice of stopping drinking their tea and doing something or just hoping it would go away. Instead they seem to have decided to abandon the whole idea of being an active affiliation and we have since folded. The lengths some people will go to not to have their elevenses disturbed is truly staggering. We asked the DOM for a statement on their new system rules to share with our readers but have received no replies.

    DOM positions share out

    Just as we were going to press news has come in of various DOM assets being given to other affiliations or sold. Hopefully we will have more on this story in the next issue of your favorite factual newsheet. Yes, that's us at the SSS.

    *** Affiliations ***


    AFT Association of Free Traders (54) - Marion Tweedy
    CIA Combined Intelligence Agency (64) - Laton CIA
    DNA Displaced Natives Asylum (66) - DNA people
    DTR Detinus Republic (58) - Morley Decker
    DEN Dewiek Elder Nation (67) - Urd
    DOM Dominion (57) – we believe the DOM are now inactive
    FCN Falconian Republic (70) - Bacran
    FEL Felini Tyranny (49) - Juris
    FLZ Flagritz Republic (47) - Kayxaer
    FET Frontier Exploration & Trade (56) - Cu Chulainn
    GRC Gracians (13) - HG1
    GTT Galactic Trade & Transport (52) - Xavier Fox
    GCE Garcia Enterprises (4) - Neil
    HEX Hexamon (23) - Ando
    IMP Imperial Services (51) - Jack Jones
    KRL Krell (30) - Namica
    KRT Krell of the Reverence Temple (37) - Kal Torak
    KST Kastor Kastorians (12) - Kastor
    MZC Mizuchi Combine (86) - Mizuchi
    MOH Mohache (73) - Listens
    MIC Mohache Independent Commune (76) - Sleeps with Dragons
    NLF Naplian Liberation Front (38) - NLFHQ
    RIP Regularly Involved in Piracy - Githyanki
    RRH Roy Robert Holdings (39) - Roy Roberts
    SMS Stellar Mining and Smelting (53) - MikhailM
    USN Ulian Stellar Nation (34) - Oeipus Prime
    WMB Wimble Nations (25) - zz

    * Leader MAY be inactive, affiliation may be active
    ** Affiliation has no leader but this is the only known contact

    NPC / FoC: ARC, CIV, CGT, FRE, HBO, HEF, IND, ISP, JCN, MEK, MRC, PIR, PRV, TCA, TRN, KAS

    Inactive: ANT, BHD, COD, HVE, IDC, RIP, RCF, SKW, TAG

    Deceased: CAL

    *** Submission ***

    By private message to The Editor or via Mica if you prefer to remain anonymous.
     
    user image


    ***** Inter Galactic News *****

    New pirate threat rocks Corward Arm.

    Several large pirate ships have been spotted in outer rings of Corward systems. Reports forwarded to us at the SSS allow us to exclusively tell readers that traders should keep their wits about them when moving through these areas.

    No existing pirate menace has yet claimed ownership.

    In a possibly unrelated event one of the FET cartel members claimed nothing was happening in the outer ring of Coptov shortly afterwards. But it could be that they are still trying to catch Empire backed pirates and have nothing to do with the new sightings.
     
    user image

    ***** Inter Galactic News *****


    DEN continue to shoot innocents

    The Dewiek have made themselves busy shooting at the peaceful and innocent traders of the SSL. Leader of Solar Spices and Liquors Mr TOAD has been vocal pointing out that the Beast-DEN are being totally unfair. News of a go-fund-me appeal are yet to surface though.

    This office is sure that it must have provided the DEN light relief after picking on the equally defenceless Felini. Word is that the DEN faced such an uphill struggle in these recent actions they had to take up Felini inter-breeding to provide some entertainment as the battle reports were rather boring.
     
    user image

    ***** Inter Galactic News *****

    Return of the LiQuans

    A close associate of the Baron LiQuan has been haunting the Corewards periphery and like the old Baron it is said he has a meklan connection. It's unclear whether he obtained his meklan nanites via the CIA but there are rumours that the DEN may be helping the Liquan relative in a bid to sow discontent in the Stellar Empire. Exactly why they would start in Corewards is unclear although with DEN allies, the DOM, having strong positions both in the Sol system and the old Harcorp systems of Harlong and Coptuv they may be the linking factor.


     
    user image

    ***** Inter Galactic News *****

    Meklan Unleashed on Mobile Bay

    Mad Dewiek scientist Dr Kala released a number of Meklan on the busy world of Mobile Bay in the Yank system. Thousands of civilians have been killed in what is treated by DEN warlords as an amusing practical joke. Rather than take any responsibility for their affiliation’s reckless behaviour, a DEN lord rumoured to be half-meklan himself quipped he would nuke the planet whilst another merely saw it as an opportunity to test some of his greener troops in combat. Surprisingly, the KAS planetary defence force was up to the job of repelling the insidious incursion. Questions remain whether further meklan are stored elsewhere on the planet and whether anybody will challenge the Dewiek’s lack of care for the lives of innocents. Probably not, given how even the mighty IMP are now cowering from a fight with the DEN (see inside this edition).


     
    user image

    ***** Inter Galactic News *****

    Who is behind the AFA?

    Following the large scale holiday attack by the AFA against the FET the question of who is behind the attacks has been raised once again. What is clear is that the AFA is using ships that were transferred from the GTT to the IMP. The organisation and expertise of the operation also reduces the pool of potential candidates. Few can go from commanding a handful of broadswords to half a thousand warships and significant army logistics without a long stint in one of the more combative affiliations. With the DEN’s allies the HEX in close relations with the FET and no recent history of animosity between the aliens and FET, at least since the departure of former one-eye big-bun Norozov, it would be a bizarre turn of events if they were behind these attacks. Frankly, there’s no point dancing around it. The IMP are clearly behind the AFA. The question is what can anybody do about this move of significant Imperial resources to a black-flag agency?


     

    Free Ship when you sign-up
    Complete missions for in game rewards
    Control everything, up to an entire empire
    Dedicated human moderators
    Player and Moderator driven plotlines
    Discover new worlds to explore, exploit & colonise
    Over 20 years of content development
    Persistent Browser-Based Game (PBBG)

    I’ve played on and off for approximately 10 years, over a 20 year spell. After some interesting debate on the in-game forum, I did wonder what, exactly, has kept drawing me back to the game, when for so many others I’ve generally lost interest after a few months.

    Ultimately, I think it is a combination of automation (that allows the game to handle thousands of positions to interact on a daily basis) coupled with Special Actions (that allow the story arc to develop in a way that could not be catered for by a set of predefined list of available orders).
    -Zigic