Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 144.1
edited by Matthias Haan
on 2026/02/13 16:04
Change comment: There is no comment for this version
To version 146.1
edited by Matthias Haan
on 2026/02/17 13:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -23,6 +23,8 @@
23 23  === Version 9.00 ===
24 24  
25 25  (% class="table-striped" %)
26 +|(% colspan="1" style="width:117px" %)Assets|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Added **overheatcooldelay** property to **<heat>** of weapons, changed functionality of **cooldelay**
27 +|(% colspan="6" style="width:117px" %)**cooldelay** now optionally defines a delay between firing a non-overheating shot and the cooldown starting, **overheatcooldelay** is an additional penalty delay when the weapon overheats.
26 26  |(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed script action **<get_highest_resource_yield>**
27 27  |(% colspan="6" style="width:117px" %)A new property that can be used in its place is **$sector.bestyieldrating.{$ware}**.
28 28  |(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed **<find_asteroid_in_cluster>** and **<find_recyclable_in_cluster>**
... ... @@ -29,20 +29,12 @@
29 29  |(% colspan="6" style="width:117px" %)**<find_asteroid_with_yield_in_sector>** and **<find_recyclable_with_yield_in_sector>** should now be used instead.
30 30  |(% colspan="1" style="width:117px" %)Parameters|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed **<yielddensities>** from **<miningparams>**
31 31  |(% colspan="6" style="width:117px" %)It has been replaced with the new **<resources>** node.
32 -|(% colspan="1" style="width:117px" %)Libraries|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)**region_definitions.xml** no longer contains **<resources>** nodes
33 -|(% colspan="6" style="width:117px" %)Instead of defining resources in regions, they're now defined via resource areas in sectors (see **mapdefaults.xml**). Regions can still have some control by defining **<allowedyields>**.
34 -|(% colspan="1" style="width:117px" %)Libraries|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)**region_definitions.xml** no longer contains **<scaneffect>** nodes
35 -|(% colspan="6" style="width:117px" %)This is now defined in resource area definitions in **resourceyields.xml**
34 +|(% colspan="1" style="width:117px" %)Libraries|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)**region_definitions.xml** no longer contains **<resources>** or **<scaneffect> **nodes
35 +|(% colspan="6" style="width:117px" %)Instead of defining resources in regions, they're now defined via resource areas in sectors (see **mapdefaults.xml** and **resourceyields.xml**). Regions can still have some control by defining **<allowedyields>**.
36 36  |(% colspan="1" style="width:117px" %)Libraries|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)**regionyields.xml** has a completely different structure
37 37  |(% colspan="6" style="width:117px" %)It now contains definitions of resource areas referenced by sector properties (see **mapdefaults.xml**).
38 -|(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed **$resourceprobe.currentbestyield**
39 -|(% colspan="6" style="width:117px" %)A new property that can be used in its place is **$resourceprobe.bestyieldrating**.
40 -|(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed **$resourceprobe.maxyield**
41 -|(% colspan="6" style="width:117px" %)Maximum yields are no longer relevant in 9.00.
42 -|(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed **$galaxy.yieldthresholds**
43 -|(% colspan="6" style="width:117px" %)Yields thresholds are no longer a thing in 9.00.
44 -|(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed **$sector.averagemaxyield**
45 -|(% colspan="6" style="width:117px" %)A new property that  can be used in its place are **$sector.yieldrating.{$ware}**.
38 +|(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed **$resourceprobe.currentbestyield** and **.maxyield**, **$sector.averagemaxyield**, and **$galaxy.yieldthresholds**
39 +|(% colspan="6" style="width:117px" %)New properties that can be used are **$resourceprobe.bestyieldrating** and **$sector.yieldrating.{$ware}**. Yields thresholds are no longer a thing in 9.00.
46 46  |(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed **flags **attribute from action **<add_blueprints>**
47 47  |(% colspan="6" style="width:117px" %)(((
48 48  The flags attribute is no longer available in the MD action <add_blueprints>