|
|
|
Targeting – everything you need to know |
|
|
|
Targeting – everything you need to know
Targeting is simply the ability to designate and engage with a specified position.
This one word can cause untold frustration in the universe of Phoenix. It can be considered tantamount to ‘healthy and safety policy’ for its ability to derail an otherwise perfectly executed assault. It can also explain why your enemies can attack you in your systems even though you cannot attack them in theirs. It is a minefield created through the implementation of a few seemingly clear options.
There are two levels of targeting:
- Policy
- Target designation
Policy
Policy is maintained at the political level. This is where the movers and shakers of the affiliation determine their relationship to other factions, where they implement their charters and determine exclusion zones in regions of space that they own. When combined with civilisation level of a system and ownership they effectively set the theatres of potential conflict zones. Just because these policies allow for conflict under specific circumstances and in various locations, it does not mean that conflict will occur.
|
Target Designation
Target designation is handled on a position level. It is the setting of enemy, support and defend lists along with various combat options. Outside a potential conflict zone it makes no difference what lists are set to or which combat options have been taken, there will be no conflict.
So far everything seems pretty clear – just two things are needed to stomp somebody, a policy that states who can be stomped and where along with a bunch of positions listing enemy targets.
Setting Affiliation Policy
Each affiliation represents a faction with a set of ideologies that in the game mechanics determines how they can behave with respect to setting their relation to other affiliations.
N.B. there are some factions that have opted out of the relations mechanics, e.g. pirates. We will ignore these for the moment and concentrate on the vast majority of affiliations that are bound by the relations mechanics.
System Civilisation Level
Each system in the game has a civilisation level, from Darkspace with increasing levels of colonisation up to Core (Darkspace, Borderland, Developing and Core). This refers to the degree to which the system has been colonised or in other ways brought up to a recognised level of civilisation. The vast majority of systems in the Peripheries are Darkspace – lawless frontiers where even neutral factions can theoretically attack each other, though of course there may be repercussions throughout the rest of the Peripheries if conflicts start to escalate.
On nexus, any system without a civilisation indicator is considered Darkspace.
Contested systems are treated as Darkspace.
Relations
There are 5 levels of relationship with increasing levels of antipathy:
- Allied – we like them so much that their enemies are ours.
- Friendly – we like them so much we will defend them.
- Neutral (default) – live and let live for the most part though in the dark places (Darkspace) of the universe and if needs must…
- Antagonistic – we will respect the neutrality of civilised systems but not beyond (Developing and Core).
- Hostile – we will only be respect neutrality in the most civilised systems (Core).
- War – Anywhere is fair game.
While each attitude is from the perspective of the affiliation, the relationship defaults to the most hostile.
Example
Wimble Nation is neutral to the Flagritz Empire, while the Flagritz Empire is hostile to the Wimble Nation. As such the mutual relationship is hostile.
On Nexus this will equate to a solid coloured box (were the relationship is mutual) or a coloured box with a different colour border. Mouseover will give details of the relationship.
Reciprocation
As relations default to most hostile, benefits of Allied and Friendly only work if reciprocated.
Example
Wimble Nation is allied to the AFT while the AFT are friendly to the Wimble Nation as such the relationship defaults to friendly, so no supporting each other enemies of the AFT cannot use this as a means of attacking the Wimble Nation.
Changing Relationship Level 1
A relation to another affiliation can change by a specific number of levels (Allied to Friendly is 1 level, while Friendly to Antagonistic is 4 levels) and can issue a change only once per relation to a specific affiliation within a period of time in accordance with their profile.
Example
Detinus Republic and Garcia Enterprises both have the profile:
5 days, 1 level
If they are both neutral to each other and the Garcia wish to become allied to the Detinus Republic, it will take them 10 days after issuing the command to change from Neutral to Friendly (day 5 – Friendly, day 10 – Allied). If sometime in the future Garcia Enterprises then wish to go to war with the Republic, it will take them a minimum of 25 days (from Allied to Friendly 5days after the level, then 4 levels at 5 days each).
The table below is an extract from a political position with access to setting relations, indicating the current relations to various affiliations.
Asynchronous Relationship Changes
How fast an affiliation can change its relationship with another faction is based on the principle of least time. This means that where the profiles of two affiliations differ, the mechanic defaults to the fastest profile options.
Example
Confederate Forces has the profile:
0 days, 1 level
This means that with respect to each other, both the Detinus Republic and the Confederate Forces can change their relation by 1 level, i.e. they do not need to give 5 days notice. By 0 days, it means that there is no waiting period for the first level change, i.e. at 6.35am the Republic decide to change their relation to the Confederate Forces from Antagonistic to War. As download of turns is at 6.50am that same day, they can then launch an assault in a Core star system.
Minimum Period of 5 days between changes
Irrespective of the setting, there is always a minimum of 5 days between changes. As such even though in the above example the Republic took advantage of the Confederate Forces 0 days waiting for a level change, they cannot revert back to Hostile from War for a further 5 days preventing affiliations changing their hostility level for the purpose of a single day’s engagement.
Control of Hostility
An affiliation with change set at 1 level has the advantage when dealing with diametrically opposite affiliation with 6 level changes in that it can still change by up to 6 levels. As such the ability to change 6 levels in one go is only really beneficial if the affiliation is aggressive or fickle in its attitudes, it confers not strategic advantage over those that have only 1 level change.
As the relation state between two affiliations defaults to the most hostile where one side is less hostile than the other, they have effectively conceded control of the relationship to the more hostile affiliation. This is because the more hostile affiliation can increase or decrease their hostility in order to open new areas for attack or deny areas to the less hostile faction.
Example
The Dewiek Elder Nation declares war on the Confederate Forces and proceeds to engage Confederate positions in Core star systems for a week. The Confederate Forces however remain neutral to the Dewiek Elder Nation. Hearing that the Confederate Forces (and their allies) are about to send in the cavalry, the Dewiek Elder Nation returns their relationship to neutral. The cavalry arrive but as both sides are now formally at peace there is no battle. It was either an oversight that the Confederacy remained neutral or that they in fact wanted peace and the arrival of the peacekeeping force was a means of forcing the Nation’s hand.
Benefits to Remaining Neutral
Primarily it is about sending the signal that you do actually want peace which means violence ends as soon as they reduce their aggression. If an affiliation has no intention of actively seeking to engage in combat, then there is absolutely no point becoming more hostile.
Being anything other than neutral requires the political machine to be oiled with stellars, either continuously telling affiliation members what great dudes they are or what the latest atrocity instigated by the enemy is. Unless there is a purpose such as active mutual defence (rather than lip service and nobody turns up in times of need) or there is an active pursuit of enemies, then any relationship other than neutral is a waste of stellars.
It forces the opposition to foot the bill while still giving the neutral affiliation all the same theatre of conflict. That said, it is not a large bill, even for war (though being at war with a dozen affiliations is going to get costly).
Localised Policy
So far only relations has been covered, this is policy at an affiliation level and applies across the entire Peripheries. More often than not however this is too blunt an instrument especially when dealing with neutral factions. In these circumstances it is desirable to limit potential hostility to specific locations. While defined as system enemy lists and exclusion zones, they are handled by Charters, allowing the current system claimant to apply any number of charters within the system.
Charters and Exclusion Zones
A charter consists of a title, a body of declaration text and can include a list of enemies.
Example:
Title: Get orf my land
Declaration: We will shoot everyone we find here.
Enemy List: Everyone
This charter can then be applied to locations claimed by the affiliation creating the charter. There are two options, application of the charter to the entire system or to a subsection (or subsections) of the system via exclusion zones.
Exclusion zones can be set to cover:
- Any quad
- Any ring
- Any orbital quad
- Any world
Example
In the above example, the affiliation claims the system ‘Enches’. For some reason they do not like the AFT so create a charter to be added to the system:
Title: No AFT Thanks
Declaration: Stay out or be attacked.
Enemy List: AFT
Within the system is a rather nice world (Nackas) with a few thorlium deposits that they want to preserve for themselves. As such they decide to associate the ‘Get orf My Land’ charter with Nackas. Together this gives them ability to attack anyone on the surface or in orbit of Nackas using the exclusion zone options and the AFT with the entire system.
A few weeks later they that the moon of Nackas also contains quite a lot of minerals and start to get a little grumpy about the number of foreign exploration ships in the system. They decide to extend the charter, applying it to the other moons and the orbital quadrant of Nackas and its moons.
Creating and moderating relations, charters and exclusion zones can be achieved by the political of the affiliation with relations access on Nexus though the use of some simple dropdown menus and text boxes.
Target designation
All that has been achieved so far is setting potential theatres of conflict. In order for an actual battle to occur, within one of these theatres, positions with an enemy list have to be present and have to have the enemy list activated. Activation is normally through scanning a position which can be achieved through the scan location order or more commonly simply by moving into a location, such as entering orbit or moving from one orbital quad into another or by scanning a position passing by. Changing a standing order such as adding a position to an enemy list on its own does not count as modifying the list does not call a scan either active or passive. Changing policy also does not initiate a combat check.
Example
A fleet of GTT ships with DEN on their enemy list is in GTT claimed system. The GTT and DEN are mutually neutral and the DEN are not on the system enemy list. Should a DEN fleet with GTT on the enemy list stop at the location of the GTT fleet, there will be no battle. Even if the GTT then add the DEN to the system enemy list, there will still be no battle until either side then initiates a scan, i.e. actively looking to engage the enemy. Until the point where there has been a scan, the location will not be indicated as a battle location. As such any number of positions with support or defend for the DEN or GTT can move through the location and will not be stopped. Support and defend checks will only cause a position to stop if it has flagged ‘on patrol’ and there is a battle flagged at the location being passed through.
If a battle has been triggered, there will be a full battle check at the end of the main processing run (before special actions are processed). This will check all positions in the location, which in the case of a battle check associated with a world, will also check all positions in orbit, on the surface of the world and even docked with bases on the surface of the world. This check will determine viable targets from the perspective of the positions present.
A viable target can be defined through the following parameters:
- Specific position number on an enemy list
- Belonging to a specified affiliation on an enemy list
- Defending a specified affiliation that is actively involved in combat
- Supporting a specified affiliation that is actively involved in combat
- Returning fire against a specific position
N.B. in all cases the lists need to be active, i.e. supported by policy above. When a position is in a location that prevents any part of its enemy list from being active, the corresponding entry will be followed by a *.
Viable targets are flagged on the battle printout as being Enemy Targets, Support Targets and Defend Targets, defining they criteria by which they qualified as a viable target. The method by which targets are generated is as follows:
- All positions in the location are listed.
- All active enemy lists are checked and truncated down according to positions present (ground enemy lists only extend from starport to sector of the position, beyond uses space enemy lists). These form the Enemy Targets list for the individual positions, i.e. irrelevant positions are pared away.
- Positions supporting entire affiliations are given Support Targets equating to the enemy lists (affiliations only) from all the positions of the affiliation being supported that are present, i.e. if anyone the position is supporting is attacking entire affiliations, it will too.
- Positions supporting specific positions are given Support Targets equating to the entire enemy list, including individual enemies present of the specific positions, i.e. if the entire (valid) enemy list of the position being supported is used.
- Positions defending affiliations will be given Defend Targets based on affiliation with the affiliation being defended on their enemy list, i.e. only affiliations will appear on the Defend Targets.
- Positions defending positions will be given Defend Targets based on the positions with the positions being defended on their enemy list, i.e. specific positions may appear on the Defend Targets.
- Specific positions are then engaged based on combat options and weighted by average chance where there are still multiple potential targets.
Example
An AFT ship has the GTT on its enemy list. It enters orbit of a world with a CNF base and scans some GTT ships present. Policy is such that the AFT does not trigger a battle with GTT ships outside of a few exclusion zones in AFT controlled systems. In this orbit the enemy list will state GTT* indicating that this is currently inactive.
Later in the week, a pirate ship enters the same orbit which then triggers a battle. Despite there being a battle in this location the AFT enemy list is not active and as such does not engage the GTT ships. In such an event it may well be the case that the AFT also engages the pirate. This does not however mean that the AFT is in any way supporting or defending the GTT, merely attacking a mutual enemy.
Extending the Example
There are situations where despite an enemy list being flagged as inactive, the position may still be bright into combat through other means.
If the AFT were friendly to the DTR and the DTR were at war with the GTT it would mean that even though the AFT could not directly attack the GTT, should a DTR vessel enter orbit and be attacked by the GTT, should the AFT have defend DTR on their list, they will become involved.
If the AFT were allied to the DTR, there would be no * after GTT on their enemy list and they would immediately attack the GTT, even though DTR were not present as the DTR’s hostility to the GTT becomes the AFT’s through the relations mechanics.
Support and Defence do not chain
This means you will only defend and support where the positions/affiliations on the support or defend list are the primary focus of the battle.
Example
In orbit of a world there are DEN, AFT, GTT and FEL ships.
AFT have the FEL on their defend lists (mutual friends).
FEL have DEN on their defend lists (mutual friends).
DEN have GTT on their enemy lists (at war with GTT).
GTT have DEN on their enemy lists (at war with DEN).
DEN and GTT are therefore mutually attacking.
The FEL are defending the DEN and therefore have GTT on their Defend Target list.
The FEL are not on GTT Target lists though may be targeted through returning fire.
The AFT do not attack the GTT because the FEL is only being attacked by the GTT because the FEL is defending the DEN who are primary target of the GTT, i.e. the FEL are not active targets.
This can lead to some curious situations where there is inconsistency across a battle group. In the above example, if the AFT were also friendly with DEN but only half the AFT ships had all DEN on their defend list, the ships defending DEN would become involved. Even if the entire AFT battle group had defend AFT, those without defend DEN would not get involved.
Disengaging and Conflict
Under normal circumstances a battle will continue until there are no targets for the remaining positions to attack. There are means of disengaging, such as moving away from the battle location or getting all parties to issue orders to clear enemy lists and unlock targets.
There is however a second option through changing policy. Before combat is continued on each day, there is a check to determine if there are viable targets (the same test as on the first day of combat). A change in policy can be sufficient to call a cease fire. It is therefore imperative that those on the currently ‘winning’ side know that a change in policy by the opposition is not going to wreck their plan.
Example
The IMP has GCE on a system enemy list for Capellan but is currently neutral to the GCE. This means that the GCE can attack the IMP and their allies in Capellan along with any base that is supporting the imperial system claim for Capellan. The GCE take advantage of this by launching a ground assault against a GTT starbase in the system.
The IMP can remove the GCE from the system enemy list, which will call a cease fire even if the battle has been raging for days and the GCE are within a hair’s breadth of capturing it.
While this may seem odd, it is perfectly correct. If the GCE was seeking to capture the base, the system claim should have first been contested or they should have raised their hostility towards the GTT so as to ensure that there would be no risk of changes to policy affecting their assault.
This is a good reason for using flags of convenience (see below) – mercenaries for example are perfect for attacking positions in otherwise neutral developing systems.
N.B. Positions in combat cannot be transferred in order to prevent abuse (such as transferring them to a neutral affiliation).
Example
An AFT ship is defending a DTR ship against a squadron of GTT ships due to their mutual friendship (not allied) despite being neutral to the GTT and in a developing system claimed by the GCE. The GTT and DTR can fight because they are currently at war. While the DTR ship exists, the AFT will continue to attack the GTT ships. Once the DTR ship has been destroyed, the AFT and GTT ships will disengage before continuing combat on the next day.
Contesting a System
If there is a counter claim of sufficient size to contest system ownership the system will be treated as Darkspace, inasmuch as anybody can then attack anybody as per normal relations in Darkspace, i.e. affiliations that are neutral to each other can attack each other if they are flagged as enemies on their enemy lists. Affiliations that are allied and friendly cannot however attack each other.
Special Circumstances
An unusual affiliation profile option exists that if opted for allows the affiliation to attack friends and allies under specific circumstances, such as exclusion zones, system enemy lists and registered outposts. Such an option may have been taken by a policing faction within an area of space open to multiple factions. Such a police force may from time to time have to deal with intransigent residents even though they are allies or at least have the capability of doing so, even if this has never actually happened.
Flags of Convenience
Player owned and where profile allows it, affiliation owned positions position can carry a flag of convenience. These are Free Lance (FRE), Privateer (PRV), Mercenary (MRC) or Pirate (PIR). While carrying the flag they are subjected to the profile of the appropriate flag affiliation. The profiles span the range from honest trader to scurvy dog which is reflected in the case of PRV, MRC and PIR having profiles that have partially or even totally opted out of relations mechanics (as can be seen in the Combat Status page Game>Affiliations) www.phoenixbse.com/index.php?a=game&sa=affs&ca=combat).
Officers
The actual adding of positions and affiliations to lists requires somebody in charge willing to take the flak – this is a naval officer. Without one all lists will be dropped and under most circumstances, the position will attempt to leave combat. There are some circumstances where the position will stay for combat such as when returning fire, but it is strongly advised not to base any sort of strategy on this mechanic.
Summary
Targeting, that is deciding who to kick and going out and kicking, normally requires two things, the target on the enemy list and some sort of political thumbs up that activates it. With friends and allies this expands to more options while in Darkspace it is pretty much a free for all.
There are nuances based on the plethora of settings and locations that can generate circumstances to watch out for, such as defend and support lists not chaining across multiple affiliations.
So, the bottom line is ensuring affiliation policy and charters are up to date and bear in mind how others can exploit your attitude to them and how your allies can leave you vulnerable.
The Game>Affiliations pages are very useful in showing your relationship to other affiliations but also the true combat status as being neutral to pirates for example does not count for anything.
Looking at individual systems is worthwhile if only to check if there are any charters or exclusion zones to be aware of. Also take note of the civilisation level of system. You may be neutral to another affiliation but if its darkspace, your positions may be fair game.
1While writing this article, a bug was discovered on Nexus that can sometimes give incorrect waiting periods after issuing a relationship change. This is purely a reporting issue as the actual changes are carried out by the Phoenix engine at the appropriate time. This bug will be fixed ASAP.
|
| |
|
|
|
|
PayPal.Me/creditKJCaccount
Don't forget to include your account number in the message. |
|
|
*** Inter Galactic News ***
Solo claim swings back and forth
The situation in Solo appears to be getting even more heated. First the NHS dropped 600,000 troops to contest the system and then the DTR answered with enough troops of their own to trump the NHS claim. The NHS found yet more troops, taking the contesting claim up to 750,000 and once again the DTR answered, bringing Solo back under DTR control. Now the NHS have had a look down the back of the sofa and found yet more troops, taking the contesting claim to a massive 900,000 trained troops. We wait to see if the DTR have an answer to this. We can only guess where all these troops are coming from, but what is clear is that the established affiliations clearly have far larger armies than many thought.
|
|
|
*** Inter Galactic News ***
NHS attempt to claim Solo away from DTR
In a shock move the NHS have contested the Solo claim with a huge garrison of 600,000 trained troops. In a move that nobody saw coming, especially as it was unknown the NHS had such a large force of troops to draw upon, the NHS seem to be provoking a response from the DTR. Currently there has been no word from the DTR in how they are going to deal with this claim jumping, although rumours are that they are pretending the Solo claim doesn't really matter to them and so action is unlikely. However this may be a smokescreen and we may yet see the DTR's powerful fleet cause havoc in the system of Solo, which has for a long time been an important junction and fought over by many different factions.
DNA Chairman TonTon resigns
The following communication has been leaked from the DNA to the GTT's PD.
Greetings CEO Fox.
It regrets me to have to inform to you that the DNA nation state will be renouncing its claim on Aladdin system following a ceremony planet side, shortly.
However, it gives me great pleasure to have to inform you that these ceremonies are being planned by Vladimir Tavikovitch, the South Road Traffic Coordinator. He is also responsible for all DNA and .ore. assets in the Outer Naplian (Capellan) periphery so if there are any further issues, please take it up with him.
For any and all other matters, please forward your request directly to the DNA directorate services at NexusID: DNA people.
The Foreign Ministry objects one last time to your illegal claim jump of Aladdin, but we realise it is time to de-escalate.
Normally i would sign off with Naambta, but doing so would be hypocritical. Let me say good riddance instead.
I hereby resign in protest!
Chairman TonTon,
Foreign Minister, DNA
cc: Directorate Services personnel coordinator - !urgent resignation!
DTR threaten WMB with fines for multiple breaches of DTR Law
Lady Sylvansight of the DTR has issued a fine of 1,000,000 stellars to the Wimbles for multiple breaches of DTR Penal and Territorial Law. This seems a very brave move of the DTR to risk upsetting the huge and warlike WMB when they also have the rival NHS Solo system claim to deal with. No word has been recieved yet that the Wimbles are going to pay, but if the formidable WMB warfleet is seen heading for the DTR home systems we will know what their thought are on the matter. The DTR and WMB fleets going head to head would be a sight to behold.
*** Affiliations ***
AFT Association of Free Traders (54) - Marion Tweedy
BLG Bolg Organisation (22) - Akhenaten
CIA Combined Intelligence Agency (64) - Laton CIA
DNA Displaced Natives Asylum (66) - DNA people
DTR Detinus Republic (58) - Morley Decker
DWK Dewiek Packs (19) - <Unknown>
FCN Falconian Republic (70) – Graspien
FEL Felini Tyranny (49) - Kr'Shan
FLZ Flagritz Republic (47) - Kayxaer
FET Frontier Exploration & Trade (56) - Cu Chulainn
GTT Galactic Trade & Transport (52) - Xavier Fox
HEX Hexamon (23) - Tranquility
KRL Krell (30) - Namica
KRT Krell of the Reverence Temple (37) - Cyn
KST Kastor Kastorians (12) - Kastor
MOH Mohache (73) – Listens
NHS Noble Houses (41) – Roy Roberts
NLF Naplian Liberation Front (38) - NLFHQ
SMS Stellar Mining and Smelting (53) - MikhailM
WMB Wimble Nations (25) - zz
* Leader MAY be inactive, affiliation may be active
** Only known contact, please update us if this is incorrect.
NPC / FoC: ARC, CIV, CGT, FRE, HBO, HEF, IND, ISP, JCN, MEK, MRC, PIR, PRV, TCA, TRN, KAS
Inactive: ANT, COD, BHD, DEN, DOM, GCE, HVE, IDC, IMP, RIP, RCF, SKW, TAG,
*** Submissions ***
By private message to The Editor or via Mica if you prefer to remain anonymous. |
|
|
*** Inter Galactic News ***
DNA and GTT clash over Aladdin system claim while Pirates look on.
The GTT have this week launched an attack on the DNA outpost in Aladdin, in what appears to be little more than a turkey shoot. Around 100,000 GTT Naplian Startroopers attacked the DNA position to remove the rival system claim. Reports indicate the DNA garrison were taken by surprise and lost control of the base in the first few hours of the fighting. The base has since been reflagged from [Free Naplian Capital] Peaceful Protest to [Loyal Naplian Capital] DNA claim Ended so it's fair to say there was a clear message being sent by the GTT. We have been waiting for the DNA leadership to comment but so far they have been unusually silent. No doubt when they have crawled out from under their desks they will have something to say on the matter.
While this attack was going on several pirate ships were also seen in Aladdin, according to the GTT in what may be true or may be a diversion, with reports of a pirate GP and scout being destroyed while a 150HH pirate warship slipped away and escaped from incoming anti-pirate patrols.
Secret meeting of the EEM
A recent communication intercepted by one of our top reporters today made us aware of a meeting of the EEM. This is underway in a top secret location called Black Pool, which sounds suspiciously like the lair of a pirate band. After pulling in many favours, we were able to identify some of the attending members. On the bases that they won't be named we were able to find out some slight information of the subjects to be discussed at the meeting and one thing is for certain, there could be huge impacts to the lives of everybody living in the galaxy. Details to follow. When the shadowy figures of the EEM come together with the top political players in a pirate base the possibilities are endless!
You are never more than 6 systems from a RAT 🐀
A new saying has arisen in the bars and spaceport of starbases throughout the many peripheries; you are never more than 6 systems from a RAT.
It is understood that this saying originated in Yank and spread by trade vessels to peripheries far and wide. Many starbases have heightened their security and added additional sensors and locks to various entry points including foul and grey water outfalls. Beer and drug stocks are undergoing increased proofing to avoid the critters gaining entry and consuming the stockpiles.
Will this present as a new plague of proportions never before seen or is this some simple urban myth being spread for the amusement of some mischievous entity? Who knows, but to be certain... check the shadows.
|
|
|
This year we will again be returning to the Briardene Hotel. They were welcoming, the bar didn't run out of beer pre-covid and there was room for quiet chats. Along with Wetherspoons there is the Victoria just down the road (Sam Smiths - last time beer was around 2 shillings per pint and a full round was less than £10).
Mostly drinking beer and talking toot though we have a good few things on the agenda.
Bookings are done directly with the hotel. Book by phone and say that you are with KJC Games
Briardene Hotel
Telephone: +44(0)1253 338300
All staff should be able to deal with the booking but if there are any problems ask for Tracy (manager) as she dealt with all our foibles in previous years. |
|
|
*** Inter Galactic News ***
Dog days are over
With the fall of the DEN and the implosion of their home territory as the AFT, DTR and GTT moved in, it was unlikely the Dewiek would rise again. The DWP gave the species a little hope with the Dewiek Pocket Periphery kept under lock and key. But news has reached us of the AFT's penetration of this private area of space that's been locked down. With a base and claim in one of the three visible systems it seems that the end of the Dewiek is near. A once noble and aggressive race, determined to make an impact on the galaxy is now little more than a species that lives under the command of others. A sad end to a once powerful species that used to control a significant part of known space.
Pirate activity continues
Yet more reports of pirate activity have been received, one from the WMB, losing a freighter in Solo and another from the FET who reported they had engaged and hit the attacking pirate ship with several weapons before it managed to make off with it's prize. Hopefully the pirate ship took significant damage and will now be out of action for some time. The Corewards periphery seems to have been plagued with pirates recently and many travellers would welcome a break from attacks.
MEK incursion into Corewards
The FET and GTT have mounted a joint venture into Nog-Kesri to tackle a MEK force. It isn't known where they have come from, with the only other MEK ships seen so far being located in the Orion Spur. The lack of a known link between where they have appeared in Corewards and the Orion Spur has caused some concern among planetary populations as who knows where they could turn up next! Fortunately the combined FET/GTT task force dealt the MEK a heavy blow and the threat has been eradicated. But we all know this is unlikely to be the last we hear of the MEK in Corwards and we would encourage ship captains to keep a keen eye on thier sensor screens when travelling near Nog-Kesri.
|
|
|
*** Inter Galactic News ***
CIA freighter fights off overwhelming pirate forces
Fin Saine media broadcast, What is Hot in the galaxy?!?!
MEKlan forces attack in Corewards Arm
|
|
|
*** Inter Galactic News ***
Aladdin faces ongoing DNA/GTT tension
The tensions between the DNA and GTT in the Coptuv system recently spilled over into the DNA system of Aladdin. A significant party of GTT ground troops has reinforced one of their bases in the system and claimed it, forcing the system claim into turmoil as the DNA finds itself under threat of losing the system. With the DNA chairman asking for help, several affiliations have been seen sending ships to evacuate any in the local population that want to escape the GTT. But so far not a shot has been fired and despite the AFT, FEL and DTR assistance no reisistance to the claim jump has been encountered so far. It remains to be seen if the DNA and it's friends will scatter before this hostile take over or put in a last minute counter claim to thwart GTT intentions.
Increasing pirate activity
Recent reports indicate a new surge in pirate attacks with the AFT and GTT reporting ships lost. Knowing how some don't like to advertise losses we wouldn't be surprised if this is the tip of the iceberg. Reports passed to us show the ship PIR Scavenger running ID 43174 and another ship of the same name running ID 68668 have both been in action with successful boarding attempts. It's unknown whether these are seperate ships or the same ship reregistered, but our information suggests that it would be hard for these pirates to cover the space where these attacks happened with just one ship. One thing is for sure, be on your guard as open space is not as safe as it once was.
GCE ships loitering in deep space
After the fall of the GCE and a lot of their assets being shared or purchased it was thought that the affiliation was no more. Yet deep space scans indicate that there is still a significant number of GCE warships holding station in deep space between Coptuv and Yank on the transport route into the Corwards Arm. Nobody knows what these ships are up to and why they are still flagged GCE, but our best guess is that are captains either awaiting new orders or owners after the fall of the GCE command structure.
*** Affiliations ***
AFT Association of Free Traders (54) - Marion Tweedy
BLG Bolg Organisation (22) - Akhenaten
BHD Brotherhood (63) - de Molay
CIA Combined Intelligence Agency (64) - Laton CIA
DNA Displaced Natives Asylum (66) - DNA people
DTR Detinus Republic (58) - Morley Decker
DWK Dewiek Packs (19) - <Unknown>
FCN Falconian Republic (70) – Graspien
FEL Felini Tyranny (49) - Kr'Shan
FLZ Flagritz Republic (47) - Kayxaer
FET Frontier Exploration & Trade (56) - Cu Chulainn
GTT Galactic Trade & Transport (52) - Xavier Fox
HEX Hexamon (23) - Tranquility
KRL Krell (30) - Namica
KRT Krell of the Reverence Temple (37) - Cyn
KST Kastor Kastorians (12) - Kastor
MOH Mohache (73) – Listens
NHS Noble Houses (41) – Roy Roberts
NLF Naplian Liberation Front (38) - NLFHQ
SMS Stellar Mining and Smelting (53) - MikhailM
WMB Wimble Nations (25) - zz
* Leader MAY be inactive, affiliation may be active
** Only known contact, please update us if this is incorrect.
NPC / FoC: ARC, CIV, CGT, FRE, HBO, HEF, IND, ISP, JCN, MEK, MRC, PIR, PRV, TCA, TRN, KAS
Inactive: ANT, COD, DEN, DOM, GCE, HVE, IDC, IMP, RIP, RCF, SKW, TAG,
*** Submissions ***
By private message to The Editor or via Mica if you prefer to remain anonymous. |
|
|
*** Inter Galactic News ***
Tension in the Corewards Arm
With the DNA obtaining several ex-GCE bases in the Coreward Arm it has found itself in the middle of an asset grab of serious proportions and aggression. Our reporters witnessed several GTT troop carriers heading for the Corewards system as the DNA published information suggesting they were accidental owners of the system and that the assets were to be moved on. As the GTT ships started to arrive the bases were quickly passed to the CIA, thus thwarting the GTT intentions as they were hardly likely to start dropping troops on their allies bases. This shrew move by the DNA seems to have calmed matters in the Coreward arm temporarily, although the shift in relations between the GTT and DNA has taken a negative turn. When asked what their next move might be the GTT refused to comment.
GCE collapse
The GCE are no more, save for some scattered light freighters. The affiliation which enjoyed a sharp rise and profiltable relations with many has ceased trading. Rumors point to the GTT buying up GCE assets before stripping the rival corporation of anything of value. Although our reporters at the SSS have been quick to point out that any GCE assets not in GTT systems have been taken over by both the DNA and FET. So it seems many different affiliations were able to profit from this development including a new group called the HSH who appear to have taken over the GCE war fleet. No doubt many in the peripheries will be watching with interest where these ships are used, who the HSH are and how they were able to get thier hands on so many warships so quickly.
Secudus trials
In the Cluster Secudus has continued his trials, claiming to root out terrorists working against the Empire. With tends of thousands of beings being sent to the camps or worse. There is no sign of these actions stopping as the NHS clamp down on the locals and bring them under the harsh control of the Empire.
*** Affiliations ***
AFT Association of Free Traders (54) - Marion Tweedy
BLG Bolg Organisation (22) - Akhenaten
BHD Brotherhood (63) - de Molay
CIA Combined Intelligence Agency (64) - Laton CIA
DNA Displaced Natives Asylum (66) - DNA people
DTR Detinus Republic (58) - Morley Decker
DWK Dewiek Packs (19) - <Unknown>
FCN Falconian Republic (70) – <Unknown>
FEL Felini Tyranny (49) - Juris
FLZ Flagritz Republic (47) - Kayxaer
FET Frontier Exploration & Trade (56) - Cu Chulainn
GTT Galactic Trade & Transport (52) - Xavier Fox
HEX Hexamon (23) - Tranquility
KRL Krell (30) - Namica
KRT Krell of the Reverence Temple (37) - Cyn
KST Kastor Kastorians (12) - Kastor
MOH Mohache (73) – Listens
NHS Noble Houses (41) – Roy Roberts
NLF Naplian Liberation Front (38) - NLFHQ
SMS Stellar Mining and Smelting (53) - MikhailM
WMB Wimble Nations (25) - zz
* Leader MAY be inactive, affiliation may be active
** Only known contact, please update us if this is incorrect.
NPC / FoC: ARC, CIV, CGT, FRE, HBO, HEF, IND, ISP, JCN, MEK, MRC, PIR, PRV, TCA, TRN, KAS
Inactive: ANT, COD, DEN, DOM, GCE, HVE, IDC, IMP, RIP, RCF, SKW, TAG,
*** Submissions ***
By private message to The Editor or via Mica if you prefer to remain anonymous. |
|
|
******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 and most reliable unbiased publication in the known universe from our home in the Heartland,
And so with the news from the last couple of weeks,
Cluster War! DNA Gather Fruit
|
|
