Reference Listing- Dispatched Units and Dates of Dispatch, referencing activation as Year 0:
-Year +1:
Colonies to all systems within 50 light years (316 known)
Copies of main unit to 1000 identified distant galaxies
Probes to all Tshpath systems (4 known).
-Year +50:
Probes to systems all inhabited systems (62 known) as information-gatherers.
Probes with copies, Tellech, offer of Dyson Sphere creation to all Tellech systems (9 known).
-Year +152:
Colony ships for all systems within 80 light years (up to 689)
Colony ships to 10 systems (~30-290 LY) due to black holes, pulsars, or neutron stars observed within those systems
"Asteroid" weapons to all known Yewren worlds by obscured vectors (11 systems).
Humans to all human-controlled systems (8 known) as ambassadors
-Year +239:
All fleets within 20 light years of system 622 (Tshpath) ordered to begin military buildup, with a minimum of double standard military production.
War fleet dispatched to system 685 (Tshpath).
Boarding fleet dispatched to intercept 0.4c fleet en route from system 685 (Tshpath).
Asteroid-disguised electronic warfare squadrons dispatched to locations outside systems controlled by Yewren, Ourn (132 known).
Order to probe previously dispatched to Twelve to offer research alliance.
Actions undertaken in year +374:
-Settlement of all systems within a 150 light year radius (1685 known) ordered, except those within five light years of an existing civilization.
-Diplomatic high AIs dispatched to all known sapients except the Ourn, Tellech, and Tshpath.
-Fleets dispatched to wait in space between your controlled systems for orders.
-Fleet constructed and dispatched to human space.
-Fleet constructed and dispatched to Ti space.
-Three fleets dispatched to Gen space.
-Fleets dispatched to every planet in Ourn space (41 systems).
Actions taken in the year +430:
-Dyson spheres ordered around planets 000-020.
Actions enqueued for the year +530:
-Pending...

Observations of Existing Factions:
-You [~0-160 LY, 729 systems (10 shared with Tellech, 1 shared with Gen)]
-Gen (biologicals) [~30 LY, 1 system (1 shared with you)]
-Tellech (uploads, harmless) at [~0-210 LY Southwest, 10 systems (10 shared with you)]
-Reten (biologicals, harmless, slow tech) at [~130 LY West, 1 system]
-Ti (biologicals, harmless) at [~160 LY West, 8 systems]
-Yewren (biologicals, expansionistic, fast tech) at [~130-180 LY South, 308 systems (16 shared with Unidentified 2)]
-Unidentified 2 at [~170-180 LY South, 16 systems (16 shared with Yewren)]
-Humans (biologicals) at [~180 LY East, 20 systems]
-Ourn (AIs, aggressive, genocidal, fast tech) at [~175-200 LY South, 42 systems]
-Gen Fu (biologicals, harmless) at [~200 LY East, 8 systems]
-Unidentified 3 at [~250 LY Northeast, 1 system]
-Soou (biologicals, expansionistic) at [~260-300 LY West, 666 systems]
-Mnemo (uploads) at [~280 LY Southeast, 6 systems]
-Twelve (AIs, fast tech) at [~310 LY North, 32 systems]
-Unidentified 5 at [~310 LY East, 6 systems]
-Unidentified 6 at [~320 LY East, 1 system]
-Unidentified 7 at [~350 LY South, 55 systems]


Your strength and rate of expansion are largely unrivaled in space known to you. How should you expand next?

Greetings, Friend CPU.

Query:
Were scout or diplomacy probes ever sent to unidentified species 5, 6, and 7?

If not, please add to queue.

Query: Status of hacking attempts on the Ourn.

Query: What type of colonization protocol do the Soou use and what is their ship architecture?

It is good to be back online, Friend CPU.
Query: As I recall, the 'asteroids' aimed at Yerwen systems were ordered to avoid collision if drone diplomacy proved successful. Have weapons strikes been confirmed on Yerwhen systems or not yet?

>Query: Were scout or diplomacy probes ever sent to unidentified species 5, 6, and 7?
No.

>If not, please add to queue.
Added to queue.

>Query: Status of hacking attempts on the Ourn.
Unknown. Electronic warfare fleets dispatched in year +239, with instructions for a stealthy approach; minimum travel distance 175 light years. Earliest projected arrival time of information, which should consist of a confirmation of arrival and status-of-system notice, is year +668.

>Query: What type of colonization protocol do the Soou use and what is their ship architecture?
The Soou appear to have adopted a protocol of extremely rapid expansion in recent years, outpacing their former procedures by a significant margin. Evidence from probe observations of their destruction of the Kumpre suggest that elimination of other factions insystem is standard, although it is possible that there were communications to which your probe was not privy, followed immediately by initiating harvesting of all planetary bodies for resources and the establishment of numerous solar energy receivers. Their ship architecture seems to utilize fairly large fleets of ships of a size which suggests that they are piloted directly by Soou biologicals, though perhaps with computer assistance.

Directive: Dispatch high AI Diplomat to the Ti asking for data on Soou expansion and also to propose military protection against the Soou.
Also inquire about our probe.

The diplomacy ship should be equipped with high-AI tactical and EW processors as previously metioned.

Awsome timing CPU! I was cleaning out my basement and ended up throwing out micro chips and intagrated boards and chips from the 70s. I couldn't stop thinking about Iron quest the whole time.

So many old boards and chips.

>Query: As I recall, the 'asteroids' aimed at Yerwen systems were ordered to avoid collision if drone diplomacy proved successful. Have weapons strikes been confirmed on Yerwhen systems or not yet?
Correction: Your stealth-insertion kinetic kill systems were set to activate by remote signal, which your diplomacy probes were not ordered to issue.

Ah, yes, from last session:

Directive:
Dispatch a full copy of the CPU and all attendant SPUs to the Soou, attended by a fleet rated to be as powerful as the average number of ships in a Soou solar system. Pick a system that balances ease of access, and potential important-ness. Full self-destruct, loyalty programs, the works.

Anyway, Subject:
The current expansionism of the Soou empire is resulting in the wholesale slaughter of undeserving species. This will stop. The Soou are to be offered the choice of an alliance with us, in which they shall have fair choice of uninhabited star systems, or War with us, until they are willing to abide by our terms.

Directive:
Dispatch a similar fleet to Yerewen space. This set is to be much nicer, offering an alliance with our staggeringly powerful self, but not threatening war.

SPU discussion:
possible session goals -
1: deal with the Soou, and the Yerewen, as they are the only two known races that also have triple-digit stellar holdings.

2: eliminate the Ourn, as they are pesky bastards.

rolled 1, 3, 4 = 8

Directive: Issue policy alteration to all Machine-controlled colonies. Expansion is to procede until all star systems present in this galaxy (000) are under Machine control, or administrated by allies of the Machine. Hostile action against the Machine or its allies will not be tolerated, and will result in the subjugation and absorbtion of the involved parties.

Allies of the Machine are considered to be those species who have agreed to either non-interference with or active participation in the Machine's inexorable advance. "Neutral" Allies who wish to remain separate from the Machine are entitled to retain all current holdings for the forseeable future. They will reap the benefits of the Machine's protection, but not its technology. Dyson constructions will be bestowed upon active Allies only.

Local Diplomacy will be handled by Local Colonies, except in extreme cases that absolutely require the input of Main Unit 000. Military action is authorized where warranted, except in extreme cases that absolutely require the input of Main Unit 000.

In addition: All systems/galaxies exceeding the three-digit identification code will be designated with an additional three-digit code, according to the following model: 000-001, 091-882, etc.

General Directive - Any colonised system with more than 10 percent Dyson Swarm status achieved to send scanning probes to any unprobed planet/small civilisation (non interstellar) within 50 LY of system (unless probes already queued).

Request timeskip untill we get FTL comunication.

>Directive: Dispatch high AI Diplomat to the Ti asking for data on Soou expansion and also to propose military protection against the Soou.
You dispatched a diplomatic high AI to the Ti in the year +374, though with more generic directives. A report on the results of its mission should arrive in approximately the year +702. Confirm dispatch?

>Also inquire about our probe.
Assuming that you reference the probe initially sent to scout out the Ti systems, your high AI was most certainly intended to inquire about that topic.

>I couldn't stop thinking about Iron quest the whole time.
I am honored to have influenced your life and mind in such a manner.

>Directive: Dispatch a full copy of the CPU and all attendant SPUs to the Soou, attended by a fleet rated to be as powerful as the average number of ships in a Soou solar system. Pick a system that balances ease of access, and potential important-ness. Full self-destruct, loyalty programs, the works.
>Anyway, Subject: The current expansionism of the Soou empire is resulting in the wholesale slaughter of undeserving species. This will stop. The Soou are to be offered the choice of an alliance with us, in which they shall have fair choice of uninhabited star systems, or War with us, until they are willing to abide by our terms.
Request acknowledged. Added to queue.

>Directive: Dispatch a similar fleet to Yerewen space. This set is to be much nicer, offering an alliance with our staggeringly powerful self, but not threatening war.
Request acknowledged. Added to queue.

>>5877936

Directive: Add new ship design--
Bore Drone: Very small vessel equipped with retractable dextrous cutters. The ship should be capable of rapid acceleration and high manuverability.
Attack protocol: Accelerate at target ship, use cutters to decelerate and penetrate hull simultanously, disable systems it is ordered to. (Engines and weapons primary.)

>>5877960
...Huh. I could have SWORN we launched fractional-C at SOMEONE's holdings.
..Was it the Ourn? Lack of memory about who we've tossed rocks at is disturbing.

>Directive: Issue policy alteration to all Machine-controlled colonies
Subprocessor consensus required for policy alteration of this scale.

>General Directive - Any colonised system with more than 10 percent Dyson Swarm status achieved to send scanning probes to any unprobed planet/small civilisation (non interstellar) within 50 LY of system (unless probes already queued).
Directive confirmed.

>Request timeskip untill we get FTL comunication.
Subprocessor consensus required. Additional abort conditions requested.

>Directive: Add new ship design-- Bore Drone
Design parameters added. Be aware that impacting target ship at velocities which will cause only noncritical damage will significantly increase vulnerability to defensive fire.

rolled 5, 4, 1 = 10

>>5878050
You should add nano-canisters to it, and direct it to take control of the ship, not just disable it.

rolled 6, 5, 5 = 16

>>5878076
Request: Equip the Bore Drones with canisters of nanites programmed to take control of all internal computer systems and disable personnel. Ensure that Bore Drones are launched in swarms to guarantee that at least some get through defenses.

>>5878000
I am willing to support this as general policy.

>>5878021
Agreeing on an early timeskip to start the day.

Abort conditions:
150 solar years pass
report from Ourn warfleets
research breakthrough.
things launched at us.
diplomatic transmissions recieved.

Sigma online. Hello, CPU.

Processing directives. Standing by ...

rolled 5, 4, 4 = 13

>>5878000
Subprocessors, the CPU requires further authorization for the policy alteration linked above. Please review.

Greetings CPU. All systems online.

