Space Engineers

Space Engineers

Not enough ratings
Automatic Miner Probe Script
   
Award
Favorite
Favorited
Unfavorite
File Size
Posted
271.356 KB
15 May, 2021 @ 1:19pm
1 Change Note ( view )

Subscribe to download
Automatic Miner Probe Script

Description
Script for automatic drilling probes
.At the moment, only the space environment is supported.
Support ENG and RU languages.

Introduction:
The script allows you to fully automate the process of mining with the help of drilling probes, which are controlled directly from the ship. It is possible to specify deposits for production either through the camera using the Raycast () function or manually by setting two coordinates on the asteroid and entering them in the display. Mining takes place according to the rule "one deposit - one probe", and it is possible to excavate around the deposit of any size if necessary.

Functional:
  • Mining in outer space
  • Excavation around the deposit
  • Docking-undocking with a simple check for obstacles
  • Semi-automatic and manual indication of field coordinates
  • Tracking the status of drones, support for emergency probe programs (in case of a script failure), easy monitoring of the situation around the drones using turrets.
  • Control multiple probes at once using a single computer
  • Simple command system
  • Automatic filling and unloading of probes

List of commands:
  • SCAN - a single launch of the beam by the camera in the direction of view to obtain the coordinates of the deposit.
  • GOODBYE:< robot number> - removes the probe from the list of controlled robots. After executing this command, you must run the CLEAR command, otherwise the probes will start behaving incorrectly.
  • CLEAR-clears the list of deposits, returns the probes to the connectors
  • CLEAR:< field number> - clearing a specific field and returning the probe used for its development to the connector.
  • RUNALL-returns all probes to the connectors.
  • RUN:< probe number> - returns a specific probe to the connector.
  • MESSAGESCLEAR-clearing notifications

Features and rules:
  • The probe connector must always be at the rear of the probe and pointing in the same direction as the rear of the remote control unit (look back).
  • The probe gyroscopes must be installed with the same orientation as the remote control unit.
  • The probe must drill a tunnel sufficient for free entry and exit.
  • The braking distance must be calculated manually based on the maximum load of the probe.
  • The cameras on the probe should allow you to freely scan any direction and there should be at least 2 of them on one side.
  • Only one type of connector is supported - connector.
  • The following blocks (boxes, reactors, connectors, drills, hydrogen tanks) located in the group of probe blocks must be connected to each other by a conveyor.
  • The probe and the mother ship must have at least one box each.
  • The number of connectors on the base must not be less than the number of probes.
  • Damaged blocks are lost by the probe and are invisible even after repair, provided that it has not docked to the base and updated the list of blocks.
  • The inventory refresh rate should be as low as possible, otherwise there will be lags. If it is high, then due to its use not only for updating inventory, there may be failures at the stage of returning to the base.
  • The probe must have a manual control system in case of accidents.
  • The probe's cameras are used to scan the asteroid and check for obstacles.
  • The probe accelerators must dampen the speed in all directions.
  • Some units, such as extractors or emergency remote control units, should not be in the driller unit group. The extractors will be taken as connectors by the script, which may cause failures.
  • In the group of probe blocks, there should be only those blocks that are located on the probes and with which the probes should work.

Guide: https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=2488313078
Example probe: https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=2488319456
Example probe 2: https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=2488920336
22 Comments
☭Android☭  [author] 26 Jun, 2024 @ 11:20am 
even manual has english version, in script you just need to set ENG bool to true as i remember
☭Android☭  [author] 26 Jun, 2024 @ 11:19am 
but this script supports english language
Arthur 26 Jun, 2024 @ 7:05am 
i had a variant of this script in english... i will see if i can find it on my disk somewhere
MrFox 26 Jun, 2024 @ 7:03am 
Wish this was in english, seems amazing!
☭Android☭  [author] 21 Sep, 2023 @ 1:44am 
Ну и читай руководство
☭Android☭  [author] 21 Sep, 2023 @ 1:37am 
Скинуть не могу, 7 винда игрой не поддерживается, строишь платформу, на ней программируемый блок, в него скрипт, на платформе к коннектору зонд-пример подключаешь, настройки в описании зондов указаны.
Ещё нужен грузовой контейнер, камера, питание и т.д.
Krolick 21 Sep, 2023 @ 12:25am 
Возможно ли полный рабочий чертеж станции с зондами для наглядного примера?
А то я что та не понимаю что и куда водить.
Arthur 11 Aug, 2021 @ 10:47pm 
And a Little Tip, convert the Values on Screen to String, Like speed or distance to have less Visual polution on screen

instead of `(float)RC.GetShipSpeed())` to get like "speed X.YZABCD"
you can use `((float)RC.GetShipSpeed()).ToString("0.0")` to get "speed X.Y"

or `((float)(RC.GetPosition() - Me.GetPosition()).Length()).ToString("0.00")` to "X.YZ m."

or even to get a GPS with a fews metters precision instead of a EXACTLY postion of RC
Arthur 11 Aug, 2021 @ 10:33pm 
well, of all the tests I've done so far, the chance of her getting stuck coming back straight is minimal compared to the chance of her get stuck trying to spin inside the hole, since the only time she got stuck, was because a small voxel (a micro perfect cube of a few cubic centimeters) entered the connector on the way back
☭Android☭  [author] 11 Aug, 2021 @ 1:16am 
Killed the probes? This should indicate that the order of the probes was lost due to the removal of one of them from the list.