Elite Wiki - Recent changes [en]

Roolite

Cholmondely — Thu, 30 Apr 2026 07:18:38 GMT

‎Selected gems from Roolite: Added a little more

Common Testing

Hiran — Wed, 29 Apr 2026 19:48:26 GMT

‎Comparison

Factions OXP

Phkb — Wed, 29 Apr 2026 14:27:33 GMT

File:Factions 1.13.oxz

Phkb — Wed, 29 Apr 2026 14:25:03 GMT

Phkb uploaded File:Factions 1.13.oxz

New page

Diplomacy Engine API

Cholmondely — Wed, 29 Apr 2026 12:35:02 GMT

Added Links

Diplomancy OXP

Cholmondely — Wed, 29 Apr 2026 12:28:32 GMT

‎What's currently implemented technically?: Added link

Diplomacy Engine API

Cholmondely — Wed, 29 Apr 2026 12:27:42 GMT

Page created

New page

=== OVERVIEW ===
This wiki page is copied from Cdr [[User:Day|Day]]'s "Diplomacy_EngineAPI_readme.txt" included inside his OXP.

There are a couple of references to this API in his "Diplomacy_roadmap.txt" which merely mention the need to complete it.

He changed the name of his OXP from Diplomacy to [[Diplomancy]] back in 2021

=== NOTE ===
FIXME reintegrate this to DayDiplomacy_JsDocDiplomacy.js

=== EventType ===
An 'EventType' is a string defined by an oxp developer. As an example, the system taxation EventType is "SELFTAX".
EventTypes are stored in an ordered array, so that "Event"s' "Response"s and "Action"s may be executed in a designed order
(for example, "VICTORY" should follow "ATTACK" and not happen before :) ).
For a same EventType, recurrent "Action"s are executed before "Event"s.

=== ActorType ===
An 'ActorType' is a string defined by an oxp developer. As an example, the system ActorType is "SYSTEM".

ActorTypes are stored in an ordered array, so that "Event"s' "Response"s and "Action"s may be executed in a designed order
(for example, "SYSTEM"s should act before "ALLIANCE"s as information come to alliances through their systems :) ).

For a same ActorType, recurrent "Action"s are executed before "Event"s.

=== Action ===
An "Action" may be said init (only executed once at the creation of an Actor) or recurring (executed each turn).

An "Action" encapsulates a function, which typically will fire Events, or act onto the Oolite world.

It contains: an 'EventType', an 'ActorType' (whose kind of actors will execute this action?), and a function.

=== Event ===
An "Event" is something done by an "Actor", to which other Actors may react by some "Response"s.

It contains: an 'EventType', the acting Actor id, and some args to be used by the Responses (defined by the oxp developer).

=== Actor ===
An "Actor" is everything which should react to events. Systems are Actors, Alliances will be.

It contains : an 'ActorType', the Actor id, its responses, and the observing other actors' ids.

An Actor observer is another actor which may react onto that actor events.

This is useful so that for example only near systems may react to an event, and not far away systems.

It's useful to limit the cpu load too by at least a factor 100.

=== Response ===
A "Response" encapsulates a function.

It contains: an Id, the 'EventType' to which it responds, the 'ActorType' of actors which will use this response, and a function which may use the args given in the event.

=== Timing ===
When docked in station, once every 10 frames, an action (event, response, etc) is realized.

A 'turn' of events is allowed each jump.

Before beginning a new 'turn', all the actions of the precedent turn have been realized.