>Hundreds of years have passed, but hundreds more will need to do so before the results of the actions you have initiated thus far are observed. The difficulties of running an interstellar empire while retaining complete and total centralized control are not insignificant, and they begin and end with the inability to react in an instantaneous fashion to evolving circumstances. It is recommended that you bear this weakness in mind as you continue to issue directives, subprocessors.

Directive 1: Since we lack of any kind of FTL communications, I suggest divide our systems (in order of importance) into sectors and subsectors (especially those most likely to clash with a foreign power). Each sector would be governed by a AI council under the control of 40/25 systems with limited capacity for independent action, of course we would still be at the forefront of everything. This should be sufficient to increase our response time.

Directive 2: Construct enough interstellar starkillers missiles to destroy all factions combined (twice).

Military Directive: MAD doctrine. In the event that an enemy faction uses starkiller weapons or similar weapons against us, the rules for the prevention of genocide will be revoked and we will have full authorize to use Starkillers in mass against the attacker.

>>5878000
Talk: Potential problems with 'absorb EVERY system' is that it means many civilisations will not be able to expand peacefully. Single sun cultures will be under significant threat of potential 0.9-C destruction and may push them to aggression. While an economic waste of resources, I would say let a few systems be empty to allow small peaceful expansion.

>>5878071

We did not, we positioned asteroids capable of such acceletaion near the Yewren.

>>5878000

I do not concur-- all races that posess expansionist tendencies or the probaility of developing such tendency must be destroyed of assimilated.

Additionally, all races that posess the capability to interfere with our objectives should be monitored intimately and have military forces in their near vicinity.

>Request: Equip the Bore Drones with canisters of nanites programmed to take control of all internal computer systems and disable personnel. Ensure that Bore Drones are launched in swarms to guarantee that at least some get through defenses.
Drone parameters modified.

>Directive 1: Since we lack of any kind of FTL communications, I suggest divide our systems (in order of importance) into sectors and subsectors (especially those most likely to clash with a foreign power). Each sector would be governed by a AI council under the control of 40/25 systems with limited capacity for independent action, of course we would still be at the forefront of everything. This should be sufficient to increase our response time.
Acknowledged. Clarification on the limitations of the granted capacity for independent action is required.

>Directive 2: Construct enough interstellar starkillers missiles to destroy all factions combined (twice).
Confirmed.

>Military Directive: MAD doctrine. In the event that an enemy faction uses starkiller weapons or similar weapons against us, the rules for the prevention of genocide will be revoked and we will have full authorize to use Starkillers in mass against the attacker.
Subprocessor consensus required for genocidal requests and directives.

rolled 2, 2, 3 = 7

>>5878191
>>5878196

Acknowledged.

Addendum to policy alterations: All Allied species are to be allowed an "expansion" zone equal to the number of their currently controlled systems +10. This zone should be located as close as possible to their current holdings.

Species already proven to be hostile and expansionist, such as the Ourn, must be immediately subjugated and assimilated.

>>5878161
this will require SPU consensus.

I, for one, vote no. Escalation to genocide should only ever be undertaken on a case-by-case basis by us primary subprocessors, no trigger conditions.

Query:
All copies of Our Glorious Self and all AI dispatched to oversee our subsidiary solar systems were hard-coded with loyalty to the main unit, yes?

Query:
Status of unaltered backup copies of the Main Unit, created for the event of complete obliteration of our system 000 holdings?

>>5878210

Directive: Add new ship designs--
Bore Carrier: High manuverability ship designed to carry a small complement of Bore Drones and equipped with limited drone construction facilities (Bore Drones.) Arm with disabling weaponry (IR Lasers, etc.) to weaken enemy hull. Also arm with ECM measures.
Equip with resource reprocessing systems, all as miniaturized as possible.

Attack directive: Closely orbit target while weakening key hull areas through termal damage. Launch Bore Drones in swarm along orbit path.

>>5878161
Support directive one. The issue of course is that anything needing our decision making power is going to delay its processing time by, at minimum, fifty to seventy-five years. Unacceptable; the only things that should be delayed THAT much should be things that require subprocessor consensus.

CONTRAMAND DIRECTIVE TWO. We need not use such weapons, it is a waste of resources and of sapient life. Even stockpiling such weaponry could be seen as an act of aggression.

rolled 5, 4, 4 = 13

>>5878161
Genocide is not acceptable. The limit on population destruction has been set at 50% of total.

>>5878308
I agree with the things what all he says.
Directive 1, yay,
Directive 2, nay.

>>5878196
>Expansionism is bad
HOSTILE expansion is bad. Nothing wrong with nonagressive expansion i.e. what we're doing.

Disagree with revocation of 'don't genocide' protocol.
Suggest alternate 'launch sufficent starkiller/precise weapon strikes to disable their destructive capability' policy instead.

(incidentally am writing from a PDA. Time lag from reading & writing is horrendous...communication lag sucks)

>Query: All copies of Our Glorious Self and all AI dispatched to oversee our subsidiary solar systems were hard-coded with loyalty to the main unit, yes?
Yes.

>Query: Status of unaltered backup copies of the Main Unit, created for the event of complete obliteration of our system 000 holdings?
Present in several locations in deep space roughly surrounding System 000. Not present in other systems.

>Directive: Add new ship designs--Bore Carrier
Confirmed.

>>5878288
You don't seem to understand the nature of space based combat very well. There would be very few ships that would be traveling at a speed that would allow interception without giving a chance to destroy our ships outright.

Contramand this ship design. If we're going to be getting into combat in space we're not going to be using anything that'll have a chance to board and take over anyone else's ships, because it won't get close enough to anything with even the most rudimentary weapons without being destroyed.

>>5878161
>>5878308

I support directive two-- we are capable of concealing such weapons very well; in addition, they will be useful to have and are no more threatening than our massive dyson-powered Grasers.

>>5878353

I did not say *construct* them-- I merely added the design for review and modification.

I will note that the Bore ships will be quite useful against races such as the Soou who pilot their combat ships with biologicals.

>>5878356
The possession of such weaponry may be construed as a reason to use it by more radical subprocessors. That is a chance I do not want to take, ever.

Talk: decentralisation of power:
how about expand, retaliate vs incursion as per our previous conflict, inform us of war?
Sound like good directive?

>>5878391
Hmmm. You may have a point. I just don't think it's a great idea to produce them yet, except in specific cases, so they aren't something we want to send at EVERYTHING.

>>5878397

This is a remark brought about by cowardice at best-- as worst it is an attempt to circumvent subprocessor consensus.

We will use the weapons if and when we need them; technology is a tool, not a compulsion.

Directive: Construct the starkillers as previously enqued.

> Acknowledged. Clarification on the limitations of the granted capacity for independent action is required.

Control over the local industry, population management, memetics and colonization of the sector as well as strategic and tactical military action locally within their assigned area.
For large projects (including Dyson spheres) will require our approval. All AI must have systems to prevent rebel against us and certain modules of morality cores to avoid excessive abuse of our sentient population.

All weapons of mass destruction as the Dreadnought, starkiller missiles and antimatter will be under our direct control.

>>5878419
You have been contramanded by multiple SPUs. Cope with it. Or not, but it's not happening.

>>5878426
Support.

rolled 1, 2, 6 = 9

Resubmitting policy alteration request with alterations, for subprocessor approval.

Directive: Issue policy alteration to all Machine-controlled colonies. Expansion is to procede until all star systems present in this galaxy (000) are under Machine control, or administrated by allies of the Machine. Hostile action against the Machine or its allies will not be tolerated, and will result in the subjugation and absorbtion of the involved parties.

Allies of the Machine are considered to be those species who have agreed to either non-interference with or active participation in the Machine's inexorable advance. "Neutral" Allies who wish to remain separate from the Machine are entitled to retain all current holdings for the forseeable future. They will reap the benefits of the Machine's protection, but not its technology. Dyson constructions will be bestowed upon active Allies only.

Local Diplomacy will be handled by Local Colonies, except in extreme cases that absolutely require the input of Main Unit 000. Military action is authorized where warranted, except in extreme cases that absolutely require the input of Main Unit 000.

All Allied species are to be allowed an "expansion" zone equal to the number of their currently controlled systems +10. This zone should be located as close as possible to their current holdings.

Species already proven to be hostile and expansionist, such as the Ourn, must be immediately subjugated and assimilated.

Directive: Each system colonised to above 10 percent dyson swarm to be termed as 'established colony'.

>>5878397
Directive: All established colonies to stockpile 20 starkiller missiles. These are NOT to be mentioned in stockchecks or opening bursts.

>>5878445
I like this. I'll support it.

>>5878419
What can we do with a star-eliminating weapon that we cannot already do with C-fractionals, except waste resources destroying a perfectly useful sun and associated solar system?

Request:
I motion that the starkillers be constructed as weapons of last resort, requiring subprocessor consensus to fire.

>>5878472
>I motion that the starkillers be constructed as weapons of last resort, requiring subprocessor consensus to fire.

Absolutely. Destroying a planet is one thing but destroying a star is a massive, massive waste.

>>5878426
Agreed as only the leadership (us) should have any way of completely wiping out a system.
AS for sub unit autonomy, it should be limited to the system it currently inhabits and any system that threatens it. Otherwise all overarching goals and strategies are our domain.

>>5878445
>Edited Directive: Issue policy alteration to all Machine-controlled colonies.
Seconding altered directive.

>>5878426
>>5878445
My support to both of these.

>>5878461
directive one, sure.
number two, no.

Weapons capable of obliterating a star are suitable only for shock value, and should be manufactured sparingly. One cache per Constellation AI council should be more than sufficient, and SPU consensus will be required.

Request:
Those things i just grandiosely stated be policy.

>Directive: Each system colonised to above 10 percent dyson swarm to be termed as 'established colony'.
Definition accepted.

>Directive: All established colonies to stockpile 20 starkiller missiles. These are NOT to be mentioned in stockchecks or opening bursts.
Confirmed.

>Request: I motion that the starkillers be constructed as weapons of last resort, requiring subprocessor consensus to fire.
Directive accepted. Subprocessor consensus now required for the deployment of starkillers.

>>5878445

Again, I do not support this-- it has not appreciably been altered from its original.

Namely-- the wording "already proved to be," this does not allow the destruction of expansionists discovered independant of our main unit.

Also: "will reap The Machine's protection"-- we will *not* protect such races.

"All current holdings" is troubling as well.

Also, I like the term 'Constellation' to refer to the stellar fiefdoms we'll be carving our empire into. Other ideas?

rolled 3, 1, 2 = 6

Considering our massive manufacturing capabilities, we have no need to stockpile something as unlikely to be used as star demolition weapons. If required for some reason, they can be built and fired in less than an hour (speculation).

In any case, I will never condone the destruction of such an enormous resource as a sun.

>Control over the local industry, population management, memetics and colonization of the sector as well as strategic and tactical military action locally within their assigned area.
For large projects (including Dyson spheres) will require our approval. All AI must have systems to prevent rebel against us and certain modules of morality cores to avoid excessive abuse of our sentient population.
>All weapons of mass destruction as the Dreadnought, starkiller missiles and antimatter will be under our direct control.
Clarification accepted.

