| SOL: 10477373803 | GalMap Seachbar (ID*2^20 + 0) | ||
| 0 | Wregoe AC-D d12-0 | Sol | Star |
| 1 | Wregoe AC-D d12-1048576 | Mercury | Planet |
| 2 | Wregoe AC-D d12-2097152 | Venus | Planet |
| 3 | Wregoe AC-D d12-3145728 | Earth | Planet |
| 4 | Wregoe AC-D d12-4194304 | Moon | Planet |
| 5 | Wregoe AC-D d12-5242880 | Mars | Planet |
| 6 | Wregoe AC-D d12-6291456 | Asteroid Belt | Sol Belt "nonBoby" |
| 7 | Wregoe AC-D d12-7340032 | Jupiter | Planet |
| 8 | Wregoe AC-D d12-8388608 | Jupiter Halo Ring | Jupiter Ring "nonBoby" |
| 9 | Wregoe AC-D d12-9437184 | Io | Moon |
| 10 | Wregoe AC-D d12-10485760 | Europa | Moon |
| 11 | Wregoe AC-D d12-11534336 | Ganymede | Moon |
| 12 | Wregoe AC-D d12-12582912 | Callisto | Moon |
| 13 | Wregoe AC-D d12-13631488 | Saturn | Planet |
| 14 | Wregoe AC-D d12-14680064 | D Ring | Saturn Ring "nonBoby" |
| 15 | Wregoe AC-D d12-15728640 | Enceladus | Moon |
| 16 | Wregoe AC-D d12-16777216 | Tethys | Moon |
| 17 | Wregoe AC-D d12-17825792 | Dione | Moon |
| 18 | Wregoe AC-D d12-18874368 | Rhea | Moon |
| 19 | Wregoe AC-D d12-19922944 | Titan | Moon |
| 20 | Wregoe AC-D d12-20971520 | Iapetus | Moon |
| 21 | Wregoe AC-D d12-22020096 | Halle's Comet | not in Game "nonBoby" may not even counted in nonBodyCount |
| 22 | Wregoe AC-D d12-23068672 | Uranus | Planet |
| 23 | Wregoe AC-D d12-24117248 | ZetaCC Ring | Uranus Ring "nonBoby" |
| 24 | Wregoe AC-D d12-25165824 | Ariel | Moon |
| 25 | Wregoe AC-D d12-26214400 | Umbriel | Moon |
| 26 | Wregoe AC-D d12-27262976 | Titania | Moon |
| 27 | Wregoe AC-D d12-28311552 | Oberon | Moon |
| 28 | Wregoe AC-D d12-29360128 | Neptune | Moon |
| 29 | Wregoe AC-D d12-30408704 | Galle Ring | Neptunes Ring "nonBody" |
| 30 | Wregoe AC-D d12-31457280 | Triton | Moon |
| 31 | Wregoe AC-D d12-32505856 | Sol 9+10 | BaryCenter Pluto & Charon "nonBoby" |
| 32 | Wregoe AC-D d12-33554432 | Pluto | Draft |
| 33 | Wregoe AC-D d12-34603008 | Charon | Draft |
| 34 | Wregoe AC-D d12-35651584 | 90482 Orcus | Draft |
| 35 | Wregoe AC-D d12-36700160 | Vanth | Draft |
| 36 | Wregoe AC-D d12-37748736 | (307261) 2002 MS4 | Draft |
| 37 | Wregoe AC-D d12-38797312 | Salacia | Draft |
| 38 | Wregoe AC-D d12-39845888 | Actaea | Draft |
| 39 | Wregoe AC-D d12-40894464 | Haumea | Draft |
| 40 | Wregoe AC-D d12-41943040 | Hi'iaka | Draft |
| 41 | Wregoe AC-D d12-42991616 | Quaoar | Draft |
| 42 | Wregoe AC-D d12-44040192 | Makemake | Draft |
| 43 | Wregoe AC-D d12-45088768 | (225088) 2007 OR10 | Draft |
| 44 | Wregoe AC-D d12-46137344 | Eris | Draft |
| 45 | Wregoe AC-D d12-47185920 | Sedna | Draft |
| 46 | Wregoe AC-D d12-48234496 | Persephone | Draft |
| 47 | Wregoe AC-D d12-49283072 | "Daedalus" | Station "nonBoby" |
| 48 | Wregoe AC-D d12-50331648 | "Burnell Station" | Station "nonBoby" |
| 49 | Wregoe AC-D d12-51380224 | "Abraham Lincoln" | Station "nonBoby" |
| 50 | Wregoe AC-D d12-52428800 | "Li Qing Jao" | Station "nonBoby" |
| 51 | Wregoe AC-D d12-53477376 | "M.Gorbachev" | Station "nonBoby" |
| 52 | Wregoe AC-D d12-54525952 | "Galileo" | Station "nonBoby" |
| 53 | Wregoe AC-D d12-55574528 | "Mars High" | Station "nonBoby" |
| 54 | Wregoe AC-D d12-56623104 | "Columbus" | Station "nonBoby" |
| 55 | Wregoe AC-D d12-57671680 | "Titan City" | Station "nonBoby" |
| 56 | Wregoe AC-D d12-58720256 | GameCrash | from here the game will Crash when trying to target. |
The Quest To Find Raxxla
- Thread starter Macros Black
- Start date
Ok.. thanks.. that cleared it up
How do you calculate the searchbar string, from the system ID number?
Thanks for this, I was using a different method to target these by figuring out the ids and editing the misc.conf, which required relogging and jumping out of the system.
I think it's the number of the body you want + the N2 number + 2 to the power of the length of the N2 bits in the id64 (which depends on the mass code), but I haven't tested it in too many systems. It feels non-trivial to explain and I think if I tried I'd just end up with something that reaches the solution in a roundabout way and is confusing.
So i tried this but i can't overflow the buffer:
Output result:
What am i missing
?
C:
#include <stdio.h>
#include <stdlib.h>
#include <math.h> // I need this to use the pow() function (power)
#include <string.h> // i need this to convert number into string
#include <inttypes.h> // uint64_t is defined here
int main()
{
char buffer[8]; // 8 Bytes = 8*8bits = 64 bits
uint64_t ID_Base = 10477373803; // Sol system adresse
uint64_t ID_Overflow;
ID_Overflow = ID_Base*pow(2,20); // Sol_adress*(2^20)
sprintf(buffer, "%I64u", ID_Overflow); // Translate Number into string
printf("ID_Base=%I64u\t, ID_Overflow=%I64u \t, buffer=%s\t\n", ID_Base, ID_Overflow, buffer); // display results
return 0;
}Output result:
Code:
ID_Base=10477371448 , ID_Overflow=3617855278842786103 , buffer=10986322712854528
Process returned 0 (0x0) execution time : 0.005 s
Press any key to continue.What am i missing
?Don't worry, Your code "works" as intended.
However, your compiler or OS probably does not.
With gcc on Linux (and %lu instead of %I64u) I get:
However, your compiler or OS probably does not.
With gcc on Linux (and %lu instead of %I64u) I get:
Code:
ID_Base= 1887439211 , ID_Overflow= 2528116736 , buffer= 2528116736
*** stack smashing detected ***: terminatedI'm on Win10 Home 64 bits 21H2
I remember that "int" type are tricky because they depend on x86/x64 architecture.
This is why i used the uint64_t to be sure i have a 64bits variable.
But i totally forgot that linux can have another behavior, so another number retreived.
Thx for you help
The Id to overflow is the SystemID not the 64bitAddress.
To get the bits for the Body by adding something to the 64bitAddress you would need to add BodyID* 2^54 (BodyID is always the 9 bit MSBs of 64bitAddress)
To get the SeachString
To get the bits for the Body by adding something to the 64bitAddress you would need to add BodyID* 2^54 (BodyID is always the 9 bit MSBs of 64bitAddress)
To get the SeachString
Thx a lot for your tool !
For those that have issues with the file when downloading it:
- #NAME? => the pb comes from the difference between your system lang and the file lang. You have to get the right name of "BITLSHIFT" in your lang (in french it's "BITDECALG"). Then replace all occurences of BITLSHIFT to the function used in your lang.
- When a cell has "##########" it just means the number is too long and the police (letters height) is too tall to be displayed. I modified it from 10 to 8 and its now displayed.
As I understand it I suspect the last half dozen or so posts may be close to the boundary of breaching the EULA clauses 3 c,d,e
www.frontierstore.net
Traditionally this thread has studiously avoided taking advantage of any exploits in the Quest for Raxxla.
@Macros Black : what do you think mate?
Elite Dangerous EULA and Terms of Use - Frontier Store
The Frontier Developments Online Store is the exclusive online retailer for products made and licensed by Frontier Developments plc
Traditionally this thread has studiously avoided taking advantage of any exploits in the Quest for Raxxla.
@Macros Black : what do you think mate?
Logs are public so I see no problems in this.As I understand it I suspect the last half dozen or so posts may be close to the boundary of breaching the EULA clauses 3 c,d,e
Elite Dangerous EULA and Terms of Use - Frontier Store
The Frontier Developments Online Store is the exclusive online retailer for products made and licensed by Frontier Developments plc
Traditionally this thread has studiously avoided taking advantage of any exploits in the Quest for Raxxla.
@Macros Black : what do you think mate?
I think Jorki is referring to the exploiting of the games overflow behaviour in the galmap.
I think it's a case where it violates the spirit of the law but not the letter of it.
It's definitely a bug that should be fixed or implemented properly (and securely) as a feature so you could link a route to any station/body/or combat zone easily from out of game links.
It would be way different the same exact exploit mechanism was used to gain a gameplay advantage or to crash other peoples games.
FDevs way of player retention...
Lets limit player numbers per instance to a very low number...infact lets make it near impossible to instance in Open..uhuhuhuhu sounds great
Here Is a bug fix...uh huh created more bugs, Also add Thargoid bugs that arnt a threat anymore unless you choose them to be...
storyline? ah sure its going ahead fine... "Insert two hundred years later meme here"
Add a marksman/sniper rifle....ehh lets make it shoot really slow plasma balls
And uh we made Dinosaurs fun again out of the rest of the profits...huhuhuhu
Lets tell everyone Raxxla is, isnt, maybe, maybe not, cant reach, can reach, is some wierd bug we planted to show you Brabens face into the game to keep players playing...huhuhuhu
Sounds good boss you can go and not engage with the community anymore and lose your enthusiasm as you now have the money you wanted while crashing your fans hopes and excitement
Lets limit player numbers per instance to a very low number...infact lets make it near impossible to instance in Open..uhuhuhuhu sounds great
Here Is a bug fix...uh huh created more bugs, Also add Thargoid bugs that arnt a threat anymore unless you choose them to be...
storyline? ah sure its going ahead fine... "Insert two hundred years later meme here"
Add a marksman/sniper rifle....ehh lets make it shoot really slow plasma balls
And uh we made Dinosaurs fun again out of the rest of the profits...huhuhuhu
Lets tell everyone Raxxla is, isnt, maybe, maybe not, cant reach, can reach, is some wierd bug we planted to show you Brabens face into the game to keep players playing...huhuhuhu
Sounds good boss you can go and not engage with the community anymore and lose your enthusiasm as you now have the money you wanted while crashing your fans hopes and excitement
Last edited:
Thanks mate
Yes, this was what I was referring to, specifically the apparent use of software to exploit this bug which I think may contravene EULA clauses 3c and 3d.
I'm not clear on how using the galnet searchbar is a bug or how it can be used to find bodies?
Maybe someone from fdev could clarify whether or not this is a bug.
If it's a bug/unintended behavior then I wouldn't use it.
Maybe someone from fdev could clarify whether or not this is a bug.
If it's a bug/unintended behavior then I wouldn't use it.
The search bar is universal cartographic, and it is for finding systems. If you've visited the system before, you can then find bodies using the system map. If you haven't then you need to got to the system, honk it on discovery scanner to find how many bodies there are in the system, and, then, use the full spectrum scanner to find bodies. To find places of interest to explore on the bodies, use a detailed surface to map the body 100%. Sometimes you need to then enter orbital cruise around the body before the places of interest on the surface show up in your navigation pane.
Ha ha ha, good joke. You do of course realise that most of us on this thread have been playing for many years!??
The question is whether it is acceptable to make use of an exploit, via the system search dialog and system logfiles, and in particular to automate that exploitation as recent discussion has implied.
P.S. In any case I don’t think it’s going to find Raxxla. I’m pretty convinced that Raxxla is disguised as an ordinary object and won’t be revealed until you perform some specific action-e.g. enter a tunnel (“omphalos”?) in an installation
PPS and please excuse me if Im grumpy. Copawlot had a fit yesterday, then again at 01:00 last night and I had a disturbed night afterwards with him, so a lack of sleep and an increasing annoyance with dogsh.. everywhere. Just had to clean up the kitchen
Last edited:
There is no automation. Only a Spreadsheet were u still have to manualy enter a Number that you get from the public Logfile or from EDSM or any other Database. Also we manualy enter the result of a calculation that one can also do by hand in the Searchbar.
We can not get any Information for Systems one has not Viseted. In fact you need to be present in the system of interesset. even if you viseted the system befor, you would need to visit it again, and seach while u there.
There is no Software in use. We use a Spreadsheet.
Only claryvication we may need is if it is unintentional to be able to klick on "SetTarget". wich also does not happen automated and again u need to be present in that system.
I fully agree here. However, we can rule out things that are just not in the game but still made some looking in the wrong direction.
I don't think we can find RAXXLA with it, but we can rule out NONRAXXLAS.
Edit: to also be clear about the GalMap Search. It is not a bug to seach for bodys or station via GalMap. just try and search for Pluto or any Station
The Galaxy Map is designed to work like that. Only thing we do is convert between a number and the Name (Alias). The Number is public and the names are also public it was just a matter of brain to find out how they convert in to eachother.
Edit Edit:
Using the word overflow may had set of some alarm bells. But there is no overflow happening. There is a bug in Game were u can overflow the GalMapSearchbars buffer resulting in a number > 1.8446744e+19 wich would override the values stored next to the ID64 any causes a Memory Access Violation Error (GameCrash).
However only a few ppl on this planet would be able to find out what to write to exploit this.
We stay under 2^64-1 and so we do not overflow the ID64. The ID64 is always 64bit long but can seen a a composition of 9 values but this is also true for any StellarForge generated name WREGOE AC-D d12-0 is one value whit 9 sub values [WREGOE] is 39x, 32y, 18z [A] = 0*26^0 [C] = 2*26^1 ....
it is not an exploit to have figured out how a number is repessented.
Or do u thing knowing that 1*10^0 + 2*10^1 + 3*10^2 = one hundred twenty three?
Last edited:
Fixed that for you
C++:
#include <stdio.h>
#include <stdlib.h>
#include <math.h> // I need this to use the pow() function (power)
#include <string.h> // i need this to convert number into string
#include <inttypes.h> // uint64_t is defined here
#include <iostream>
int main()
{
uint64_t ID_Base = 10477373803; // Sol system adresse
uint64_t ID_Overflow = ID_Base* (static_cast<uint64_t>(1) << 20); // Sol_adress*(2^20)
std::cout << "Base: " << ID_Base << "; ID_Overflow=" << ID_Overflow;
return 0;
}
Last edited: