Give Feedback
0 of 0
File information
Last updated
Original upload
Created by
kuerteeUploaded by
kuerteeVirus scan
Safe to use
Tags for this mod
Current section
Activity logs
This page was last updated on 25 February 2024, 1:42PM
- Changelogs
-
-
Version 6.0.0021
- Tweak: Allow creation of Waypoint Fields without a ship begin selected or with the player's ship selected. Previously, it required a non-player-controlled ship to be selected.
-
Version 6.0.002
- Bug-fix: When deploying with one ship, the ship was acquiring the Protect Position order - interrupting the ship's deployment orders.
-
Version 6.0.0004
- Bug-fix: Corrected fleet leader orders when deploying (if they don't have have subordinates in the Follow group) or when protecting the deploy location.
- Note: This version should work with 6.x and 5.x of the base game.
-
Version 5.1.03141
- Tweak: the Protect Position/Ship will not override any orders of the fleet leader. It's followers will still perform their deployment orders, however. E.g. you can have the fleet leader do something else while its followers perform the deployments.
-
Version 5.1.0314
- New feature: New behaviours: The ship you ordered to perform the deployment will follow the Waypoint Field and deploy the necessary equipment or weapon. But if the ship has subordinates assigned as "Followers", they will perform the deployments and the rest of the ship will defend them. Otherwise, the whole fleet will perform the deployment.
- Tweak: The manually-created Waypoint Field will now close when complete. Previously, I prevented it from closing to allow the player to use the "Abort and Retrieve" function. But the "Retrieve Deployables In Range" order has been available for several versions now.
-
Version 5.1.0305
- Bug-fix: Finding stations for resupply that obey the ship's activity and travel blacklist rules. In previous versions, the resupply simply fails causing the ship to loop between finding the same station and failing to travel to it immediately.
- Bug-fix: Finding stations with resources to build the deployable. In previous versions, stations that can supply the deployable but don't have the necessary resources were used.
-
Version 5.1.0301
- Bug-fix: Collect deployables in range no available space loop bug.
- Tweak: The "Collect deployables in range" order doesn't get removed immediately, allowing you to increase its range.
-
Version 5.1.0009
- Tweak: Better collect deployables in range.
-
Version 4.2.0809
- Bug-fix: Infinite loop resulting in a hang in Collect Deployables In Range order when there are deployables to be collected but no ship (e.g. no more room) is able to collect them.
-
Version 4.2.0808
- Bug-fix: Collect deployments in range was broken by the last update.
- Tweak: Deployables with the "maxweaponrange" property will use that instead of "maxradarrange".
- Tweak: Better size selections of the field in the UI.
- Bug-fix: Small spheres are now not discs.
- Bug-fix: Sizes were incorrectly double your chosen size.
- Bug-fix: Attach waypoint fields to objects. Previous versions would drop the field to the ecliptic plane when you try to attach it to an object (e.g. station).
-
Version 4.2.0807
- Tweak: Allow for L-sized and XL-sized ships to receive the mod's deploy orders. I didn't know that smaller ships couldn't take laser towers mark 2. Previous versions limited deployments to S-sized and M-sized ships.
- Tweak: Correct resource probes scanning range. Because their scanning range was unknown until v5.0 beta of the base game, their range was an estimation in previous versions.
-
Version 4.2.0804
- Bug-fix: Support for the impounding ship feature of the mod, Crime has Consequence. The previous version would cause the game to freeze unrecoverably when there is an active Waypoint Field mission and the player ship is impounded.
-
Version 4.2.05
- New feature: Packed density: range x 2 but with no gaps. This is only available on Waypoint Fields that are not attached to missions.
-
Version 4.2.04
- New feature: Resource Probes' optimal density is now set at 50km. From their "mouseover rings", it looks like their range is 100km. From testing, spacing them at 50km generate the best results. I.e. They start to return different values at 50km.
- New feature: Cluster Mines are available - if you have the DLC installed. I think they came with the Cradle Of Humanity DLC.
- New feature: Distance tool: The Interact Menu (i.e. right-click) shows the distance from the selected object or from the last left-click on the holo-map. This requires v4.2.03 of UI Extensions.
-
Version 4.1.0
- Bug fix: Minimised (i.e. removed, but it may still happen) the double-up of deployments on one waypoint.
- Tweak: Resource probe sizes and densities based on the 4.1 resource probe range UI. Note that I think no one really knows for sure the range of resource probes. As from one of my forum posts, this is what the range is as I understand it: "when deployed, the radius around a resource probe when you mouse-over one looks to be about 40km - the typical comm range. but the docs state that "currentyield" value is '... The current yield detected by the resource probe (volume is a cube of space with a side length of 32km) ...'. which means that the range (or radius) is 16km. but in the encyclopedia, its range is 3km." Here is a discussino about the range: https://forum.egosoft.com/viewtopic.php?f=146&t=442026&p=5079853&hilit=kuertee+probes#p5079851
-
Version 2.0.7
- New option: Auto-restock. Enabled by default. Disable it in the mod's Extension Options.
-
Version 2.0.6
- -Tweak: Missions, apart from find resources missions, no longer need to be active to create Waypoint Field missions.
-
Version 2.0.5
- Bug-fix: Restocking was taking ships to the furthest station with available stock rather than to the nearest station.
-
Version 2.0.4
- Bug-fix: NPC pilots with no wingmen and no free space to collect deployables were not removing their order, causing them to idle indefinitely.
-
Version 2.0.3
- Bug-fix: NPC pilots will not restock their deployables if you don't have enough money to pay for them.
- Tweak: Sometimes the Create Waypoint Field button is not avaiable after the mission is activated UNTIL you close then re-open the menu. This version fixes that.
-
Version 2.0.2
- New feature: NPC pilots in deploy missions now restock their deployables.
- Tweak: In the mission UI ... you now need to have the mission Active before the Create Waypoint Field button is available.
- Tweak: The Waypoint Field mission now doesn't get create automatically when you accept/receive a deployment mission.
-
Version 2.0.1
- New feature: Configurable size multiplier in the Extensions Options.
- Tweak: Player NPC ships now deploy normal mines by default. Previously, they wouldn't get away fast enough or they would trigger the mines. In this version, the mines deployed are deactivated and only activated after the waypoint field mission is complete.
- Bug-fix: Deploying laser towers or mines for a mission was sometimes getting ignored - preventing the current waypoint from completing.
- Bug-fix: The ship leader (or the ship, in the case that the ship has no wingmen) of the Collect Deployables order were sometimes not collecting deployables because it was busy searching for deployables to give its wings the order to collect. In the case of the ship not having wings, the deployables would not be collected. Fixed in this version.
- Bug-fix: Previously, if the previously deployed object is destroyed (e.g. a mine exploding), the waypoint field would never complete because the destruction caused a miscount.
-
Version 2.0.0
- New feature: updated for v4.0.0 beta 11 of the base game.
- Tweaks: Cleaned-up unnecessary localisation files. Rewrote content.xml manifest file.
- New feature: The shape, size and density of each deployable type is saved then restored on next use.
- New feature: AI order: Collect Deployables In Range. You can now order any of your ships to collect any deployable within a given area.
- Tweak: Compatibility with my other mod, "Accept mission for later". Accepting a deployment mission will not override your current active mission.
-
Version 1.2.8
- Tweak: Create Waypoint Field is now a ship order also. Right-click on the map, while a ship is selected, will order the ship to deploy.
- Tweak: "Allow Deployments" and "Pause Deployments" are now only AI-controls. The mission now leads you to each waypoint even if deployments are paused. Previously, deployments had to be allowed for the mission to lead you to each waypoint.
-
Version 1.2.7
- Tweak: Transfering the mission to a ship doesn't transfer it to their fleet's top-most commander anymore. The mission is transfered only to that ship and its wingmen.
- Tweak: Preview beacons are now based on whether their position is explored or not instead of their distance from the sector's core.
- Tweak: Manually-created Waypoint Fields do not terminate when all deployments are complete. This allows you to send an "Abort and retrieve" order.
- Tweak: Mission objective notification now follow more closely the notifications from any attached X4 mission.
- Tweak: German language file provided by EagleFour.
- Bug-fix: Another bug-fix attempt for the reassignment of player-ignored waypoints bug - that I can't seem to fix.
-
Version 1.2.6
- Tweak: Mission pings lessened. It will only ping if your waypoint changes, one of your wingmen deploys at a waypoint changing its status, or the waypoint deployable, shape, density changes.
- Bug-fix: Switching deployables now reverts to its default size and density setting - rather than acquiring the previous settings - which may not have an option in the panel for the new deployable.
- Bug-fix: Player-ignored waypoint was not getting reassigned to AI pilot.
-
Version 1.2.5
- Bug-fix: Guidance Mission bugs: "Set to active", "Set to inactive" buttons are now available. And the "Transfer mission to ..." button now work. The required UI Extensions file, kuertee_menu_map.lua, wasn't getting loaded. It worked in my environment because I have other mods that loaded that file.
- Bug-fix: Prevent crash on retrieval of deployables by the AI.
- New feature: Resource probes have larger size options (25km, 50km, 100km, 150km, 200km) and new density options (Inadequate x5, Flawed x10).
- Bug-fix: Aborting or "Aborting and retrieving" the Waypoint Field mission now activates its attached X4 mission, if one is attached.
-
Version 1.2.4
- New feature / bug-fix: "Transfer mission to ..." allows you to select the fleet that will perform the deployments. This ALSO fixes the bug that stuck the task to the one fleet - requiring you to destroy or sell the fleet leader to reset new Waypoint Field tasks to your current ship. You need the updated UI Extensions mod for this.
-
Version 1.2.3
- Bug fix: Incorrect calculation of sphere layouts for target coverages that are smaller than the optimal deployment density that was introduced in the previous bug-fix. It produced a weird cylindrical shape. This version fixes this bug properly.
-
Version 1.2.2
- Bug fix: Incorrect calculation of sphere layouts for target coverages that are smaller than the optimal deployment desnity. E.g. Achieve satelitte coverage missions of 36km radius.
- Bug-fix: The original mission group wasn't getting re-activated after the completion of one of its missions.
-
Version 1.2.1
- New feature: Wall, rectangular plane, and disc layouts.
- Tweak: Better cube and sphere layouts.
- Tweak: Manually-created Waypoint Fields will acquire the settings of the previous manually-created Waypoint Field.
- New feature: The mod's mission is now listed in the Guidance Missions tab, keeping your Plot Missions free of the helper missions created by my various mods. I recommend the use of my Ui Extensions mod (https://www.nexusmods.com/x4foundations/mods/552). Without this mod, you wont be able to switch between the missions listed in the Guidance tab.
- Tweak: Better mission and objective descriptions to follow my other helper mods of Loot mining, Ship scanner, Signal leak hunter - increasing range, and Station scanner.
- Tweak: Previously, the preview beacons may render outside the sector's known space - increasing the sector's known space. In this version, the preview beacons will render only if they are within the sector's known space.
- Bug-fix: Spacewalking stopped your wingmen from deployments. This occured because internally in the game, spacesuits are considered as ships. The mission (the Waypoint Field controller for your guidance and wingmen orders) is still limited to one ship, however. Changing ships will interrupt the previous ship's wingmen orders. But the new ship's wingmen will continue with the task. I recommend not changing ships. Doing anything else (dock, disembark, guard, fly to another sector, etc.) will not interrupt the Waypoint Field mission.
-
Version 1.2.0
- New feature: Size and density controls are enabled. They were disabled in previous versions (as shown in the code, if you look at it). I wanted to familiarise myself with the mod by actually playing with it, rather than only play-testing it, to identify the actual controls required. (Also, I knew that my previous cube/sphere layouts weren't the best. I wanted to tweak them before enabling these controls.)
- Tweak: The Waypoint Field mission only attaches to activated deployment missions. Previously, it tries to attach to the last deployment mission even if that mission wasn't active.
- Tweak: The Waypoint Field mission is auto-created only the first time the original deployment mission is activated. If you abort the Waypoint Field mission, it needs to be re-created via the original deployment mission.
- Bug-fix: Previously crashes at two points: creation of waypoint positions and at AIs retrieving deployments.
- Bug-fix: Previously, the mission update notification was incorrectly reporting the number of deployments against the total.
- Tweak: Better reassignment to an AI pilot of the player-ignored waypoint.
- Tweak: Better handling of mission abortion/completion.
- Tweak: Better handling of manually creating waypoints on the map. Previously, it auto-created a Guidance Mission (which was removed immediately when the Waypoint Field mission was activated). In this version, it doesn't need a Guidance Mission.
-
Version 1.1.0
- New feature: Create a Waypoint Field directly with a right-mouse click on the map.
- New feature: The Waypoint Field panel now lists its attached mission. "Show original mission" and "Show Waypoint Field mission" toggles between the two mission panels.
- New feature: The Waypoint Field mission (e.g. mission target, progress, etc.) is now attached to your last controlled ship. Previously, it would only work if you were in direct control of the ship. In this version, you're allowed to exit the ship to do other things.
- Tweak: Wingmen defaults to deploying Fried-Foe mines when performing mining missions. Manually order them to deploy other mines. Their AI is not very good at avoiding mines they deploy.
- Tweak: Better distribution of retrieved deployments. Previously, the first wingman would retrieve as much as they can, while the others would retrieve what remaining few.
- Tweak: Missions created from the base game's rml_achievecoverage.xml, rml_deployinplace.xml and rml_find_resources.xml files now create Waypoint Field missions. These underlying files are the base missions for the gm_* files previously used.
- Tweak: Increased horizontal interval of resource probe waypoints.
- Bug-fix: Completion of a waypoint previously failed for deployments that do not set their ownership immediately after deployment - causing wingmen to deploy multiple times on the one waypoint. E.g. laser towers.
- Bug-fix: For manually created Waypoint Fields that are attached to missions, wingmen deployment would stop after the first if the sector they are deploying is different from the sector of the mission.
- Bug-fix: Re-assignment of waypoint ignored by the player.
- Bug-fix: Previously fails when the target coverage from the missions was too small for the waypoint interval set in my mod. In this version, the area determines the intervals.
-
Version 1.0.0
- Initial release.
-
- Author's activity
-
Load more items
February 2024
-
25 Feb 2024, 1:42PM | Action by: kuertee
File added
'Russian translation [version 6.0.00211]'
April 2023
-
18 Apr 2023, 12:48PM | Action by: kuertee
File added
'kuertee_waypoint_fields_for_deployments [version 6.0.00211]'
-
18 Apr 2023, 3:24AM | Action by: kuertee
File added
'kuertee_waypoint_fields_for_deployments [version 6.0.0021]'
-
18 Apr 2023, 3:23AM | Action by: kuertee
Attribute change
'Mod version changed to 6.0.0021.'
-
18 Apr 2023, 3:23AM | Action by: kuertee
Readme file added
-
18 Apr 2023, 3:23AM | Action by: kuertee
Changelog added
'Change log added for version 6.0.0021'
-
18 Apr 2023, 3:22AM | Action by: kuertee
Attribute change
'Description changed.'
-
13 Apr 2023, 3:38PM | Action by: kuertee
Attribute change
'file visible to the public'
-
13 Apr 2023, 9:13AM | Action by: kuertee
File added
'kuertee_waypoint_fields_for_deployments [version 6.0.002]'
-
13 Apr 2023, 9:12AM | Action by: kuertee
Readme file added
-
13 Apr 2023, 9:12AM | Action by: kuertee
Changelog added
'Change log added for version 6.0.002'
-
13 Apr 2023, 9:12AM | Action by: kuertee
Attribute change
'Description changed.
Mod version changed to 6.0.002.'
-
13 Apr 2023, 9:11AM | Action by: kuertee
Attribute change
'file hidden from public viewing'
February 2023
-
18 Feb 2023, 3:01PM | Action by: kuertee
Attribute change
'file visible to the public'
-
18 Feb 2023, 2:10PM | Action by: kuertee
Attribute change
'Description changed.'
-
18 Feb 2023, 1:28PM | Action by: kuertee
File added
'kuertee_waypoint_fields_for_deployments [version 6.0.0004]'
-
18 Feb 2023, 1:26PM | Action by: kuertee
Readme file added
-
18 Feb 2023, 1:26PM | Action by: kuertee
Changelog added
'Change log added for version 6.0.0004'
-
18 Feb 2023, 1:25PM | Action by: kuertee
Attribute change
'Description changed.
Mod version changed to 6.0.0004.'
-
18 Feb 2023, 1:25PM | Action by: kuertee
Attribute change
'file hidden from public viewing'
-
- Mod page activity
-
Load more items
April 2024
-
07 Apr 2024, 10:06PM | Action by: Hellequin2
Endorsed
'Waypoint fields for deployments'
-
06 Apr 2024, 1:32AM | Action by: helloween22
Untracked
'Waypoint fields for deployments'
-
05 Apr 2024, 8:33PM | Action by: Zanzibarbarian
Endorsed
'Waypoint fields for deployments'
-
05 Apr 2024, 7:45PM | Action by: shilum
Tracked
'Waypoint fields for deployments'
-
05 Apr 2024, 4:25AM | Action by: shilum
Untracked
'Waypoint fields for deployments'
-
02 Apr 2024, 12:45AM | Action by: shilum
Tracked
'Waypoint fields for deployments'
March 2024
-
31 Mar 2024, 9:36PM | Action by: Dunlir
Tracked
'Waypoint fields for deployments'
-
20 Mar 2024, 7:25PM | Action by: RauLeCreuset105
Endorsed
'Waypoint fields for deployments'
-
20 Mar 2024, 8:46AM | Action by: NQone
Tracked
'Waypoint fields for deployments'
-
11 Mar 2024, 7:51AM | Action by: Visaoni
Tracked
'Waypoint fields for deployments'
-
07 Mar 2024, 1:16AM | Action by: aceacs123
Endorsed
'Waypoint fields for deployments'
-
02 Mar 2024, 5:35PM | Action by: damevos
Tracked
'Waypoint fields for deployments'
February 2024
-
27 Feb 2024, 8:43AM | Action by: SaintAshley
Untracked
'Waypoint fields for deployments'
-
26 Feb 2024, 12:31PM | Action by: greetmechta
Endorsed
'Waypoint fields for deployments'
-
26 Feb 2024, 12:31PM | Action by: greetmechta
Tracked
'Waypoint fields for deployments'
-
26 Feb 2024, 9:07AM | Action by: teghash
Tracked
'Waypoint fields for deployments'
-
26 Feb 2024, 4:55AM | Action by: fdulo
Tracked
'Waypoint fields for deployments'
-
25 Feb 2024, 10:50AM | Action by: romkacg
Endorsed
'Waypoint fields for deployments'
-
18 Feb 2024, 4:10AM | Action by: ttyyygggg
Tracked
'Waypoint fields for deployments'
-
13 Feb 2024, 11:18PM | Action by: incalo
Untracked
'Waypoint fields for deployments'
-