Phoenix
Phoenix: BSE
Phoenix at a Glance
Rulebook
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
Issue 32
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
user image
  Star Date: 221.22.5

user image

RAGNAROK BECKONS

user image

Assault on End Game

The ancient Architects have declared war on the Dewiek Elder Nation. The first sign of the conflict was subspace transmissions in a remote system in the Pocket Periphery. This followed reports that the ancient Ragnarok shipyards on Beacon were malfunctioning. In response, the Wolf Mother sent urgent orders to several Dewiek scout ships to patrol the End Game system.

The Konungr Smidamadr was the first to encounter the gigantic, “Planet Killer” class ARC ships. Measuring in at thirty-two hundred heavy hulls and armed with a hundred ARC plasma weapons, the ship was more like a mobile armed platform. It is certainly the largest vessel ever recorded. The scout ship was vaporised instantly.

user image
ARC Planet Killer dwarves largest DEN warships

 
user image
  Star Date: 221.11.4

user image

Caste Apart

The Flagritz Republic is (very nearly) no more. In its place, a single Hexamon and Flagritz power has arisen. The new Collective has absorbed much of the Flagritz holdings with only a handful of Clique-caste Flagritz systems choosing instead to align with the other Elder species, the Dewiek.

user image
Flagritz and Hexamon Hybrids - A hope for the Future?

 
user image
  Star Date: 221.3.3

user image

Meklanmania

Meklan scout ships continue to be seen around the Orion Spur periphery. These cyborg creatures in service of hidden ancient masters appear to be terrorising the Wimble Nation in particular. Despite public lamentations against the hardship of defending themselves, the Wimble leadership have not yet responded to our request for comment.

user image
Artist's impression of a Meklanised Wimble

However, Xavier Fox, CEO of Galactic Transport and Trade, did give us the following statement:

“We have engaged several Meklan ships, although currently the source has not been identified. GTT Directors have been running patrols and have engaged and destroyed numerous ships that have attacked outlying outposts belonging to different affiliations. The pattern of ships encountered leads us to believe there is a central source, but until that is found we would suggest any affiliation with assets in the area provide adequate defences.”

user image

Doomsday On Pause

At the site of the Thete anomaly, the Dewiek Nation has sent media sensation Sharon Aleman to the scene. Aleman, whose cybernetic enhancements allow her to directly interface with her ship’s sensor array, led her hardened crew into a dive of the outermost “edge” of the anomaly. After spending several days collecting and analysing data (mere minutes to the rest of us outside the anomaly), Aleman reported her shocking discoveries.

 
user image
  Star Date: 220.50.5

user image

Veil Lifted on Flagritz Home Space

As the Hellcadium ISR field continues to fluctuate, one of the newly exposed systems is Junista inside the previously hidden and inaccessible home periphery of the Flagritz Republic.

Over the past few weeks Flagritz Republic patrols and platforms have dealt with a number of scout ships from the Human Empire as the IMP wasted no time in exploiting this opportunity to poke around in their old enemy’s backyard. It is understood that at least one of these unarmed scouts was destroyed with no one willing to estimate how many more might be buzzing around.

Coincidentally, suspected IMP lackey, SSL TOAD, has also been overheard showing an obsessive interest in the Flagritz periphery. However, we have received no reports of this being anything other than his usual drug-fueled, barely decipherable mutterings at this stage.

Either way, this sudden, uninvited interest in the Flagritz Periphery has left the FLZ leadership muttering darkly about appropriate measures being taken. Defensive fleets and supporting structures are being deployed in the Junista system and beyond in expectation of further uninvited guests.

user image
When You stare into the Flagritz Periphery...

user image

Thete's Timey-Wimey Tease

Investigation into the Thete anomaly continued in the Dewiek Pocket Periphery. The anomaly was scanned from all angles by a number of the Dewiek Nation’s best sensor ships and officers. The data, collected over several weeks, was sent to one of the DEN’s most advanced scientific laboratories for analysis.

What they found will shock you!

 
user image
  Star Date: 220.45.1

user image

Perfidion Reached

Long speculated by theoretical Stellar Cartographers, Perfidion Reach finally opened in the last few weeks. Immediately, the Detinus Republic boldly staked a claim on the first accessible system, Hellcadium. Only time will tell the true value of this strategic move but their much-taunted bureaucracy may have finally proved its worth.

Early reports from scans of the system reveal a wildly fluctuating ISR field. Rumours suggest that at least one ship was destroyed as it was forced into an asteroid belt chasing a stable jump field attempting to exit the system. Casual travellers are warned away from the system at this time for their own safety. Leave it to skilled explorers and navigation officers.

user image
Mathematical model of Hellcadium ISR Field.

We spoke to Captain Zakiyah Ummahi via subspace link. Zakiyah led the first DEN expedition into the Perfidion Reach. "Spirits remain high but this is largely down to the extended R&R we were all forced to take immediately prior to jumping into this hole. Initial scouting reports show at least one planet with plenty of forests and grasslands which might help if we're going to be stuck here for Folkvar knows how long waiting for this damned ISR field to stabilise."

user image

Valhalla Stargate Reopens

Dewiek engineers and scientists have finally managed to re-enable Stargate Valgrind this week and the protective Exclusion Zone is to be lifted. If DEN investigators discovered who caused the gate to malfunction, or why, they were not willing to share it with us. Military sources, however, have announced a project to provide a significant boost to the already formidable defence platform in the stargate’s orbit.

 
user image

*** Inter Galactic News ***

Empire - DEN action grinds to a halt

After months of tension relations between the Empire and the Dewiek Nation, which rose to several large scale fleet actions ending in the DEN losing over 60 Direwolf warships in Solo, things appear to have moved from antagonistic to unfriendly. With the Solo system being a particular issue an agreement has been reached between the Wolf Mother of the DEN and Xavier Fox of the GTT. Since this things have become very quiet, not just because the shooting has stopped, but also because my reporters have been on their summer holidays.
 
News For Discerning Naplians!
---- Special Galactic Edition ----



(The Host sits at his desk as the studio lights dim, and a single spotlight bathes him in light. He looks straight into the camera and begins to speak: )

Host: Naambta!
Good Greetings, and welcome to the show.

This is News for Discerning Naplians, and i’m sure you are all showing much impatience to see this week’s Panel Discussion. We will be discussing religion with the Lady Ghadir of the Temple of Ya Zoon, renowned neo-naplian spiritualist Chairman TonTon, and a very special guest from our imperial neighbours, Bishop Samantha Porteus of the Brotherhood. But before we get to that...

(Looks demonstratively at his digital wrist watch. )

... it is time for a word from our sponsor.
 
******Empire Syndicated News Network (ESNN) ******

user image

Welcome to the latest version of ESNN, giving the news and views from the ESNN's reporter and news anchor, Ainsley Moore, making this the peripheries' most favourite unbiased publication in the known universe from our new home in the Heartland,

And so with the news from the last few weeks,
 
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.
     

    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