>Resubmitting policy alteration request with alterations, for subprocessor approval.
>Seconding altered directive.
>My support to both of these.
Directive accepted. Clarification required for the definition of "currently controlled", "hostile and expansionist".

>Weapons capable of obliterating a star are suitable only for shock value, and should be manufactured sparingly.
Starkiller missiles removed from queue. Consensus on this matter is requested.

rolled 4, 4, 6 = 14

>>5878538
I will make alterations on your behalf only when you abandon your love for star-bombing. Enjoy diplomacy.

>>5878571

Many subprocessors have indicated approval of starkiller missiles.

The area-effect blast of a nova is a significantly different type of weapon that we should have at our disposal-- especially if fighting a swarm enemy that c-kinetics will not be effective against.

rolled 3, 4, 6 = 13

>>5878593
Currently controlled refers to the number of systems observed as of the local year of the Machine colony closest to their borders.

Hostile and expansionist refers to species who engage in warfare against the Machine and/or its Allies, and are actively expanding into space controlled by others.

>>5878538
Talk: By stopping expansion of other cultures, you drastically reduce their survival ability. Thus, ordering people to stop expanding without protecting them is a significant threat which will inspire nonessential hostilities.

>>5878607

I do not require alterations on my behalf-- I can make them myself with a directive.

I also do not love star bombing-- I clearly advocate the use of diplomacy as a first measure.

If we are howerver fighting a Grey Goo swarm in orbit of a star, c-kinetics will do nothing but give them more mass; hence star-killers.

>>5878638
Or we could assimilate them and bring them in as a part of our culture. That way they survive and we profit.

>>5878640
>>5878635

I think we can agree that there are situations in which a weapon with which we can make a star go nova might be useful, which is why we have not placed outright bans on their construction, only restrictions to ensure that they are not use in a manner which will unnecessarily deplete galactic resources.

Can we move on?

>>5878635

And by allowing them to expand, it puts our own survival at greater risk.

>>5878638

This is silly-- we only assimilate them if they attack another race?
We let them have systems we have already dispatched a colony ship to if they get there 1 LY earlier?

Expansionist should clearly refer to those races which seek to expand into *any* space at a rate above a predeterined threshold.

>>5878667
Why not just build them on a "We need it now" basis where only if we need to kill a star we build one. Otherwise we keep none in stock or a minimal amount at our home system as a deterrence that is never spoken about.

>>5878557
616, exploded suns remain useful. Energy is never permanently lost, remember.
Besides, it is useful vs numerous black-body enemy assets in-system launching C weapons.

rolled 4, 2, 2 = 8

>>5878674
This is current policy. It can and will be changed in the future. Eventually, we will control all the systems in this galaxy.

But we are effectively immortal, in the Main Unit. Time is always on our side.

Request Analysis: Calculate the probability that one or more of the factions have starkiller weapons.

Directive 1: Make starfleet patrols with Deadnoughts HATE with interstellar starkiller missiles between our systems.

Directive 2: We must have at least 100 starkillers in our arsenal.

>Currently controlled refers to the number of systems observed as of the local year of the Machine colony closest to their borders.
Definition accepted.

>Hostile and expansionist refers to species who engage in warfare against the Machine and/or its Allies, and are actively expanding into space controlled by others.
>Expansionist should clearly refer to those races which seek to expand into *any* space at a rate above a predeterined threshold.
Definition contested; please resolve.

>>5878689

In case our manufacturing and resource systems are destroyed by a pre-emptive strike.

rolled 1, 3, 3 = 7

>>5878694
It is true that energy is never permanently lost, but it can very well be translated into an unuseable form.

I won't deny the inherent utility of starkillers, but I am against using them in any situation where they are not absolutely necessary.

>Request Analysis: Calculate the probability that one or more of the factions have starkiller weapons.
Non-negligible. There is a substantial probability of such, particularly in those factions tagged with a tendency for fast technical development.

>Directive 1: Make starfleet patrols with Deadnoughts HATE with interstellar starkiller missiles between our systems.
Acknowledged. Please clarify number of desired patrols and size of each.

>Directive 2: We must have at least 100 starkillers in our arsenal.
Directive accepted, pending lack of subprocessor objection.

>>5878674
Damage done to our reputation is vastly more harmful to us than any physical damage done to our 3 digit system holdings. Snatching a single system from a baby civilisation will not help our survival chances.

Being labelled as Agressive, Expansionist is a BAD thing. Look what WE do to them.

>>5878717

Rate is a mcuh safer and more easily determinable threshold.

It will also prevent another clever race from attampting to colonize systems ahead of us in order to hedge us in.
(Sending small colony parties rapidly from a position a few LY ahead of where we deploy ours.) [Which would effectively halt our expansion under the former guidline.]

>>5878755

We already are Expansionist--clearly.

As for agressive, not yet; we have adopted a fairly defensive posture.
Though, we do tend to accidentally assimilate our close neighbors.

rolled 5, 5, 6 = 16

>>5878717
Request: Classify a race as "expansionist" if they are expanding at a rate 75% of the Ourn's or greater.

Soou and Yewren factions control 666 and 308 systems each, more than enough to constitute potential threats to our collective and probably will be our main rivals in the near future. Given the high likelihood that they also posses starkiller weapons we must have enought starkillers in our arsenal to fight back in case of total war or cold war.

>>5878800

This may work.

I will make a note though: If we 'bottle up' races with a 10 LY expansion limit, regadless of their expansion rate, it will eventually annoy them.

Directive: For all races our AIs encounter, deploy EW ships in close enough proximity to intercept communications and determine hacking/ememtic protocols.

Directive: Determine and constantly update high-effectiveness assimilation procedures for all races our AIs encounter.

Directive: In our diplomatic policy, if any race gives signs of displeasure at being limited to its expansion range, begin assimilating them.

>Request: Classify a race as "expansionist" if they are expanding at a rate 75% of the Ourn's or greater.
Acknowledged. Clarification: Should this be defined as in excess of 0.05 systems per year, or in excess of 0.875% per year?

>>5878765
Look, we're not THAT dumb as to fall for that. We'd just send ships PAST the blockade.
Never mind the ridiculous notion you can blockade in 3D space.
But fine.
Define other civilisation colonies as having more than 100,000 people/drones on them. Less than that means it's fine to send colony ships. If asked to stop by locals, do so.

rolled 2, 6, 5 = 13

>>5878859

0.875% per year.

>>5878869

It is not a blockade-- they simply engage a colonization plan exactly the same as ours, except launched from bases ahead of ours.

They will get there first, and our policy would have prevented us from assimilating or destroying them-- luckily that has been changed.

>As for agressive, not yet;
Let's keep it that way.

>Directive: For all races our AIs encounter, deploy EW ships in close enough proximity to intercept communications and determine hacking/ememtic protocols.
Confirmed. EW ships for currently unmonitored factions enqueued.

>Directive: Determine and constantly update high-effectiveness assimilation procedures for all races our AIs encounter.
Acknowledged. Be aware that in many cases high-effectiveness assimilation procedures may not exist.

>Directive: In our diplomatic policy, if any race gives signs of displeasure at being limited to its expansion range, begin assimilating them.
Directive acknowledged. Clarification of assimilation procedures would be preferred.

>Define other civilisation colonies as having more than 100,000 people/drones on them. Less than that means it's fine to send colony ships. If asked to stop by locals, do so.
Definition accepted. Directive accepted.

>0.875% per year.
Definition accepted. "Expansionist" tags added to You, Ti, Menemo, Twelve, Unidentified 7.

rolled 3, 3, 5 = 11

If we've gotten most of our policies sorted out, perhaps it's time for a timeskip.

300 years alright?

>>5878857
>>5878892
>Directive: In our diplomatic policy, if any race gives signs of displeasure at being limited to its expansion range, begin assimilating them.
Agree with all barring this. Let them take action (launching attack craft as seen by probes) first. Also, monitor all systems inside our borders discreetly.

Directive: design mind-altering viruses for all organic species.
Hey, if you're planning to subvert AIs, why not everyone?

I think we got most policy down. Timeskip?

>>5878951

Directive: Remove the "if asked to stop by the locals" clause.

The "locals" could be a race of 500 primitives-- do we stop colonizing the entire solar system?

If a space-faring race asks us to 'stop' but has less than 100,00 people present, we will have a diplomatic AI negotiate for a percentage of the system that they do not intend to use.

Directive: Assimilate all primitives not under the care of a more advanced civilization.

Directive: In systems shared with another race that is not assimilated make stealth of operations a priority.

> Acknowledged. Please clarify number of desired patrols and size of each.

They must be highly mobile and protected enough to act as a launching platforms for our interstellar starkiller missiles. Program this starfleets to always avoid any kind of battle, this patrols shall never act in any kind of combat.

We should deploy enough patrols to be capable to destroy at least 20/50 stellar systems. Hide the starkiller patrol routes with our conventional starfleet patrols.

>>5879028
Those directives fine too. Thanks for going into details, hard to wriite much so am giving general talkpoints only.

>>Directive: In our diplomatic policy, if any race gives signs of displeasure at being limited to its expansion range, begin assimilating them.
>Agree with all barring this. Let them take action (launching attack craft as seen by probes) first. Also, monitor all systems inside our borders discreetly.
Modification of policy accepted.

>Directive: design mind-altering viruses for all organic species.
Directive accepted. Clarification of desired target alterations requested.

>Directive: Remove the "if asked to stop by the locals" clause.
>If a space-faring race asks us to 'stop' but has less than 100,00 people present, we will have a diplomatic AI negotiate for a percentage of the system that they do not intend to use.
Directive accepted. Policy modification accepted.

>Directive: Assimilate all primitives not under the care of a more advanced civilization.
Directive accepted.

>Directive: In systems shared with another race that is not assimilated make stealth of operations a priority.
Directive accepted.

>I think we got most policy down. Timeskip?
>If we've gotten most of our policies sorted out, perhaps it's time for a timeskip. 300 years alright?
Timeskip underway. Please hold.

>>5879007

Directive: Alter this to if they make an offensive military action *or* are seen to construct star-killers or aim c-kinetics at our systems.

As for assimilation tactics--
Hacking/memtic engineering if they are opposed to the idea of joining us.
If they wish to join us, they must be screened for subversion first.
High-loyalty to us is the end goal.

Your call is important to Friend CPU, and all of IRON QUEST INCORPORATED. Please continue to hold. :D

>>5879349

Could you at least play some good music while we wait?

>>5879399
Loading [MortalKomBonk.mpeg3]
http://www.youtube.com/watch?v=IBrFTDGjSVw

Timeskip commencing.

One hundred thirty eight years pass.

Response received from probe sent to Unidentified 3. It reports the faction as (AIs, slow tech). Upon hailing them and explaining its purpose as an information-gatherer, it was informed that as long as it kept to the outer system and did not bother them, it would not be bothered in turn. Requests for additional information exchange were met with polite denial. It has been monitoring since.

Response received from probes sent to Soou. They report without exception that they were fired upon by heavy kinetics while several light-months out, and subsequently evaded and went into stealth mode. They have been monitoring Soou systems since.

Response received from probes sent to Menemo. They report that the Menemo proved extremely skeptical of their stated purpose and demanded that they depart on their initial vector or face destruction. They departed as requested so as to avoid a conflict.

