Download Nexus Turns and Ancillary Data
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.
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.
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.
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).
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.
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.
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.
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.
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 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.
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.
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.
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.
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.
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.
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.
Star Date: 221.3.3
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.
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.”
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.
Star Date: 220.50.5
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.
When You stare into the Flagritz Periphery...
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!
Star Date: 220.45.1
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.
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."
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.
*** 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: )
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) ******
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,
*** 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
***** 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.
***** 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.
***** 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
*** Submission ***
By private message to The Editor or via Mica if you prefer to remain anonymous.