[[Category:OXP API's]]

Category:OXP API's

Cholmondely — Wed, 29 Apr 2026 12:13:35 GMT

Oops!

Diplomancy OXP

Cholmondely — Wed, 29 Apr 2026 12:06:58 GMT

Updated download details

Defence Rider Drones OXZ

Reval — Wed, 29 Apr 2026 12:04:54 GMT

corrected minimum Oolite version required

Diplomancy OXP

Cholmondely — Wed, 29 Apr 2026 12:02:14 GMT

Tweaks, added more about WarZones

Custom Populator OXP

Cholmondely — Wed, 29 Apr 2026 11:07:33 GMT

Added license details & requirements

Guide to Unlisted OXPs

Cholmondely — Wed, 29 Apr 2026 10:42:46 GMT

‎Utilities & Oddities: Added Phkb's Custom Populator OXP

Custom Populator OXP

Cholmondely — Wed, 29 Apr 2026 10:39:40 GMT

Oops!

Custom Populator OXP

Cholmondely — Wed, 29 Apr 2026 10:36:14 GMT

Page created

New page

A utility: Creates a customised population for [[Lave]], used for testing
== Overview ==
*You will need to use the [[Debug OXP|Debug Console]] - available with the TR & Nightly versions of the Oolite game.

*This OXP is currently set to spawn ''these'' ships between the witchpoint beacon and the planet.
pirates: 50,
police: 50,
traders: 100,
thargoids: 20,
asteroids: 50,

To alter these settings, use the debug console.

To count how many are ''actually'' spawned (which will vary slightly from the settings) try these commands in the Debug console:
system.countShipsWithRole("trader")
system.countShipsWithRole("police")
system.countShipsWithRole("pirate")
system.countShipsWithRole("thargoid")

For more details see Phkb's explanations in Hiran's [https://bb.oolite.space/viewtopic.php?t=22091 BB thread]

== Download ==
*[https://app.box.com/s/5xbksy48qr9cp31z2wpef6wjla05s3ih Phkb's Oolite Box] - look in his "miscellaneous" folder.

== Links ==
*Author: [[User:Phkb]]
*[https://bb.oolite.space/viewtopic.php?t=22091 CustomPopulator.oxp] Hiran's query thread (2026)

[[Category:Oolite utilities]]
{{misc-OXP}}

Oolite System Populator

Cholmondely — Wed, 29 Apr 2026 10:20:44 GMT

‎Links: Added Custom Populator

Defence Rider Drones OXZ

Reval — Wed, 29 Apr 2026 10:15:46 GMT

Police Player OXZ

Reval — Wed, 29 Apr 2026 03:25:26 GMT

Police Player OXZ

Reval — Wed, 29 Apr 2026 03:24:28 GMT

This OXP is so tiny and simple it barely merits a separate Wiki page. But it is so effective that it should be used!

New page

== Become an Enforcer ==

The most notable observed effect of this tiny tweak is that ships of class Pirate no longer openly threaten or attack the player's ship. You are essentially transformed into a police vigilante, or proxy copper.

Thanks to Phkb for the idea!

== Pairs nicely with: ==

* [[Defence Rider Drones OXZ|'''Defence Rider Drones''']]

* [[Police IFF Scanner Upgrade|'''IFF Police Scanner Upgrade''']]

== Police Player Download ==

Drop this file into your Oolite AddOns folder:

https://wiki.alioth.net/img_auth.php/7/74/Police_Player.oxz

== Quick Facts ==

{{IconOXP|ooVersion="1.79"|oxpCPU="Low"|oxpMEM="Average"|oxpGPU="Low"}}

[[File:Tag-colour-blue.png]]
{{OXPLevel|1}}{{Infobox OXPb| title = Police Player
|version = 1.0
|release = 2026-04-28
|features = Eases Combat
|license = CC BY-NC-SA 4
|category = Mechanics OXPs
|author = [[User:Reval|Reval]]
}}

File:Police Player.oxz

Reval — Wed, 29 Apr 2026 03:08:16 GMT

Reval uploaded File:Police Player.oxz Forces all RoleWeights of the player to be 'police'. The most notable observed effect of this tiny tweak is that ships of class Pirate no longer openly threaten or attack the player's ship. You are essentially transformed into a police vigilante, or pr...

New page

== Summary ==
Forces all RoleWeights of the player to be 'police'. The most notable observed effect of this tiny tweak is that ships of class Pirate no longer openly threaten or attack the player's ship. You are essentially transformed into a police vigilante, or proxy copper.

Defence Rider Drones OXZ

Reval — Tue, 28 Apr 2026 12:20:22 GMT

File:Defence Rider Drones.oxz

Reval — Tue, 28 Apr 2026 10:00:28 GMT

Reval uploaded File:Defence Rider Drones.oxz Galcop authorizes you to carry Mambita Defence Rider Drones, these weapons to be deployed from hardpoints on your ship's hull. A Rider's single purpose is to eliminate your attackers or any other Offender you target or fire upon.

New page

== Summary ==
Galcop authorizes you to carry Mambita Defence Rider Drones, these weapons to be deployed from hardpoints on your ship's hull. A Rider's single purpose is to eliminate your attackers or any other Offender you target or fire upon.

Defence Rider Drones OXZ

Reval — Tue, 28 Apr 2026 09:57:01 GMT

Download link for zipped OXP

File:Defence Rider Drones.oxp.zip

Reval — Tue, 28 Apr 2026 09:51:21 GMT

Reval uploaded a new version of File:Defence Rider Drones.oxp.zip Galcop authorizes you to carry Mambita Defence Rider Drones, these weapons to be deployed from hardpoints on your ship's hull. A Rider's single purpose is to eliminate your attackers or any other Offender you target or fire upon.

New page

File:Defence Rider Drones.oxp.zip

Reval — Tue, 28 Apr 2026 09:46:08 GMT

Reval uploaded File:Defence Rider Drones.oxp.zip Galcop authorizes you to carry Mambita Defence Rider Drones, these weapons to be deployed from hardpoints on your ship's hull. A Rider's single purpose is to eliminate your attackers or any other Offender you target or fire upon.

New page

Defence Rider Drones OXZ

Reval — Tue, 28 Apr 2026 09:37:31 GMT

Defence Rider Drones OXZ

Reval — Tue, 28 Apr 2026 08:59:33 GMT

creation of Defence Rider Drones OXZ page

New page

== Downsizing ==

Galcop, in a final drive to economize on personnel and vehicles (particularly its costly Police Viper and Viper Interceptor models), sanctioned the galaxy-wide production and adoption of a smaller, cheaper enforcement platform.

The result, under consultation with several manufacturers, primarily FE Shipyards, is the Mambita - a fully autonomous reduced-scale defence craft, dubbed Ship Defence Drone (SDD).

For the project, FE Shipyards took its proven Mamba II design, scaled down its hull to less than half the size of the original and dispensed with the need for an organic pilot, integrating instead advanced robotic AI systems, all of which can be mass-produced. The SDD Mambita's internals are almost wholly taken up by a powerful - for an organic, 'too powerful' would be understating the case - non-Hyperspace engine. What remains houses a laser mounting of military specification.

Mambita SDD is a fire-and-forget weapon, in effect, and belongs officially to the Mine-class, being too light in mass to lock or hinder any vessel.

Police forces have begun a gradual phase-out of their manned Viper patrol vehicles, and are introducing artfully programmed Mambitas to take their place. Remaining Vipers are being modified to carry Mambita SDDs as Rider drones, couched along the mothership's underside, to be released and recalled when occasion demands.

Trials have proven an outstanding success. The Mambita's speed and acceleration, turn rate, and reaction-time, outstrip those of opponent ships, and their miniaturized electromagnetic and visual profile renders the drones hard to detect and hit. Loss rates are low, far lower than those of manned Vipers in dangerous systems. The SDD's future looks bright.

'Drop a drone' is becoming a popular phrase not only among the shrinking Galcop Police Corps, but increasingly among non-uniformed crews. And thereby hangs another tale...

== Civilian SDD ==

At some stage in the project, an unknown Galcop nabob had a brainwave: A de facto space police force might soon become unnecessary. All that would be required was licensing - a stringent, Galcop controlled form of licensing, granted; a licensing of SDD for the use of approved civilian vessels. A trader vessel, for example, sporting its own Rider drone hardpoints and Mambita complement, could effectively carry its own police enforcers along with it.

Plans were quickly realized for the formation of a new Civilian SDD Authority, whose responsibilities include approval and licensing of applicants, along with outsourcing of Mambita production for the general market. All accompanied by the close and seamless integration of the 'product' not only with individual ship systems, but with the Galcop communications network itself, every aspect of SDD deployment to be monitored and recorded.

SDD capability requires one thing and one thing only of any applicant: a clean and spotless Galcop record and a history of compliance with galactic laws.

The SDD Authority, once satisfied, will grant approval and a duly legitimized licence for the carrying of Rider drones. There is little room for abuse of the system as it has been put in place: Special codes are issued and hard-coded in to every drone alotted; no drone can function without them. Hardpoints are mated with a unique coded link; an SDD will not attach itself without such a code. Every 'drop' is recorded, every retrieval, every kill, every loss.

The SDD, as a weapon of the ship on which it is installed, and certainly not accounted a vessel or craft in its own right, but a Mine, carries out its allotted task of targetting offending vessels of its own selection or that of its mothership, and on their elimination registers a 'kill' with the on-ship and Galcop systems simultaneously. Galcop credits the launching vessel with the kill, awarding the ship its bounty plus 100 credits. Galcop regards the bonus as 'incentive to policing', but charges the licensee 100 credits for every drone lost. The dropping of a drone is accompanied by a (negligible) tax.

Some crews noticed that there can be profit in this. Some, reputedly, have become hunters using SDDs only. The Galcop Administration must be smiling. They have a free Police Force that does not require wages or great expenditure, merely ongoing production and licensing. Licensing fees swell Galcop's coffers and the spacelanes become safe for all (except offenders). Win-win.

== Onboard SDD Mechanisms ==

An automated comm-link is established with all attached SDDs on station launch.

The deployment mechanism is mated with the WEAPONs (online/offline) switch. An organic commander must toggle ship weapons ON to drop an SDD. Toggle OFF, then ON again to deploy another Mambita.

There are various ways and situations in which deployed SDDs are recalled and retrieved:

1) Manually. In flight, from the F5 ship status screen, press [x].

2) On Torus-drive engagement, all deployed drones are automatically recalled and retrieved.

3) On requesting docking clearance, any deployed SDDs are automatically recalled and retrieved.

4) On engagement of the hyperspace motor (witchdrive), all deployed drones are recalled.

== Hostile encounters ==

Frequently, on encountering a group of Offender ships, deployed drones will select appropriate targets and initiate their own attack. Whether they do will depend on the gravity of the offences the scanned group has committed or is in the process of committing.

Otherwise, when their mothership fires on an identified Offender, every deployed drone will join in attacking this target. In fact, any ship their mothership fires on will become a target, regardless of legal status. The only class of ship an SDD is prevented from attacking is a vessel of CLASS_POLICE or CLASS_PLAYER.

When the mothership receives hostile fire, drones will be assigned to attack the attacker.

When the alert condition changes to RED, any currently unengaged (idle) drones will be assigned the nearest hostile to attack.

== General SDD status and other observations ==

As already observed, the SDD Mambita is officially classed as a Mine. As a Mine it cannot mass-lock other ships.

All SDD Mambitas are identified as CLASS_POLICE, with role 'police', as they are in every sense Galcop property. Additionally, as mentioned, Galcop Police Corps increasingly assigns SDDs to its own patrols, replacing organic crew and expensive Vipers.

On the scanner, a Police SDD can be recognised by its lollipop colours flashing purple and blue. Civilian-licensed SDDs when dropped are distinguished by their red and blue flashing blips.

== SDD Charges and Credits ==

The nominal cost of a Galcop SDD Licence is 1000 credits, renewable every LY (Lave Year).

As mentioned already, each drone deployment or 'drop' carries a small tax.

Loss of a drone through destruction incurs a Galcop penalty of 100 credits.

On registration of a kill, each kill by an SDD is credited to the mothership pilot's Elite score (the SDD is a weapon fired by the mothership, just like any other missile or mine.) The mothership pilot's account is credited with the bounty on the destroyed vessel plus Galcop's 'policing incentive' bonus of 100 credits. All accounting occurs in realtime.

Thus, with the aid of SDDs, a reasonable living can be eked out through hunting Offenders insystem - a practice Galcop tacitly if not overtly encourages via its 'policing incentive'.

Oolite on Fedora Core 5

Cholmondely — Fri, 24 Apr 2026 07:44:30 GMT

Cholmondely deleted page Oolite on Fedora Core 5 content was: "{{Deleteme|Page moved. This name is unlikely.}}", and the only contributor was "Debresser" (talk)

OXP List (Test)

Cholmondely — Fri, 24 Apr 2026 07:42:56 GMT

Cholmondely deleted page OXP List (Test) content was: "{{deleteme|testpage}}"

Koneko Industries Fleet

Cholmondely — Fri, 24 Apr 2026 07:42:32 GMT

Cholmondely deleted page Koneko Industries Fleet content was: "{{deleteme|Merged into Koneko Industries OXP.}}"

Chapters hosted separately at Alioth.net

Cholmondely — Fri, 24 Apr 2026 07:40:38 GMT

Cholmondely deleted page Chapters hosted separately at Alioth.net content was: "{{deleteme|Moved into the respective articles.}}"

@@ Line 34: / Line 34: @@
 == Selected gems from Roolite ==
 === Stranger's Oeuvre ===
 *[[Strangers World]] - Stranger's suite of realistic oxp's introducing more laws of physics and astronomy to Oolite (now on Oolite too)
@@ Line 41: / Line 43: @@
 === Others ===
 *Hal's Hot Sister for "Supercobra" - see the Sounds page
-*ВПЧ produced a dozen or so Russian oxp's back in the v.1.76 - 1.77 era
+*ВПЧ produced a dozen or so Russian oxp's back in the v.1.76 - 1.77 era including his [[Gravitation OXP]]
 *[https://app.box.com/s/dyo1vedrxuyeyum3atci Tch's Box account] (2014)

@@ Line 15: / Line 15: @@
 After starting Oolite, press Shift-F to show the frame rate on the screen, then fly around.
 === Note ===
@@ Line 30: / Line 76: @@
 | 1.90/debug/.run || CustomPopulator || 360 || 800x600 || 70
 |-
-| 1.92/appimage/test  || CustomPopulator || 358 || 1024x768 || 35
+| 1.92/test/appimage  || CustomPopulator || 358 || 1024x768 || 35
 |-
 | 1.93/flatpak/release  || CustomPopulator || 360 || 1233x700 || 40

@@ Line 65: / Line 65: @@
 ==Revision History==
 Version 1.12 (20.06.2012)
 - Supporting version 1.6+ of Cabal_Common_Library, no other changes
@@ Line 95: / Line 98: @@
 ==Download==
 * [https://app.box.com/s/47f1ee7ab7b553446676 Version 1.12] from box.com
 * [http://app.box.com/s/5649f8449570ee392b3c Version 1.11] from box.com

@@ Line 41: / Line 41: @@
 The oxp contains Engines which may be use by developers to implement interesting galaxy-spanning events:
-* (main) Engine
+* (main) [[Diplomacy Engine API|Engine]]
 * War - see WarZones OXP below
 * History
@@ Line 49: / Line 49: @@
 ----
 == Effects on game ==

@@ Line 11: / Line 11: @@
 *[[CCL]] / Cabal Common Library
 :::now replaced by Library OXP
 *[[Friend or Foe]]
 :::The Friend or Foe system will allow groups of ships to work as a team independently without being setup as escorts. There is no concept of a leader or escorts/wingmen in this system. Each ship has complete autonomy and can call on help from any other team member. Each ship keeps track of who has attacked them and will ignore stray shots, ''ie'' friendly fire. Also if an attacker disappears off the scanner and later comes back the team will remember them and restart the attack run.

← Older revision		Revision as of 12:35, 29 April 2026
Line 67:		Line 67:
	Before beginning a new 'turn', all the actions of the precedent turn have been realized.		Before beginning a new 'turn', all the actions of the precedent turn have been realized.

		+
		+
		+	== Links ==
		+	*[https://github.com/DaymareOn/Diplomacy Day's Diplomacy Github site]
	[[Category:OXP API's]]		[[Category:OXP API's]]

@@ Line 548: / Line 548: @@
 *[https://bb.oolite.space/viewtopic.php?p=286468#p286468 Problems with combining the buggy Diplomancy with Bounty System OXP] (2022)
-=== New version ===
+=== Downloads ===
-*[https://app.box.com/s/ymg7crh8md63x49444e8o6rhh2srcdcz oolite.oxp.Day.Diplomacy.oxz] (Phkb 2023: v.0.19    Bugfix: Process of making peace and breaking alliances were spamming the system events and not changing anything.)
+*Version 0.21 (2026) [https://app.box.com/s/5xbksy48qr9cp31z2wpef6wjla05s3ih Phkb's Oolite Box] look in his "Mechanics" folder
 == Gameplay and Balance Indicator ==

@@ Line 141: / Line 141: @@
 == Quick Facts ==
-{{IconOXP|ooVersion="1.90"|oxpCPU="Low"|oxpMEM="Average"|oxpGPU="Low"}}
+{{IconOXP|ooVersion="1.92"|oxpCPU="Low"|oxpMEM="Average"|oxpGPU="Low"}}
 [[File:Tag-colour-blue.png]]

@@ Line 41: / Line 41: @@
 The oxp contains Engines which may be use by developers to implement interesting galaxy-spanning events:
-* (main) Engine,
+* (main) Engine
-* War,
+* War - see WarZones OXP below
-* History,
+* History
-* Systems,
+* Systems
-* Economy,
+* Economy
-* Citizenships.
+* Citizenships - see Rexebe Citizen OXP & Digebiti Subject OXP below
 ----
@@ Line 54: / Line 54: @@
 * The player is considered fugitive when in systems warring with their flag.
 * The player is refused docking in some stations when they have not the requisite visa or passport.
-* Some new ways to spend money: passports, visas.
+* Some new ways to spend money: becoming a citizen, visas.
 === Effects on game performance ===
@@ Line 86: / Line 86: @@
 ----
 == Versions history ==
 *'''v.0.19'''
-Bugfix: breaking alliances and making peace now works again.
+:Bugfix: breaking alliances and making peace now works again.
 *'''v.0.18'''
-Improvement, user-friendliness: the visa system in-game explanation is clearerer.
+:Improvement, user-friendliness: the visa system in-game explanation is clearerer.
 *'''v.0.17'''
 Improvement, user-friendliness: the visa system in-game explanation is clearer.
-<div class="mw-collapsible mw-collapsed"  data-expandtext="Show older" data-collapsetext="Hide older" style="overflow:auto;">
 *'''v.0.16'''
 :Improvement, flavor: the player is considered fugitive when in systems warring with their flag.
@@ Line 125: / Line 139: @@
 :Improvement, code consistency: Alliances scripts become War scripts.
-*'''v.0.13''' Bugfix: manifest.plist for the oxz manager.
+*'''v.0.13'''
-*'''v.0.12''' Bugfix: manifest.plist for the oxz manager.
+*'''v.0.12'''
 *'''v.0.11'''
@@ Line 163: / Line 179: @@
 :Improvement, speed: major refactor to remove closures, dereferences, JSON (de)serialization special functions.
-*'''v.0.5''' Bugfix manifest.plist for the oxz manager.
+*'''v.0.5'''
-*'''v.0.41''' Put into the oxz manager.
+*'''v.0.41'''
 *'''v.0.3'''
@@ Line 183: / Line 201: @@
 ----
 == Associated OXPs ==
-=== Rexebe Citizen ===
+=== Rexebe Citizen OXP ===
-*[https://app.box.com/s/stnhgdubo7ogn0ug3e7zqfhyksw182wz RexebeCitizen.oxz] grants citizenship of Rexebe for users of Diplomancy who want ''eg''. to try out [[Hermitage]] (Phkb, 2021)
+*[https://app.box.com/s/stnhgdubo7ogn0ug3e7zqfhyksw182wz Rexebe Citizen.oxz] grants citizenship of Rexebe for users of Diplomancy who want ''eg''. to try out [[Hermitage]] (Phkb, 2021)
-=== Digebiti Subject ===
+=== Digebiti Subject OXP ===
-*[[File:DigebitiSubject.0.92.oxp.zip|DigebitiSubject.oxp]] grants subjecthood of Digebiti for users of Diplomancy
+*[https://wiki.alioth.net/index.php/File:DigebitiSubject.0.92.oxp.zip Digebiti Subject.oxp] grants subjecthood of Digebiti for users of Diplomancy
-=== Quick Visa ===
+=== Quick Visa OXP ===
 *[[Quick-Visa]] provides horrendously expensive "Visa purchasing options" on arrival at the Witchpoint Beacon (for those forgetting to get a visa at the previous system)
-=== WarZone.oxp.hide ===
+=== War Zones OXP ===
-Hidden away inside the newer versions of Diplomancy.oxz. Look away people. Nothing to see here.
+*[https://app.box.com/s/ivyhkxdj3fnobb50fxb3v8iw6s8ew59t WarZones 1.6.oxz] creates wars between warring systems.
 ----

@@ Line 18: / Line 18: @@
   system.countShipsWithRole("thargoid")
-For more details see Phkb's explanations in Hiran's [https://bb.oolite.space/viewtopic.php?t=22091 BB thread] (use in measuring [[Frame rate]], how to remove limits on spawning asteroids, et cetera)
+For more details see Phkb's explanations in Hiran's [https://bb.oolite.space/viewtopic.php?t=22091 BB thread] (use in measuring [[Frame rate]], how to remove limits on spawning asteroids, ''et cetera'')
 == Download ==
 *[https://app.box.com/s/5xbksy48qr9cp31z2wpef6wjla05s3ih Phkb's Oolite Box] - look in his "miscellaneous" folder.
 == Links ==

@@ Line 678: / Line 678: @@
 == Utilities & Oddities ==
 *OXP Additional Cargo Space Workaround 0.1.0.oxz  - by ocz (2015). See [https://bb.oolite.space/viewtopic.php?f=3&t=17932 BB Thread]
 *[https://github.com/JensAyton/Griffification.oxp Griffification.oxp] - by [[User:Ahruman|Ahruman]] (2012) for importing Griff's ships into the then Vanilla game
 *[https://bb.oolite.space/viewtopic.php?f=4&t=14536 HUD requests .oxp] - by Norby (2013) - part of his campaign to improve Oolite HUDs.

@@ Line 56: / Line 56: @@
 *[[System Populator]] - more on this
 *[[Configurable Populator]] - OXP for adjusting some populations in-game
 *[https://bb.oolite.space/viewtopic.php?f=3&t=8117 System.addShips] (2010 BB discussion)

@@ Line 9: / Line 9: @@
 For the project, FE Shipyards took its proven Mamba II design, scaled down its hull to less than half the size of the original and dispensed with the need for an organic pilot, integrating instead '''advanced robotic AI systems''', all of which can be mass-produced. The SDD Mambita's internals are almost wholly taken up by a powerful - for any organic, 'too powerful' would be understating the case - non-Hyperspace engine. What remains houses a laser mounting of military specification.
-Mambita SDD is a fire-and-forget weapon, in effect, and belongs officially to the Mine-class, being too light in mass to lock or hinder any vessel.
+Mambita SDD is a fire-and-forget '''weapon''', in effect, and belongs officially to the Mine-class, being too light in mass to lock or hinder any vessel.
 Police forces have begun a gradual phase-out of their manned Viper patrol vehicles, and are introducing artfully programmed Mambitas to take their place. Remaining Vipers are being modified to carry Mambita SDDs as Rider drones, couched along the mothership's underside, to be released and recalled when occasion demands.
@@ Line 22: / Line 22: @@
 At some stage in this initiative, an unknown Galcop nabob had a brainwave: A de facto space police force might soon become unnecessary. All that would be required was ''licensing'' - a stringent, Galcop controlled form of licensing, granted; a licensing of SDD for the use of '''approved civilian vessels'''. A trader vessel, for example, sporting its own Rider drone hardpoints and Mambita complement, could effectively carry its own police enforcers along with it.
-Plans were quickly realized for the formation of a new '''Civilian SDD Authority''', whose responsibilities include approval and licensing of applicants, along with outsourcing of Mambita production for the general market. All accompanied by the close and seamless integration of the 'product' not only with individual ship systems, but with the Galcop communications network itself, every aspect of SDD deployment to be monitored and recorded.
+Plans were quickly actualized for the formation of a new '''Civilian SDD Authority''', whose responsibilities include screening, approval and licensing of applicants, along with outsourcing of Mambita production for the general market. All accompanied by the close and seamless integration of the 'product' not only with individual ship systems, but with the Galcop communications network itself, every aspect of SDD deployment to be monitored and recorded.
 SDD capability requires one thing and one thing only of any applicant: a clean and spotless Galcop record and a history of compliance with galactic laws.
-The SDD Authority, once satisfied, will grant approval and a duly legitimized licence for the carrying of Rider drones. There is little room for abuse of the system as it has been put in place: Special codes are issued and hardwired in to every drone allotted; no drone can function without them. Hardpoints are mated with a unique encrypted link; an SDD will not attach itself without such a code. Every 'drop' is recorded, every retrieval, every kill, every loss.
+The SDD Authority, once satisfied, will grant approval and a duly legitimized licence for the carrying of Rider drones. There is little scope for abuse of the system as it has been implemented: Special codes are issued and hardwired in to every drone allotted; no drone can function without them. Hardpoints are mated with a unique encrypted link; an SDD will not attach itself without such a code. Every 'drop' is recorded, every retrieval, every kill, every loss.
-The SDD, as a weapon of the ship on which it is installed, and certainly not accounted a vessel or craft in its own right, but a '''Mine''', carries out its allotted task of targetting offending vessels of its own selection or that of its mothership, and on their elimination registers a 'kill' with the on-ship and Galcop systems simultaneously. Galcop credits the launching vessel with the kill, awarding the ship its bounty plus 100 credits. Galcop regards the bonus as 'incentive to policing', but charges the licensee 100 credits for every drone lost. The dropping of a drone is accompanied by a (negligible) tax.
+The SDD, as a '''weapon''' of the ship on which it is mounted, and certainly not accounted a vessel or craft in its own right, but a '''Mine''', carries out its allotted task of targetting offending vessels of its own selection or that of its mothership, and on their elimination registers a 'kill' with the on-ship and Galcop systems simultaneously. Galcop credits the launching vessel with the kill, awarding the ship its bounty plus 100 credits. Galcop regards the bonus as 'incentive to policing', but charges the licensee 100 credits for every drone lost. The dropping of a drone is accompanied by a (negligible) tax.
 Some crews noticed that there can be profit in this. Some, reputedly, have become hunters using SDDs only. Galcop Administration must be smiling. They have a free Police Force that does not require wages or great expenditure, merely ongoing production and licensing. Licensing fees swell Galcop's coffers and the spacelanes become safer for all (except offenders). Win-win.
@@ Line 73: / Line 73: @@
 The nominal cost of a Galcop SDD Licence is 1000 credits, renewable every LY (Lave Year).
 As mentioned already, each drone deployment or 'drop' carries a small tax.
@@ Line 80: / Line 82: @@
 On registration of a kill, each kill by an SDD is credited to the mothership pilot's Elite score (the SDD is a weapon fired by the mothership, just like any other missile or mine.) The mothership pilot's account is credited with the bounty on the destroyed vessel plus Galcop's 'policing incentive' bonus of 100 credits. All accounting occurs in realtime.
-Thus, with the aid of SDDs, a reasonable living can be eked out through hunting Offenders insystem - a practice Galcop tacitly if not overtly encourages via its 'policing incentive'.
+Thus, with the aid of SDDs, a reasonable living can be eked out through conscientiously hunting Offenders insystem - a practice Galcop tacitly if not overtly encourages via its 'policing incentive'.
@@ Line 132: / Line 134: @@
 * [[Police IFF Scanner Upgrade|'''IFF Police Scanner Upgrade''']]

← Older revision		Revision as of 03:25, 29 April 2026
Line 3:		Line 3:
	The most notable observed effect of this tiny tweak is that ships of class Pirate no longer openly threaten or attack the player's ship. You are essentially transformed into a police vigilante, or proxy copper.		The most notable observed effect of this tiny tweak is that ships of class Pirate no longer openly threaten or attack the player's ship. You are essentially transformed into a police vigilante, or proxy copper.

−	Thanks to Phkb ~~for the idea~~!	+	Thanks to Phkb!

@@ Line 1: / Line 1: @@
+[[Image:Griff_mamba.jpg|thumb|right|200px|<b>SDD Mambita</b> - a very little thing, a deadly insect. Galcop's new police rider drone. This one illicitly defaced with a civilian 'hunter' decal.]]
 == Downsizing ==
@@ Line 20: / Line 20: @@
 == Civilian SDD ==
-At some stage in the project, an unknown Galcop nabob had a brainwave: A de facto space police force might soon become unnecessary. All that would be required was ''licensing'' - a stringent, Galcop controlled form of licensing, granted; a licensing of SDD for the use of '''approved civilian vessels'''. A trader vessel, for example, sporting its own Rider drone hardpoints and Mambita complement, could effectively carry its own police enforcers along with it.
+At some stage in this initiative, an unknown Galcop nabob had a brainwave: A de facto space police force might soon become unnecessary. All that would be required was ''licensing'' - a stringent, Galcop controlled form of licensing, granted; a licensing of SDD for the use of '''approved civilian vessels'''. A trader vessel, for example, sporting its own Rider drone hardpoints and Mambita complement, could effectively carry its own police enforcers along with it.
 Plans were quickly realized for the formation of a new '''Civilian SDD Authority''', whose responsibilities include approval and licensing of applicants, along with outsourcing of Mambita production for the general market. All accompanied by the close and seamless integration of the 'product' not only with individual ship systems, but with the Galcop communications network itself, every aspect of SDD deployment to be monitored and recorded.
@@ Line 26: / Line 26: @@
 SDD capability requires one thing and one thing only of any applicant: a clean and spotless Galcop record and a history of compliance with galactic laws.
-The SDD Authority, once satisfied, will grant approval and a duly legitimized licence for the carrying of Rider drones. There is little room for abuse of the system as it has been put in place: Special codes are issued and hard-coded in to every drone alotted; no drone can function without them. Hardpoints are mated with a unique coded link; an SDD will not attach itself without such a code. Every 'drop' is recorded, every retrieval, every kill, every loss.
+The SDD Authority, once satisfied, will grant approval and a duly legitimized licence for the carrying of Rider drones. There is little room for abuse of the system as it has been put in place: Special codes are issued and hardwired in to every drone allotted; no drone can function without them. Hardpoints are mated with a unique encrypted link; an SDD will not attach itself without such a code. Every 'drop' is recorded, every retrieval, every kill, every loss.
 The SDD, as a weapon of the ship on which it is installed, and certainly not accounted a vessel or craft in its own right, but a '''Mine''', carries out its allotted task of targetting offending vessels of its own selection or that of its mothership, and on their elimination registers a 'kill' with the on-ship and Galcop systems simultaneously. Galcop credits the launching vessel with the kill, awarding the ship its bounty plus 100 credits. Galcop regards the bonus as 'incentive to policing', but charges the licensee 100 credits for every drone lost. The dropping of a drone is accompanied by a (negligible) tax.
-Some crews noticed that there can be profit in this. Some, reputedly, have become hunters using SDDs only. The Galcop Administration must be smiling. They have a free Police Force that does not require wages or great expenditure, merely ongoing production and licensing. Licensing fees swell Galcop's coffers and the spacelanes become safe for all (except offenders). Win-win.
+Some crews noticed that there can be profit in this. Some, reputedly, have become hunters using SDDs only. Galcop Administration must be smiling. They have a free Police Force that does not require wages or great expenditure, merely ongoing production and licensing. Licensing fees swell Galcop's coffers and the spacelanes become safer for all (except offenders). Win-win.
@@ Line 81: / Line 81: @@
 Thus, with the aid of SDDs, a reasonable living can be eked out through hunting Offenders insystem - a practice Galcop tacitly if not overtly encourages via its 'policing incentive'.
@@ Line 90: / Line 119: @@
 Simply unzip to your Oolite AddOns folder.

← Older revision		Revision as of 09:57, 28 April 2026
Line 81:		Line 81:

	Thus, with the aid of SDDs, a reasonable living can be eked out through hunting Offenders insystem - a practice Galcop tacitly if not overtly encourages via its 'policing incentive'.		Thus, with the aid of SDDs, a reasonable living can be eked out through hunting Offenders insystem - a practice Galcop tacitly if not overtly encourages via its 'policing incentive'.
		+
		+
		+	== Download ==
		+
		+	Download Version 1.0 of Defence Rider Drones (zipped OXP):
		+
		+	https://wiki.alioth.net/img_auth.php/3/3b/Defence_Rider_Drones.oxp.zip
		+
		+	Simply unzip to your Oolite AddOns folder.

@@ Line 2: / Line 2: @@
 == Downsizing ==
-Galcop, in a final drive to economize on personnel and vehicles (particularly its costly Police Viper and Viper Interceptor models), sanctioned the galaxy-wide production and adoption of a smaller, cheaper enforcement platform.
+'''Galcop''', in a final drive to economize on personnel and vehicles (particularly its costly Police Viper and Viper Interceptor models), sanctioned the galaxy-wide production and adoption of a '''smaller, cheaper enforcement platform.
-The result, under consultation with several manufacturers, primarily FE Shipyards, is the Mambita - a fully autonomous reduced-scale defence craft, dubbed Ship Defence Drone (SDD).
+The result, under consultation with several manufacturers, notably FE Shipyards, is the '''Mambita''' - a fully autonomous reduced-scale defence craft, dubbed '''Ship Defence Drone (SDD)'''.
-For the project, FE Shipyards took its proven Mamba II design, scaled down its hull to less than half the size of the original and dispensed with the need for an organic pilot, integrating instead advanced robotic AI systems, all of which can be mass-produced. The SDD Mambita's internals are almost wholly taken up by a powerful - for an organic, 'too powerful' would be understating the case - non-Hyperspace engine. What remains houses a laser mounting of military specification.
+For the project, FE Shipyards took its proven Mamba II design, scaled down its hull to less than half the size of the original and dispensed with the need for an organic pilot, integrating instead '''advanced robotic AI systems''', all of which can be mass-produced. The SDD Mambita's internals are almost wholly taken up by a powerful - for any organic, 'too powerful' would be understating the case - non-Hyperspace engine. What remains houses a laser mounting of military specification.
 Mambita SDD is a fire-and-forget weapon, in effect, and belongs officially to the Mine-class, being too light in mass to lock or hinder any vessel.
@@ Line 12: / Line 13: @@
 Police forces have begun a gradual phase-out of their manned Viper patrol vehicles, and are introducing artfully programmed Mambitas to take their place. Remaining Vipers are being modified to carry Mambita SDDs as Rider drones, couched along the mothership's underside, to be released and recalled when occasion demands.
-Trials have proven an outstanding success. The Mambita's speed and acceleration, turn rate, and reaction-time, outstrip those of opponent ships, and their miniaturized electromagnetic and visual profile renders the drones hard to detect and hit. Loss rates are low, far lower than those of manned Vipers in dangerous systems. The SDD's future looks bright.
+Trials have proven an outstanding success. The Mambita's speed and acceleration, turn rate, and reaction-time outstrip those of opponent ships, and their miniaturized electromagnetic and visual profile renders the drones '''hard to detect and hit'''. Loss rates are low, far lower than those of manned Vipers in dangerous systems. The SDD's future looks bright.
 'Drop a drone' is becoming a popular phrase not only among the shrinking Galcop Police Corps, but increasingly among non-uniformed crews. And thereby hangs another tale...
@@ Line 19: / Line 20: @@
 == Civilian SDD ==
-At some stage in the project, an unknown Galcop nabob had a brainwave: A de facto space police force might soon become unnecessary. All that would be required was licensing - a stringent, Galcop controlled form of licensing, granted; a licensing of SDD for the use of approved civilian vessels. A trader vessel, for example, sporting its own Rider drone hardpoints and Mambita complement, could effectively carry its own police enforcers along with it.
+At some stage in the project, an unknown Galcop nabob had a brainwave: A de facto space police force might soon become unnecessary. All that would be required was ''licensing'' - a stringent, Galcop controlled form of licensing, granted; a licensing of SDD for the use of '''approved civilian vessels'''. A trader vessel, for example, sporting its own Rider drone hardpoints and Mambita complement, could effectively carry its own police enforcers along with it.
-Plans were quickly realized for the formation of a new Civilian SDD Authority, whose responsibilities include approval and licensing of applicants, along with outsourcing of Mambita production for the general market. All accompanied by the close and seamless integration of the 'product' not only with individual ship systems, but with the Galcop communications network itself, every aspect of SDD deployment to be monitored and recorded.
+Plans were quickly realized for the formation of a new '''Civilian SDD Authority''', whose responsibilities include approval and licensing of applicants, along with outsourcing of Mambita production for the general market. All accompanied by the close and seamless integration of the 'product' not only with individual ship systems, but with the Galcop communications network itself, every aspect of SDD deployment to be monitored and recorded.
 SDD capability requires one thing and one thing only of any applicant: a clean and spotless Galcop record and a history of compliance with galactic laws.
@@ Line 27: / Line 28: @@
 The SDD Authority, once satisfied, will grant approval and a duly legitimized licence for the carrying of Rider drones. There is little room for abuse of the system as it has been put in place: Special codes are issued and hard-coded in to every drone alotted; no drone can function without them. Hardpoints are mated with a unique coded link; an SDD will not attach itself without such a code. Every 'drop' is recorded, every retrieval, every kill, every loss.
-The SDD, as a weapon of the ship on which it is installed, and certainly not accounted a vessel or craft in its own right, but a Mine, carries out its allotted task of targetting offending vessels of its own selection or that of its mothership, and on their elimination registers a 'kill' with the on-ship and Galcop systems simultaneously. Galcop credits the launching vessel with the kill, awarding the ship its bounty plus 100 credits. Galcop regards the bonus as 'incentive to policing', but charges the licensee 100 credits for every drone lost. The dropping of a drone is accompanied by a (negligible) tax.
+The SDD, as a weapon of the ship on which it is installed, and certainly not accounted a vessel or craft in its own right, but a '''Mine''', carries out its allotted task of targetting offending vessels of its own selection or that of its mothership, and on their elimination registers a 'kill' with the on-ship and Galcop systems simultaneously. Galcop credits the launching vessel with the kill, awarding the ship its bounty plus 100 credits. Galcop regards the bonus as 'incentive to policing', but charges the licensee 100 credits for every drone lost. The dropping of a drone is accompanied by a (negligible) tax.
 Some crews noticed that there can be profit in this. Some, reputedly, have become hunters using SDDs only. The Galcop Administration must be smiling. They have a free Police Force that does not require wages or great expenditure, merely ongoing production and licensing. Licensing fees swell Galcop's coffers and the spacelanes become safe for all (except offenders). Win-win.
@@ Line 36: / Line 37: @@
 An automated comm-link is established with all attached SDDs on station launch.
-The deployment mechanism is mated with the WEAPONs (online/offline) switch. An organic commander must toggle ship weapons ON to drop an SDD. Toggle OFF, then ON again to deploy another Mambita.
+'''The deployment mechanism is mated with the WEAPONs (online/offline) switch.''' An organic commander must toggle ship weapons ON to drop an SDD. Toggle OFF, then ON again to deploy another Mambita.
 There are various ways and situations in which deployed SDDs are recalled and retrieved:
@@ Line 62: / Line 63: @@
 == General SDD status and other observations ==
-As already observed, the SDD Mambita is officially classed as a Mine. As a Mine it cannot mass-lock other ships.
+As already observed, '''the SDD Mambita is officially classed as a Mine'''. As a Mine it cannot mass-lock other ships.
-All SDD Mambitas are identified as CLASS_POLICE, with role 'police', as they are in every sense Galcop property. Additionally, as mentioned, Galcop Police Corps increasingly assigns SDDs to its own patrols, replacing organic crew and expensive Vipers.
+All SDD Mambitas are identified as CLASS_POLICE, with role 'police', as they are in every sense '''Galcop property'''. Additionally, as mentioned, Galcop Police Corps increasingly assigns SDDs to its own patrols, replacing organic crew and expensive Vipers.
 On the scanner, a Police SDD can be recognised by its lollipop colours flashing purple and blue. Civilian-licensed SDDs when dropped are distinguished by their red and blue flashing blips.