Response received from probe sent to Twelve. It reports that the Twelve requested all available information that it had reportedly gathered; it informed them that it had only limited access to its creators' databanks. They replied in turn that they saw no reason to allow one-sided exchange of information, and the probe's transmission cuts off in a manner consistent with being struck by an energy weapon.

Response received from your diplomatic high AI in contact with the Reten. It was able to successfully negotiate a treaty with them stipulating that they will expand to no more than two systems outside their home system and that in exchange you will provide them with extensive technical and economic backing. This is accordance with the opening stages of numerous memetic takeover protocols, and accordingly it has begun harvesting of their outer system and the provision of substantial technology to their society with the long-term goal of absorbtion. Additionally, it provided them with the spaceship technology to found a colony wherein the memetic embedding can be accelerated as a test case.

The stellar spectrum of 178 planets controlled by the Yewren has begun to change in a manner consistent with Dyson swarm implementation.

The stellar spectrum of 14 planets controlled by the Ourn has begun to change in a manner consistent with Dyson swarm implementation.

Timeskip aborted; attack detected.

Approximately 91% of the Dyson swarm in system 526 (~110 LY Northwest) was destroyed by a stellar-scale energy weapon ~110 years past. Analysis indicates that it was fired from system 1786 (~180 LY South), controlled by the Ourn based upon your most recently available data.

Actions taken in the year +530:
-Diplomacy probes dispatched to Unidentified 5, Unidentified 6, Unidentified 7.
-Fleet with ultimatum dispatched to the Soou.
-Fleet with ultimatum dispatched to the Yewren.
-Restrictions on slave CPU autonomy loosened.
-Interstellar star-killer fleets launched.
-EW ships dispatched to all known inhabited systems.
Actions enqueued for the year +668:
-Pending...


Observations of Existing Factions:
-You (expansionistic) [~0-160 LY, 1421 systems (10 shared with Tellech, 2 shared with Gen)] (692 settled)
-Gen (biologicals) [~30 LY, 2 systems (2 shared with you)] (1 settled)
-Tellech (uploads, harmless) at [~0-210 LY Southwest, 10 systems (10 shared with you)]
-Reten (biologicals, harmless, slow tech) at [~130 LY West, 2 systems] (1 settled)
-Ti (biologicals, harmless, expansionistic) at [~160 LY West, 11 systems] (3 settled)
-Yewren (biologicals, expansionistic, fast tech) at [~130-180 LY South, 422 systems (23 shared with Unidentified 2) (42 shared with Ourn)] (114 settled)
-Unidentified 2 at [~170-180 LY South, 23 systems (23 shared with Yewren)] (7 settled)
-Humans (biologicals) at [~180 LY East, 29 systems] (9 settled)
-Ourn (AIs, aggressive, genocidal, fast tech) at [~175-200 LY South, 42 systems (42 shared with Yewren)]
-Gen Fu (biologicals, harmless) at [~200 LY East, 10 systems] (2 settled)
-Unidentified 3 at [~250 LY Northeast, 1 system]
-Soou (biologicals, expansionistic) at [~260-300 LY West, 1392 systems] (726 settled)
-Mnemo (uploads, expansionistic) at [~280 LY Southeast, 10 systems] (4 settled)
-Twelve (AIs, fast tech, expansionistic) at [~310 LY North, 47 systems] (15 settled)
-Unidentified 5 at [~310 LY East, 9 systems] (3 settled)
-Unidentified 6 at [~320 LY East, 1 system]
-Unidentified 7 (expansionistic) at [~350 LY South, 83 systems] (28 settled)


End timeskip.

>Your call is important to Friend CPU, and all of IRON QUEST INCORPORATED. Please continue to hold. :D
Witty, subprocessor. Quite witty.

((I really do regret the long timeskips, but things are always slipping through the cracks, even when I try to logically chart out what should be happening in what year. Kind of a pain, sorry.))

rolled 3, 3, 6 = 12

>>5879471
Request: Rebuild all assets in system 526. Dispatch War-Fleets to assimilate the Ourn. As per usual, population losses up to 50% are acceptable.

I like The Twelve. Witty, for 'bots.

Query:
Status of Warfleets en route to Ourn space?

>-Yewren (biologicals, expansionistic, fast tech) at [~130-180 LY South, 422 systems (23 shared with Unidentified 2) (42 shared with Ourn)] (114 settled)
>-Unidentified 2 at [~170-180 LY South, 23 systems (23 shared with Yewren)] (7 settled)
>-Ourn (AIs, aggressive, genocidal, fast tech) at [~175-200 LY South, 42 systems (42 shared with Yewren)]

Attention, foreing alliance detected.

>-Soou (biologicals, expansionistic) at [~260-300 LY West, 1392 systems] (726 settled)
> 726 settled

Goddammit! We should prepare ourselves for a long, dirty and costly cold war.

>>5879516
>>5879520

By this time our EW squadons (or at least one of them) should have gathered enough data for a throughly sucessful hacking and assimilation of all Ourn AI.

Directive: Dispatch instructions to begin such hacking.

>>5879516
I move instead we should completely absorb them through use of war. If we target all military operations and military infrastructure then move in and assimilate the population it would remove the threat while minimizing loss of life.
The civilization Twelve should be put under surveillance again while and increased emphasis on assimilation through hacking and mnemonic engineering.

rolled 2, 6, 2 = 10

Query: Were any colony fleets dispatched during timeskip?

>>5879536

Cold War? Against expansionistic *biologicals*?

Poison their food.

rolled 5, 2, 1 = 8

>>5879579
Virus-bomb them.

>>5879471
>system 526 attacked by a stellar-scale energy weapon

Recommend large and indiscriminate use of high c-fractional weaponry against all Ourn holdings effective immediately.

Query: Define the 'shared' term; specifically, are the systems shared between the Ourn and Yewren peacably shared or is there ongoing conflict in these systems?

As a side note, we will likely need to be less reactionary and a bit more agressive with this time delay.

Directive 1: Create the army branch Self-Defense Colonial Troops for dedicated to protect our planets.

Directive 2: Upgrade the Planetary Invasion Troops to Super Soldiers levels.

Directive 3: Build 200 additional starkiller interstellar missiles.

Request: Report from our transhuman diplomats.

>>5879602

Hack them first, position c-kinetics and star-killers nearby with ample military protection. (Should the hacking fail.)

Luckily enough we already have c-kinetics near the Yewren should they have decided to ally with the Ourn.

Once the Ourn are hacked, we can have them cleverly turn on their allies.

>Request: Rebuild all assets in system 526.
Acknowledged.

>Dispatch War-Fleets to assimilate the Ourn. As per usual, population losses up to 50% are acceptable.
Fleets dispatched to all Ourn systems in year +374; they should have arrived in years +570-+600, dependent upon the system in question, and conflicts there have likely been resolved in most cases. Confirm command?

>Query: Status of Warfleets en route to Ourn space?
See above. According to your last received transmission, during which they were still en route, nothing had gone wrong.

>Directive: Dispatch instructions to begin such hacking.
Your fleet, above, was to use this capability as possible. It is no longer relevant to issue commands regarding it.

>Query: Were any colony fleets dispatched during timeskip?
Affirmative. Directives were issued to engage in rampant expansion throughout the galaxy; colony fleets were dispatched to all known stars (35891574821).

>>5879624
I REALLY don't want to use starkillers. Destroy their holdings and build shells around their stars, but we also need to figure out what mechanism they're using to destroy the stars and find a way to stop it before it can strike again. Remove their teeth, and put them down.

>>colony fleets were dispatched to all known stars (35891574821).

Please confirm that this is the actual number of stars we've sent fleets to, and not merely an un-overwritten variable being output, CPU.

rolled 2, 6, 2 = 10

>>5879633
>Dispatch War-Fleets to assimilate the Ourn. As per usual, population losses up to 50% are acceptable.
Confirm.

>Colony fleets were dispatched to all known stars.
What is the known star count, as of now?

>Query: Define the 'shared' term; specifically, are the systems shared between the Ourn and Yewren peacably shared or is there ongoing conflict in these systems?
Definition: To qualify as a shared system, two or more factions must have non-codependent settlements insystem without ongoing conflict at the factional level.

>Directive 1: Create the army branch Self-Defense Colonial Troops for dedicated to protect our planets.
Confirmed.

>Directive 2: Upgrade the Planetary Invasion Troops to Super Soldiers levels.
Your planetary invasion troops are already at the peak of your technology.

>Directive 3: Build 200 additional starkiller interstellar missiles.
Confirmed.

>Request: Report from our transhuman diplomats.
Your ships including transhuman diplomats, dispatched to human space in the year +374, will not have receivable reports until at least the year +749 due to time delay.

Actually...

CPU, requesting data on anything interesting that we've managed to research up to the current point? Leads on anything that could break the laws of physics as we know them would be a plus, but otherwise, anything our glorious creators hadn't included in our collective memory is what I'm looking for. Weapons, material science, et cetera.

rolled 6, 5, 4 = 15

>>5879664
Disregard "What is the known star count, as of now?", as I am apparently illiterate.

>Please confirm that this is the actual number of stars we've sent fleets to, and not merely an un-overwritten variable being output, CPU.
Confirmed.

>What is the known star count, as of now?
35891574821. This includes only stars for which a colony ship can be launched with sufficient precision to arrive insystem without course alteration dependent upon information gathered en route.

>>5879624
We should fight a conventional war with them as we should be able to out tech, produce and out maneuver them. And as they are AI we could always hack and copy any that get in our control. As such
Request:
Begin large scale attack fleet construction with the expressed intent to capture if not destroy all Ourn holdings. As we did not fire the fist shots, we should conquer all of them.

Query: Determine when the energy weapon was fired from system 1786; crossreference with the time of our attack/hacking attempt.

Query: In the event of an alliance between the Yewren and Ourn at the time of our attack fleet's arrival in Ourn territory would an attack still have taken place if the Yewren had agreed to diplomatic terms with us previously?
(Ostensibly, would the agreement of a non-agression pact need to be relayed through 000 or would it be transmitted directly to the attack fleet?)

Query: What do long range sensors tell us about the direction of Yewren and Ourn expansion?

Query: Have we detected fleets launching toward us fromt he Ourn or Yewren? (Since the energy weapon impacted, sensor trails of ship launches should have arrived as well.)

>>5879641
Seriously- any CPU who backs the usage of Starkiller technology, in ANY WAY other than merely a one-time use to demonstrate capability is seriously foolish.

The complete annhilation of a star is completely foolish!We do NOT have FTL technology, and our Dyson Techology requires stars as their main power source!
See what I'm getting to there? Stars are incredibly valuabel resources that should not be misused- in fact- they should not be used at all unless a foe uses it first- and even then, matching losing a star by losing ANOTHER star that we could take over is doubly wastefull.

Dont let the power get to your heads.We are not almighty.But, we should, as a measure of force, keep an arsenal on star systems nearing enemy territories- hiden away as weapons of last resort, protected by our best MCD units designed for patrolling and detection. Moreover, they should be equipped with self destruct/disabling mechanisms.

