Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Can't display screenshots? Nonsense. I have a web browser, discord, 3rd party tools etc all floating in various spots of my cockpit.
It's actually for displaying any window on your desktop in VR, in any position or size. It's a must have in this game in my opinion. I spent some time to move them around and make profiles for each ship so I can have the screens integrated into the layout of the cockpit.
https://forums.frontier.co.uk/threads/frontiers-stance-on-bots-and-cheating.565085/
If i had written a program that reads the output (screen) and based on that generates input commands such as auto fly around asteroids and auto searching cores with PW scanner and prospector limpets avoiding collisions in real time, that would be a bot. But macros are not capable to do so. They are not processing the output. You still have to find the cores yourself when making the map and you still have to provide the input manually when you record the macro. It doesn't compromise the game mechanics in no any way.
Indeed we exploit here the fact that the core asteroids are always spawning in same place, but screenshot mapping exploits that too and after all, this is the way the game is designed.
We know what macros are... Hell anyone that's using Voice Attack is using a bunch of macros. I've got a macro installed for my joysticks so that if I hold a certain button for half a second, my POV toggles between being an analogue thumbstick and an 8 way POV (there's a small rapidly blinking light next to the POV when it's in 8 way mode, it stops blinking when it's in analogue mode). Here's the important part though: It's not actually automating anything.
Using a macro to speed up a few regularly used menu sequences (requesting docking for instance) probably isn't going to cause any problems... However...
What we don't know is the method used by Frontier, or how good it is at detecting bots.
An action constantly being repeated, that requires multiple inputs from the user, that's automating flying around and mining, and the actions are all exactly the same down to the last micro second? That may well be enough to trigger any process looking for automated inputs.
Some games devs have completely blacklisted AHK. Simply having it running is enough to get you kicked or even banned from their games.
However, don't get it wrong, its not auto mining, this would not be possible with macros. Its only navigating to each next core. There is also nothing repeated, every flight between each core is unique set of inputs with unique timings between each command. I doubt it can draw any suspect.
How it works in more detail:
When i start making a new map, i drop at hotspot center and search the first core. When found i remember its direction from hotspot and distance and then fly back to the hotspot marker. From there I align the ship facing the planet marker being above the asteroid plane. I use keyboard when flying to the core, while the macro tool is capable to record mouse input, but this is not precise enough, works better with keyboard. First im only seting the correct course by turning the nose into direction of the core. Then simply fly streight (above asteroids) until reaching certain distance and then cut engines and stop recording.
When recording a map i carry a fighter with me. i drop it at the found core and leave it there while searching next core. When found repeat the process, but now using the fighter as reference for distance.
Each flight between cores requires to set different direction and fly for a different distance, so that in the end each flight between each core is a unique set of keyboard inputs which are provided manually so that the timings between each key press is always different and natural just like I have pushed the buttons when i was recording that flight.
Each flight is a separate macro. in the end they are chained together by a hotkey (the NEXT button). The whole set of chained macros are then saved into one single file which represents the map.
When i replay the course, I leave the fighter at the carrier (its only needed to measure distance when recording), load that file, drop at hotspot, align with planet and hit NEXT. It replays the first flight and I find myself right above the core. Crack it (all by myself) and then again align with planet and hit NEXT, it replays the second flight etc...
But lets find out. I take the risk, if I don't get banned in the next weeks I guess we can consider it safe :-)