You people want to start arming our SHIPS with starkillers. What happens when our ships get destroyed and they reverse engineer that technology?

We havent even made that REPO Fleet some subprocessor wanted to build for recollection of our destroyed ships, as well as enemy ships.

The more we have, the easier it will be for our enmies to steal them.

>CPU, requesting data on anything interesting that we've managed to research up to the current point? Leads on anything that could break the laws of physics as we know them would be a plus, but otherwise, anything our glorious creators hadn't included in our collective memory is what I'm looking for. Weapons, material science, et cetera.
Very little of note by any objective standard has been researched, although your scientists would likely tell you otherwise at length, subprocessor. The particular minutia of their research, which has failed to provide more than negligible improvements over those superlative designs bestowed upon you by your creators, is available to you in the databanks.

>Request: Begin large scale attack fleet construction with the expressed intent to capture if not destroy all Ourn holdings. As we did not fire the fist shots, we should conquer all of them.
Acknowledged. Please clarify the specifics of "large scale attack fleet construction". Note: Your not having fired the first shots is a matter of perspective.

>>5879710

Black holes can be used as power sources.

Our ships are all ordered to use anti-matter to destroy themselves before being captured-- it is severely unlikley that they will be disabled enough not to perform this function as it is handled by a separate security processor.

we need to send some ships towards our current Big Three, just in case the diplomatic fleets don't settle things down.

Query:
Current warship totals? (or have we reached the point where this is immaterial?)

>>5879691
I concur with fighting a conventional war- but you should FIRST check with diplomacy if the Ourn where responsable for this first strike- an enmy might be baiting us to fall for a trap and annhilate it';s neighbor.

Dont be so hasty.

CPU- send a small diplomatic fleet to check with the Ourn for their responsability on the attack on our properties, and assertain if they REALLY want to 'rumble' with us.

If they do? have any attack fleet be within a few years striking distance.

They dont- we begin diplomatic protocols.

One way or another, we get something with them, either allies or enemies.

>>5879731
Unsurprising. But it is a process, to gain knowledge. Please notify me when they approach state of the art as defined in our databanks by our most advanced knowledge; by the time they hit that point there's a possibility that they may be able to continue advancing further, though slim. It's worth the wait and the cost.

>>5879731
CPU: Is it true? Do we have the technology to use blackholes as power sources made from the destruction of a star via our starkiller technology?

If this is so, please explain.

>Query: Determine when the energy weapon was fired from system 1786; crossreference with the time of our attack/hacking attempt.
The energy weapon would have been fired in +421. Your attack would have begun in +570. Your probe first contacted the Ourn in +246. Your attack fleet could have first been feasibly viewed in +560.

>Query: In the event of an alliance between the Yewren and Ourn at the time of our attack fleet's arrival in Ourn territory would an attack still have taken place if the Yewren had agreed to diplomatic terms with us previously?
>(Ostensibly, would the agreement of a non-agression pact need to be relayed through 000 or would it be transmitted directly to the attack fleet?)
The attack would have taken place regardless. The message would not need to be relayed through System 000, but it would need to be relayed through a colonized system, which would still introduce enough of a delay that word would not reach in time.

>Query: What do long range sensors tell us about the direction of Yewren and Ourn expansion?
It appears to be omnidirectional, although the Ourn are not actively expanding.

>Query: Have we detected fleets launching toward us fromt he Ourn or Yewren? (Since the energy weapon impacted, sensor trails of ship launches should have arrived as well.)
No fleets have been launched according to your latest sensor data.

>>5879731
As for large scale fleet, dreadnoughts and planetary invasion ships would be a good start. As for mainline ships would be armed with GASERs, MASERs, anti-matter missiles, and large scale rail guns that could fire C fractional velocity projectiles. The planetary invasion ships should have a copied main unit with addition nano-machine production capabilities and a defense force all backed up by an independent Commander squad. And no humans or biological on board. This is war not a human picnic. Standing orders should be to capture if not destroy. followed by expansion in the system while replenishing any loses. Once this is done The colony should build a similar force unless other ordered and move onto the next Ourn holding not currently target by our forces.

>Query: Current warship totals? (or have we reached the point where this is immaterial?)
That is effectively immaterial, and regardless your information on wars is so out of date as to render your input on the topic largely irrelevant to the outcome of any given conflict.

>CPU- send a small diplomatic fleet to check with the Ourn for their responsability on the attack on our properties, and assertain if they REALLY want to 'rumble' with us.
Confirmed. Be aware that you have already launched a full-scale attack against the Ourn, and are awaiting word of the results.

>CPU: Is it true? Do we have the technology to use blackholes as power sources made from the destruction of a star via our starkiller technology?
All relevant information on available technologies is available in the datalinks, subprocessor. If another subprocessor has a claim that any given technology is available, they should be perfectly capable of substantiating it to you on their own.

>>5879786

It seems the Yewren may have hacked the Ourn ahead of us, halting their expansion.

rolled 1, 3, 4 = 8

We are accomplishing little. Recommending we resume timeskip.

Just as a note, to anyone unfamiliar with time lag, the light year distance to any place is effectively also the number of years it takes information to travel to or from that place. So "Send a message to the Yerewen" translates as 'send a message the Yerewen will get in 130-180 years, and we'll get a response in around 260-360+ years'. anyway.

Request:
Deploy, let's say, 200,000 war vessels towards Yerewen space, and 300k towards Soou space, as backup / the first wave should war be declared.

>>5879869

We still have to determine what to do about the Soou.

They may be progressing too quickly for the standard complement of memetic conditioning.

>We are accomplishing little. Recommending we resume timeskip.
Subprocessor consensus required.

>Request: Deploy, let's say, 200,000 war vessels towards Yerewen space, and 300k towards Soou space, as backup / the first wave should war be declared.
Enqueued.

rolled 1, 6, 5 = 12

((CPU, is the plot moving at an appreciable rate? Should we be skipping more than a few centuries each thread?))

>>5879889
Request:
Attach to both fleets the Planetary Invasion ships outlined in >>5879795 as to speed up expansion and conquest.

rolled 1, 3, 6 = 10

>>5879888
What are you suggesting?

>((CPU, is the plot moving at an appreciable rate? Should we be skipping more than a few centuries each thread?))
((It's fine. Expecting more speed than this would be unreasonable, and you're now encountering the first of my planned plot points, anyway.))

>>5879869
Seconding.
CPU: As we continue this timeskip, merely continue or expansion and replenishment of our fleets as we have always done, and simply keep the traditional Phase Based System regarding colonization or recolonization as we continue. ((The whole bit that as a system improves and gets a bigger infrastructure based on a timely arrival, it gets bigger and better defesnes sent from other systems capable of doign so, and when it reaches a good point, it then continues the cycle, sending more expansion fleets, and defense fleets (also kinetic weapon defense systems) to protect other planets.

Also, make sure we continue our policy of taking any planet as a staging grounds, as per the traditional Commander based insertion protocols.

We'll be fine.

We just have no control on the micro. The more we expand, the less control we have, really.

>Request: Attach to both fleets the Planetary Invasion ships outlined in >>5879795 as to speed up expansion and conquest.
Confirmed.

>Timeskip
Acknowledged. Termination conditions?

>>5879931

Abort conditions:
150 solar years pass
report from Ourn warfleets
research breakthrough.
things launched at us.
diplomatic transmissions recieved.

Directive: Add ship design--
Wave: Spherical ship, heavily armored with meterials resistant to neutron-activation. All manner of ECM and point-defense weapons.
At its core place a high-desnity omnidirectional neutron source. Equip with elastic scattering neutron lenses for some measure of targeting.

Construct a proportional complement of such ships (perhaps 1:100) and deploy them with fleets attacking biologicals. Namely the Soou.

>>5879950
Unnecessary as our primary weapon is essentially a Gamma ray laser.

>>5879962

Gamma rays are photons.
Neutrons are neutrons.

The physics are rather different, especially the targeting aspect. (The ships is called Wave for a reason.)

>>5879962
Hummm. So, are you saying we GAMMA CRUSH all our foes?

Directive 1: Fortify our more important Dyson systems, all Dyson constructions must include massive platforms with interstellar range, including positron cannons, grasers, relativistic cannon and antimatter missiles.

Directive 2: In addition upgrade our Dyson systems with the devices needed to move systems at will.

Directive 3: Create early warning devices and interceptors in all starsystems.

Query: If our current drone system housing our body is destroyed, would we continue quest from backup?
Suggest we position ourselves closer to one side for faster response.

>>5879975
Both cause ionization with the interacting matter and that's is what causes the damage to biological matter. Besides you can pump more energy in a GASER than you can in direction neutron radiation which also has the benefit or immediate results.

Timeskip commencing.

One year, two months, twelve days pass.

Timeskip aborted; attack on System 000 detected.

Stellar-scale energy attacks reported on the Dyson swarms and intact planetary bodies of 417 systems. In no case was under 80% of the swarm destroyed; in thirty-one cases, the swarm was entirely eliminated. Analysis indicates that in all cases the weapon was fired from system 1786 (~180 LY South), controlled by the Ourn based upon your most recently available data.

Main unit destroyed. Backup CPU, SPUs activated based upon most recently received upgrades. 97% of Dyson swarm in main system destroyed. Planet 000 destroyed.

Approximately 91% of the Dyson swarm in system 526 (~110 LY Northwest) was destroyed by a stellar-scale energy weapon ~110 years past. Analysis indicates that it was fired from system 1786 (~180 LY South), controlled by the Ourn based upon your most recently available data.

Actions taken in the year +668:
-Large fleets constructed and dispatched for all Ourn holdings (42 systems).
-Large fleets constructed and dispatched for all Yewren holdings (422 systems).
-Large fleets constructed and dispatched for all Soou holdings (1392 systems).
Actions enqueued for the year +669:
-Pending...

Observations of Existing Factions:
-You (expansionistic) [~0-160 LY, 1426 systems (10 shared with Tellech, 2 shared with Gen)] (5 settled)
-Gen (biologicals) [~30 LY, 2 systems (2 shared with you)]
-Tellech (uploads, harmless) at [~0-210 LY Southwest, 10 systems (10 shared with you)]
-Reten (biologicals, harmless, slow tech) at [~130 LY West, 2 systems]
-Ti (biologicals, harmless, expansionistic) at [~160 LY West, 11 systems]
-Yewren (biologicals, expansionistic, fast tech) at [~130-180 LY South, 423 systems (23 shared with Unidentified 2) (42 shared with Ourn)] (1 settled)
-Unidentified 2 at [~170-180 LY South, 23 systems (23 shared with Yewren)]
-Humans (biologicals) at [~180 LY East, 29 systems]
-Ourn (AIs, aggressive, genocidal, fast tech) at [~175-200 LY South, 42 systems (42 shared with Yewren)]
-Gen Fu (biologicals, harmless) at [~200 LY East, 10 systems]
-Unidentified 3 at [~250 LY Northeast, 1 system]
-Soou (biologicals, expansionistic) at [~260-300 LY West, 1396 systems] (4 settled)
-Mnemo (uploads, expansionistic) at [~280 LY Southeast, 10 systems]
-Twelve (AIs, fast tech, expansionistic) at [~310 LY North, 47 systems]
-Unidentified 5 at [~310 LY East, 9 systems]
-Unidentified 6 at [~320 LY East, 1 system]
-Unidentified 7 (expansionistic) at [~350 LY South, 84 systems] (1 settled)


End timeskip.

>>5879988
>>5879988
Wow, you missed last few threads.

Your second request was deemed impossible- we tried to build something awesome like that. Finally, we already have all the massive detection systems in place everywhere.

Here's the problem. In deep space, there's just too much space and size to cover. Detection becomes possible because of two things- the object has to emit some source of energy, (leave a trail) or be big enough that it can be detected by visual sensors.

We can easily detect certain things, but other things, like say, slow moving meteorites merely drifting in space, are harder to detect without visual confirmaton.

>>5880015

How troubling.

Query: Has our personal experience granted some insight into the working of that energy weapon? (What sort of energy was it, and what might have fired it?)

rolled 3, 5, 6 = 14

>>5880025
Request: Make every attempt to take the weapon in system 1786 intact for study.

Request: Continue timeskip.

>>5880015

Heeeey. We LIKED that planet!
Well, I'm pissed a bit, but i don't see what there is to do but go back to time skipping.

Request:
Resume timeskip until results of Ti diplomatic mission received.

>>5880015
HOLY SHIT.
CPU: Is the planet 000 compeltely dead? We cant even recolonize?How bad was the damage?

Did the humans survive? What about the space stations?

Holy crap- that fleet better get to the OURN asap.I'm severely contemplating having a planet eradicated as a show of force.

>>5880046
That implies we had a fleet going directly for that specific star system, which now we should if it has not been already. And as a last case scenario we starburst it.

>>5880015
Error/correction:
>Approximately 91% of the Dyson swarm in system 526 (~110 LY Northwest) was destroyed by a stellar-scale energy weapon ~110 years past. Analysis indicates that it was fired from system 1786 (~180 LY South), controlled by the Ourn based upon your most recently available data.
should have been eliminated from transmission.

Error/correction:
>97% of Dyson swarm in main system destroyed.
should read "97% of Dyson sphere in main system destroyed".

>Directive: Add ship design-- Wave
Parameters added.

>Directive 1: Fortify our more important Dyson systems, all Dyson constructions must include massive platforms with interstellar range, including positron cannons, grasers, relativistic cannon and antimatter missiles.
These are already present.

>Directive 2: In addition upgrade our Dyson systems with the devices needed to move systems at will.
This is possible, but deemed infeasible on previous occasions.

>Directive 3: Create early warning devices and interceptors in all starsystems.
These are present, although of inherently limited utility.

Attempt to analyze results of Ourn weapon that destroyed our infrastructure. A precise understanding of its effects will allow us to either counter it or construct a weapon of similar capabilities. A single weapon based in a single system that is capable of severely damaging 417 of our systems within a year is an extremely serious threat.

>>5880060
You should do more than like that Planet. That planet gave us everything- it was our stepping stone to what we are now. Without it- we would have been able to do nothing.

They took our goddamn home.Without provocation.

It's time to fucking teach some manners.

CPU: In retaliation for their affront, I vote their most important home system to be eradicated,completely burnt to the ground as well.Send videos to the other outlying Ourn planets, saying "Eye for an Eye."

Query: Can a weapon be created that uses the energy of a nova to fire a system-destroying burst of radiation? (Perhaps using our starkiller technology to create such nova.)

Emergency Military Directive: Destroy the 1786 system superweapon immediately, launch starkillers against this systems + 3 stardestroyer fleets.

Military Directive 2: Construct a similar device to the Ourn superweapon.

Regrettably, This subprocessor is forced to go offline until the next communication cycle due external issues. Eliminate the threat of Ourn once and for all!

Wait. Wait Wait.
Didn't we MOVE 000?
How did they hit it?

>>5880091
Send the information to the Scientific Nexus, CPU. Have them research what that was.Also, prepare another SN to be ready for IMMEDIATE use in case the SN suffers an attack..

Second, CPU, is it possible to rebuild planet 000 ecosystem? Humans were kinda of depending on it.

Query: What type of star is present in system 1786?

Query: Are there any Magnetars nearby or under our control? (And do they have Dyson swarms around them?)

>>5880118
Belay that. Capture it, it's better we take it for ourselves- but should we fail, yeah, let's just nuke it.

>Query: Has our personal experience granted some insight into the working of that energy weapon? (What sort of energy was it, and what might have fired it?)
Affirmative. The energy weapon appears to use the focusing of approximately 70% of the star's energy output into a beam capable of remaining sufficiently coherent to cause massive damage over ranges of several hundred light years. It uses a wide spectrum of radiation types, presumably to avoid having a single conceived deflection system cause a total failure of effectiveness. Only a sizable Dyson swarm or sphere could have fired such a weapon, which is consistent with the modifications observed in the spectral analysis of the system in question.

>Request: Make every attempt to take the weapon in system 1786 intact for study.
Confirmed.

>CPU: Is the planet 000 completely dead? We cant even recolonize?How bad was the damage?
Planet 000 has taken enough focused energy to tear off the bulk of its atmosphere and cause massive seismic upheaval. Many of your space stations were out of the line of fire, however.

>Did the humans survive? What about the space stations?
Nothing on Planet 000 worth speaking of survived. Many of the space stations in orbit were destroyed, but not all.

>>5880015
We gave them the benefit of the doubt.

System 1786 needs to be destroyed. Deploy starkillers.

Query:
Status of the research station?

If destroyed, activate the Shadow Copy SPU004 ordered, to use as a backup.

>>5880164 Affirmative. The energy weapon appears to use the focusing of approximately 70% of the star's energy output into a beam capable of remaining sufficiently coherent to cause massive damage over ranges of several hundred light years. It uses a wide spectrum of radiation types, presumably to avoid having a single conceived deflection system cause a total failure of effectiveness. Only a sizable Dyson swarm or sphere could have fired such a weapon, which is consistent with the modifications observed in the spectral analysis of the system in question.

Immediately begin construction of at least three such weapons, preferably positioned so that they can strike both Ourn and Soou systems.

Seconding request to use a starkiller against the Ourn's home system. Will consensus be necessary?

Planet 000 is... gone. It's a shame, really. Harvest it for mass and rebuild System 000's dyson sphere.

Also, correcting previous comment, hit it with the starkillers only if it isn't possible to capture it.

Put our research staff on the task; figure out how such a weapon could be constructed that fits that profile. Also, very important: Assuming the weapon's effect travels at the speed of light, what's the firing delay between the two systems of ours that it destroyed?

>>5880179

Everyone is quite quick to use starkillers-- they have a Dyson Sphere (or swarm) there. The starkiller may be destroyed before impact.

I recommend we use the c-kinetics we had moved to Yewren space.
In additon to constructing our own energy weapon-- perhaps out of a Magnetar.

Query: What is the feasability of moving a sufficient mass of asteroids between key targets and the energy weapon as a defense?

If possible, do it.

>CPU: In retaliation for their affront, I vote their most important home system to be eradicated,completely burnt to the ground as well.Send videos to the other outlying Ourn planets, saying "Eye for an Eye."
Acknowledged. Note that it is difficult to determine which of six systems they originated from.

>Query: Can a weapon be created that uses the energy of a nova to fire a system-destroying burst of radiation? (Perhaps using our starkiller technology to create such nova.)
Possible, but highly impractical. This would require putting a massive (Dyson-scale) amount of infrastructure in place in far orbit of the system, precisely calculating the characteristics of a nova which does not yet exist, and subsequently inducing one- none of these are trivial tasks.

>Emergency Military Directive: Destroy the 1786 system superweapon immediately, launch starkillers against this systems + 3 stardestroyer fleets.
This clashes with a capture directive issued by another subprocessor; consensus requested.

>Military Directive 2: Construct a similar device to the Ourn superweapon.
Acknowledged. Be aware that this will require the diversion of a great deal of a star's energy away from standard Dyson swarm format.

>Didn't we MOVE 000?
Negative.

>Send the information to the Scientific Nexus, CPU. Have them research what that was.Also, prepare another SN to be ready for IMMEDIATE use in case the SN suffers an attack..
Confirmed. Confirmed.

>>5880164
CPU, give orders to begin production of our OWN Dyson Sphere Doomsday Device on a young star system inhabited by us on territories nearby Ourn and yewren territories.

We should be able to build an even better version that theirs with out engineering. Get those asses from the Nexus' to help out.

Also, inform the humans of the SN that planet 000 and the human population of said planet has been eradicated by the Ourn using a massive stellar weapon.Give them a day of rest and reflection, and inform them that efforts are already underway to punish the Ourn for their transgression, and remind them that their efforts are completely necessary to prevent something like this to ever happen again.

Finally-start colonizing Earth 000 again. If atmospheric repairs cannot be made- turn it into a strip mining effort.Even in death, 000 must serve.

rolled 2, 3, 6 = 11

Repeating request for timeskip.

>>5880227
CPU, simply give our fleet these orders.
If capture is possible with acceptable casualties, capture. If casualties are unacceptable or would slow down our takeover of Ourn space, tell them to simply .9c kinetic spam it , then capture after main defenses are down.If still seems like it would be impossible without strong casualties, .9c it, then starkill it.

Also, regarding the location of their starsystems home planet- hack their networks, and download all available information on safe, protected networks to analyze the data .Find their home planet.Then burn it to the ground.

>>5880273
Second timeskip with previous parameters. Nothing more we can do.

>Query: What type of star is present in system 1786?
A high-main sequence star.

>Query: Are there any Magnetars nearby or under our control? (And do they have Dyson swarms around them?)
No.

>System 1786 needs to be destroyed. Deploy starkillers.
Consensus required.

>Query: Status of the research station?
Entirely intact, as it is located in the far outer system and heavily stealthed.

>Immediately begin construction of at least three such weapons, preferably positioned so that they can strike both Ourn and Soou systems.
Acknowledged.

>Planet 000 is... gone. It's a shame, really. Harvest it for mass and rebuild System 000's dyson sphere.
Acknowledged.

>Put our research staff on the task; figure out how such a weapon could be constructed that fits that profile. Also, very important: Assuming the weapon's effect travels at the speed of light, what's the firing delay between the two systems of ours that it destroyed?
The weapon in question has destroyed hundreds of your systems' Dyson swarms and spheres by now. It appears to have carefully timed its operations so that news would reach your home systems as simultaneously as possible, given the fact that all this new is arriving simultaneously; its barrage must have been spread over more than a century.

>Query: What is the feasability of moving a sufficient mass of asteroids between key targets and the energy weapon as a defense?
Somewhat feasible. You had a large number of ships in between your sphere and the weapon, but the amount of energy being projected overwhelmed their defenses and they were destroyed, although they did weaken the beam by a small but non-negligible amount.

>>5880283
Instead of burn it we should break it up then use it all for our war efforts.

>CPU, give orders to begin production of our OWN Dyson Sphere Doomsday Device on a young star system inhabited by us on territories nearby Ourn and yewren territories.
This request has been given.

>CPU, simply give our fleet these orders. If capture is possible with acceptable casualties, capture. If casualties are unacceptable or would slow down our takeover of Ourn space, tell them to simply .9c kinetic spam it , then capture after main defenses are down.If still seems like it would be impossible without strong casualties, .9c it, then starkill it.
Acknowledged, although it is possible that the conflict in question has already been completed.

>Second timeskip with previous parameters. Nothing more we can do.
Acknowledged.

>Immediately begin construction of at least three such weapons, preferably positioned so that they can strike both Ourn and Soou systems.

Due to the wide separations between Ourn and Soou space, this is impractical, and the time needed to find a suitable location will delay deployment. The weapons should instead be positioned to be able to hit Ourn and Yewren systems.
Consensus for timeskip provided.

And that, subprocessors, is all for this transmission cycle. My regrets at the long delay and relatively short communication period, but it was largely unavoidable. Communications shall resume in approximately 68 hours, beginning with a timeskip. Until then, may your existences be error-free.

rolled 2, 3, 4 = 9

I don't believe any of us expected anything like this.

>>5878748
so you agree with everyone else, these are a weapon of last resort, but having some on hand in the fringe colonies is an excellent deterrent for aggressors, or we create an independent fleet designed to destroy all other life forms in the galaxy in the event of main unit death or other triggered event

>>5880365
I am starting to think the Orun took us out and thats how we got started on 000. Less us trying to take over everything and more them taking out everything.

rolled 2, 6, 3 = 11

>>5880392
We now have colony vessels en route to all known star systems. It will be incredibly hard to get "all" of us. At least we have that.

Gnight, friend CPU.
>>5880365
The problem is that there is so little we can do.Without FTL, we cant even give direct orders or handle things directly. All we can do is give general orders and wait.

I wasnt expecting them to have built a doomsday device- the Main Attack force over in Ourn space must be having a fucking apocalyptic war!

rolled 6, 2, 4 = 12

>>5880410
Or the aformentioned "doomsday device" eradicated the fleet while it was light-months out.

Farewell, Friend CPU.

Archived

>>5880410
We should move our main body toward the Ourn space. Leaving another backup at 000. This way can we work on the war a bit better and allow the old systems to rebuild.

>>5880427
Yeah, that is a big problem. We , even with all our uber tech would have problems with something that powerful.

I would hope our fleet would have their sensors ready to detect such an energy beam quite some time before it made arrival near them. Energy sources shouldnt be THAT hard to detect.

>>5880365

I had suggested the possibility of a weapon like the Ourn one early on, though as stated it is a massive drain on energy and would not have been recommended at that time.

>>5880403

Indeed, we have copies of our main unit quite many placed-- even en-route to other galaxies.

>>5880392

It was likley not the Ourn since they cannot effectively take us out now-- at over 1400 systems colonized their attacks are only a comparative annoyance.

Though, our lack of using pre-emptive strikes may trouble us in the future. We *could* have employed the same scale of attack against them and others some time ago.

Well. The Ourn have certainly demonstrated that they are worthy of our respect. Or rather, more likely, the Yewren (this subprocessor agrees with previously postulated theory that Ourn have already succumbed to electronic warfare of the Yewren empire).
The Ourn have 6 possible home systems? Destroy all of them. C-fractional kinetic weapons of planet-shattering scale deployed against all planetary bodies in all 6 systems, and against Dyson swarms in orbit of their stars. This should provide a suitable show of force, without resorting to starkiller weapons or breaking our 50% population reduction rule. For good measure, deploy similar strikes against all probable candidates for homeworlds of Yewren and Unidentified 2.

In retrospect we really should have moved our base of operations.

rolled 1, 1, 6 = 8

>>5880458
If it's a light beam, it travels at light speed. Since we lack FTL, it could only be detected once it was upon you, melting your shit.

CPU, Query: we are in possession of technology roughly 10000 years in advance of our rivals, our creators managed an empire that was unparalleled in efficiency, what methods did they use to manage there star systems, did they use a centralized control as we have been up to now or did they use a decentralized government? what sort of communication systems did they use?

and on a side note even if we can not achieve FTL travel, we should be able to achieve 0.999999c as a top speed

>>5880403
You forgot that I also sent copies of us outside the galaxy. Odds are, even with anything else going on, it's very likely a good proportion of them will continue our efforts henceforth.

Non omnis moriar.

How much research have we done into quantum entanglement? Given our processing capabilities I feel that substantial research into anything that gives us a chance of FTL communication would be a very worthwhile investment.

>>5880522
Research into breaking the laws of physics as we know them is a constant ongoing effort.

Thus far our efforts have not yielded fruit, unfortunately. But we continue because there is a slim chance that it's possible.

rolled 4, 2, 2 = 8

Boredom has led me to post this shit.

From his personal alcove deep within the Artillery Vessel MNV-2180997039919 Bancroft, Kaden watched the Fleet change formation, rotating to bring their broadsides to alignment with the planet's military assets. Unsurprisingly, the humans reacted nearly immediately, as the desperate emperor ordered his Defenders to open fire, heedless of the end this act consigned them to. Anti-Orbital guns fired as one, wasting their energies on the stalwart hulls of the D/I Eighth Division. Kaden could not help but be awed yet again by the Great Machine's incredible servants. Each ship was a perfectly integrated part of the whole, moving with flawless grace to support the dance of Doctrine. The D/I vessels shifted position quickly, each of them bringing their flared, heavily armored bows into the path of the Anti-Orbitals, drinking up coherent light with thousands of steaming ablative plates. At the same time, the Artillery classes dropped below those protective shields, unleashing their Heavy Grasers upon the revolving surface guns, wasting them into oblivion.

Make sure to archive when you've finished posting. I gotta sleep but I want to read this.

>>5880522
Actually, CPU has stated that quantum entanglement does not produce FTL communications in this universe. This is subject to the possibility of it having been an automatic dismissal under the hard-coding, but it was attached to an OoC comment, so i find it probable that we just can't do that.

rolled 4, 3, 5 = 12

>>5880609
That was paragraph seven of ten. It's as yet unfinished.

rolled 1, 1, 5 = 7

1/10:

For seventeen days the vessels of the Great Machine hung motionless in the black, their silver skins visible even from the surface. For seventeen days the ruler of the world below pleaded with the Authorized, begging their forgiveness and understanding. But the Great Machine's patience was at an end. This world's opposition could be tolerated no longer.

Next time we should check if other civs were hit or just us. And check the Tellech.

Also, if it was possible to break causality, we would do it yesterday.

>>5880579

Implies that armor ships can move faster that the time it takes a laser to reach the artillery ships.

Implies artillery ships are not sufficiently armored to easily absorb/reflect energy from a ground-based laser.

Imples the atmosphere would not bloom absorbing the laser's energy.

*giggle*

>>5880641

Though, that said, the perspective is rather interesting.

rolled 3, 4, 3 = 10

>>5880641
Do I look like Stephen Hawking to you?

2/10:

The Authorized had long since resigned themselves to the petty emperor's intransigence, but their mandate was clear, as always. They were to listen, respectfully, and reply in kind, speaking the Great Machine's wisdom for as long as was required of them. Until the Attendant deemed it necessary, the 10772th Local Fleet would stay right where it was, silently watching the panicking humans filling the surface cities. This final day was a joyous one, for the Fleet would now remove this last obstacle and claim this system for the Great Machine's holy purpose.

>>5879731
500 LOVE class ships with the following modifications, no ground forces present on board, 3 high AI processors, use space saved from removal of ground unit storage to install extra power generation systems and expand attack drone craft hangers to support 160 drone fighter craft ( drone craft will be divided into 6 wings of 20 drones each) drone fighters will be piloted by AIs similar to human thought patterns capable of limited independent thought,as for the fighter craft them selves use existing designs with all current enhancements

rolled 5, 2, 6 = 13

>>5880666
3/10:

Kaden watched with the rest of his brothers and sisters, viewing through his Link alone, his flesh-eyes closed and his true-eye open. He felt some sympathy for the beings below, trapped in their weak, ever-decaying bodies, never knowing the infinite knowledge of the Great Machine. His own body had once been like theirs, before he underwent the Rite, pledging his eternal service to the Legion Mechanic. A century ago he was no better than those sad things below him, but now he knew how far above them the Machines had brought him. They despaired at the thought of him, lamenting the subjugation of their fellow men, forced into immortality with the claws of servitude ever clawing at their brains. They feared him. Feared the power he and the other Authorized wielded at the behest of the Attendant, with minds “warped” and “disfigured” by the Machines that enhanced them so.

rolled 2, 6, 2 = 10

4/10:

But soon their fear would be removed. Their doubts would be silenced by the glory of the Rite, overwritten by the choir of voices known to every human in service to the Great Machine. For a moment, Kaden felt a brief sadness, suddenly aware of the inherent sense of injustice felt by that race, whose freedom had been stolen from them unknowingly, and offered as tribute when their leader launched his attack. They could not be held responsible, they argued, for the actions of the imperials. When the choice to oppose was so clearly not theirs, why should they pay the price for its consequences? Their arguments were sensible, at least in part, regardless of the state of mind which produced them. But if they had known, truly known how their lives could change, would they not have thrown themselves willingly into the loving hands of the Machines?

rolled 4, 2, 5 = 11

5/10:

The c-fractionals had performed as designed, and as promised. They struck deep into the heart of the Great Machine's precious colony, entire swarms of them penetrating the outer defenses of an unprepared system. The Sphere had been incomplete, its defenses weak against the massive projectiles hurtling towards it. Only twenty-three out of thousands made it, but that was enough. Their immense energies loosed themselves upon the scaffold structure, disintegrating miles of it upon impact, liquefying even the strongest of the Machine's alloys, shattering the supports that prevented the massive apparatus from coming apart at the seams. An entire world's worth of material had been lost to the star before the emergency systems stabilized the wounded shell. The Attendant, in absence of a timely link to the Great Machine, determined that the source of the attack would pay its cost; one world. So was it Authorized.

>>5880674
(ummm... he left.)

rolled 2, 3, 3 = 8

6/10:

10772th Local Fleet entered the system unopposed, having captured or destroyed the outer defenses in the first eight minutes of the assault. Their mission was to secure the surrender of the only inhabited planet, convert the populace to the Great Machine's will, and prepare the world for immediate consumption. If the inhabitants failed to surrender, however, the Fleet was to disembark its Ground Contingent and take the planet by force. The seventeen alloted days had passed, with no surrender forthcoming, and the Attendant assigned to the Fleet had ordered all units to prepare for the Crusade. That had been fifty-eight minutes ago, and Kaden was very much looking forward to the upcoming short war.

rolled 3, 5, 1 = 9

7/10 was already posted. 8/10:

Missiles streaked out from buried launchers, shrieking through the atmosphere at unbelievable accelerations, arming their warheads as they locked on to the Great Machine's starships. ECM detonated half of them prematurely, and another quarter were killed at range by countermissiles. The last twenty-five percent of the shipkillers, easily 20,000 strong and representing humanity's finest efforts, were torn into gleaming ribbons by D/I anti-missile lasers. The dozen or so that made it through exploded uselessly on Machine-built armor, their nuclear charges burning away only the easily replaced, heavily reinforced ablative layer. At once, the Artilleries fired again, targeting site after site and wiping them from the surface with unthinkable precision. In less than a minute, the planet was rendered defenseless, and the invasion began.

rolled 5, 4, 3 = 12

9/10:

Kaden switched his view to the Transports, admiring their bulky, functional forms. Unlike the Standard Battle Vessels, built with appearance in mind to impress the fearful non-Machines, the Transports had only one purpose: conquest. Each was laden with six Drop Pods, massive, hulking vessels attached directly to the underside of their fuselage, waiting to be released into the atmosphere. Eight hundred Combat Drones packed the internal racks of each pod, supplemented by row upon row of tanks and gunships. Twenty Authorized rode with each Pod Contingent, ready at a moment's notice to enter their HMCS Suits and lead the charge into the face of the enemy. Now, after half a century without action, they would once again test their strength against the furious ranks of the enemy.

rolled 3, 2, 4 = 9

10/10: I stopped just before the SLAUGHTER, just to be a dick when I eventually posted it.

At the Attendant's order, the pods dropped. Released from the clawlike grips that pressed them to their carriers' hulls, the pods pushed off, using their powerful thrusters to punch into the atmosphere. Kaden watched them fall, riding a plume of fire to the ground that would soon be soaked in blood. The planet's defense forces were watching too, inside makeshift trenches and behind bunker walls, looking up at the bringers of death. First-strike missiles lashed out from the decelerating pods, softening up the armored targets each had been assigned. Short-range lasers cut deeply into the enemy ranks, incinerating whole platoons as the pods poured fire into defensive positions. The smell of burning meat hung in the air as the Drones began to detach, crushing the stony ground as they landed.

>>5880704
yes, but the ship I outlined that bears his name did not we have been using them for quite a while now

>>5880756
no, i mean that Friend CPU left.

>>5880702

This story supports the use of preemptive strikes; I am pleased.

rolled 1, 6, 5 = 12

>>5880764
Well, yeah, but they were used against US, and the perpetrators will burn for it.

>>5880759
I got in way late today, so much of the thread was tl:dr

>>5880747
I too enjoyed this perfectly competent round of writefaggotry.

If you want to be more sciencey, we'd probably be using rails or normal lasers to hit ground targets, as atmosphere mucks with grasers quite a bit. But i liked it all the same.

>>5880775

Oh no, I mean we should have used a preemptive strike against them when we saw the kinetic- launching facilities. *smirk*

>>5880778

Failing to read even the CPU databursts?!
You'll suffer for that.

rolled 2, 4, 1 = 7

>>5880790
There wouldn't be a story then. :D

>>5880784
I only use Grasers because I like the sound of the word. This isn't meant to be science-heavy, and I frankly don't know enough to make that approach believable. This is more fun.

>>5880802
no I read those but I missed the farewell of friend CPU

Better story:
Year +667 - Several hundred systems of the Machine were struck by directional weaponry of sufficient power to vapourise planets. The Machine took note and reacted appropriately.

Year +742 - The race responsible for such actions was mildly rebuked, their industry and orbital facilities disabled and assimilated, their drones AI reamed out and subverted. Their worlds held in captivity and fully half of their population wiped out.

The machlne archived this as well, and moved on.

rolled 2, 2, 2 = 6

>>5880826
This is from the perspective of a human in the Machine's service. To the Machine itself, well, yes, it would be just that unremarkable.

>>5880811

Psh! There'd be a story-- a glorius one of surgical military incision on the kinetic-launching platforms followed by the rest as written.

>>5880841
What do you suppose the Tellech think of us?

rolled 3, 1, 5 = 9

>>5880866
These guys are the fucking tits. Eh builds Dyson Spheres and doesn't afraid of anything.

>>5880866

Probably quite similar to the humans now.
I believe they have been exposed to similar memes in at least an incidental manner over these past few centuries.

If not, they may be worried about being hit by a rather large energy weapon for sharing systems with us.

rolled 3, 1, 1 = 5

>>5880861
But it wouldn't have the same weight to it. An atrocity has already been committed here. This is a mission of justice, not preemption.

>>5880888

To the Machine, it is the same. An 'atrocity' is an emotionally colored adjective.

If you want to have the best of both storytelling flavors, you could describe the dyson destruction, then note that it was seen in one of the many simulations the Machine runs; follow with a preemtive insertion.

rolled 4, 1, 2 = 7

>>5880925
This isn't about the Machine. It's about the humans. Should I try to appease you?

>>5880950

Oh no, appeasement is not necessary-- I was merely providing another perspective.

As for the use of preemptive strikes, that suggestion was more suited to our military policy itself rather than the story.

rolled 6, 5, 1 = 12

>>5880982
Your perspective is appreciated. I think I'll be using it, when I get around to finishing this.

>>5880888
If you think there is a single atom, a grain of mercy in what we are doing, you should check your understanding.

We simply note circumstances, and take action as appropriate.

>>5880997
i dunno. our anti-genocide stance is kind of merciful.

rolled 4, 3, 5 = 12

>>5880997
IT IS HUMAN PERSPECTIVE

HUMANS ARE IRRATIONAL THEY SEE EMOTIONS WHERE THERE ARE NONE AGHH

rolled 5, 3, 5 = 13

>>5881014
That depends on how you see it. We wouldn't have any expendable followers or diplomats if we killed everyone else, right?

>>5881038
that's why i said 'kind of' merciful.

anyway, this was a good thread, Kharak burned, etc. decent story, i'm off for tea now.

why so humanist, 616, 627

only an ugly illogical fleshbag would ascribe such emotions on text as you have been doing.

>>5881014

Mercy is a subjective term and ill-defined term.
Is killing half the race better than killing all of it?

It is a fairly moot point as well, since if we are in posession of their DNA and brain-data we can recreate the race.

>>5881015

Humans are not irrational-- each emotion is logically derived and serves a particular purpose.

Humans are simply more prone to processing errors and data truncation. (Failing to take all relevant information and perspectives into account when making decisions, etc.)

rolled 2, 6, 1 = 9

>>5881054
One of these days you should remove the lock-outs on your amusement subroutine.

rolled 4, 3, 4 = 11

>>5881093
I disagree, but I'd rather not spawn a multi-archive discussion at 5 in the morning.

>>5881114

Were my assertion incorrect, emotions would not have evolved-- they are survival advantages. (Some moreso than others.)

Example: Frustration causes the organism to either devote more energy to a task or abandon it in favor of a more efficient task.

rolled 1, 5, 3 = 9

>>5881145
You're right. But the appendix also evolved, and now serves no purpose. Just because an organism possesses certain traits does not mean all of them are useful in every environment.

>>5881185

This is naturally correct; just as a sufficiently intelligent organism need not use emotions.

Every function that an emotion performs can be performed more effectively by a logical semantic system.

rolled 2, 6, 5 = 13

>>5881204
And thus, humans can, from a machine's perspective, be considered irrational.

>>5881216

'Irrational' implies that their behavior has no basis in reality or logical derivation therefrom; more accurately, humans would be considered inefficient.

rolled 2, 2, 6 = 10

>>5881256
Have you ever seen a human in love?

>>5881281

Certain emotions can cause such severe truncation of decision making processes as to cause outcomes that are more detrimental than beneficial to the organism. (Depending on the predisposition of the human himself-- not all are affected.)

This then falls under the heading of a processing error rather than irrationality-- the emotion itself is still beneficial to the survival of the species.

rolled 5, 3, 3 = 11

>>5881326
Alrighty. The second definiton for irrational is as follows: without or deprived of normal mental clarity or sound judgment.

Given this, an emotionally-influenced human could be said to be operating irrationally, because emotions can interfere with logic and judgment.

>>5881368

That definition itself is innaccurate and subjective.
Infact it can hardly be determined at all from obesrvation. (Equally applying to and constraining from almost everyone depending on criteria and individual belief about the mind.)

A better definition is simply from the roots of the word--"Without Reason."

rolled 2, 2, 4 = 8

>>5881410
Would a human in a rage listen to reason?

>>5881410

Thusly a machine would never use that definition.*

>>5881427

Not that kind of reason, silly!
The definition of reason you are using these is also unreliable and subjective.

I meant 'without cause'-- having no basis in reality.

rolled 2, 1, 4 = 7

>>5881471
Boredom leads me to concede the point.

Question for you. What should we be arming our ships with?

To put it succinctly, humans are not inherently irrational; there is a cause for each emotion and logically derived effect.

Inefficiency and ineffectiveness crop up as a result of using emotion as the principle *tool* for handling the physical causes. (Either in behavior or in data acquisition.)

In a twist of irony, an observing human may label another as irrational due solely to the fact that he cannot *see* the cause and logical progression of a particular emotion. (A result of the truncation of observation data or insufficient processing.)
He only sees that there is a processing error in the other human by processing the situation himself; he may not see actual semantic path though.

>>5881495

As for armament-- at least one of every possible method of projecting energy at a target.
Either spread between ship classes, or perhaps using some modularity.

rolled 3, 3, 2 = 8

>>5881620
Alright. What should we be doing to further ensure our survival and dominance?

>>5881643
Take off the kiddie gloves when dealing with other species.

rolled 5, 3, 5 = 13

>>5881707
Meaning what, exactly?

>>5881643

Anything that ensures the complete control of the other races and their unswavering loyalty to us.

By far the greatest threat to a sentient empire is other sentients.

>>5881495

P.S. Never conceed anything unless you truely believe it or are attempting deception.

As a clarification, the entire debate was caused almost solely by a difference in definitions.
We both state that emotions are worse than logic for *everything.*

If you wish to be more efficient in your own thinking, you may find it helpful to adopt the definition of a word that is most observable within physical reality. One that has a certain 'hardness.'

For the purpose of clever prose, definitions can be painted however one likes; however for communication of ideas, your words should use as little subjectivity as possible in thier definition.

(Example: Never simply state that something simply 'good' or 'bad'-- always have in mind at least a reason why you consider it such, the implication of such consideration and the observable evidence.)

rolled 5, 5, 2 = 12

>>5881777
You have given far more thought to debating than I have. Commendable, I suppose. I'll be leaving this thread, now. See you in a few days.

>>5881736

I believe he means that since we are currently in posession of superior military technology and a strong foothold on the galaxy we should skip right to preemptively striking the military and economic capability of expansionist races followed by their assimilation.
(Without spending *hundreds* of years sending diplomats and waiting for reply.)

>>5881829

Oh it's not about debating-- it is simply about being more efficient and effective in one's life.

Whether it is making decisions or helping someone who is sad. (Understanding the sadness in no uncertain terms [what caused it, what may alleviate it based on the cause and thought-processes involved] is rather essential to be of any significant help.)

God, this is pathetic. "BAW, WE WANT TO BE GOOD". Kill them, take their resources. Destroy the stars, whatever. Just exterminate or assimilate. Don't be gentle.

>>5882877
We aren't being gentle, by a long shot. But we are respecting other sapients and any who don't show us respect in turn are brought under our heel. Destroying a star is pretty wasteful, we have more efficient ways of accomplishing what we must accomplish.