Exploration value formulae

Kingdud

K
One quick question: Is there any bonus for fully mapping (to any level) all the bodies in a system? Or is it just per-planet bonuses?
 

marx

marx
Kingdud said:
One quick question: Is there any bonus for fully mapping (to any level) all the bodies in a system? Or is it just per-planet bonuses?
Click to expand...
Not for fully mapping with probes, no. For fully scanning with the FSS, there is, based on the number of bodies. 10,000 Cr per body, if memory serves.
 
Last edited:

khaos526

khaos526
Yes confirmed that's an accurate chart. Just got done first mapping SKAUDUAE SE-X D2-27, and estimated it being about 13 million CR according to that chart. Just cashed in and it came out to be 12, 995, 733 CR, so pretty damn close.

2x ELW's, 1 Terriformable WW, 1 Terriformable HMC, 1 reg HMC and 2 K stars and 1 F star and one measly little asteroid belt.

Thanks again for the work in getting that chart, been waiting for that since the patch...
 

Maolagin

M
iain666 said:
Plenty of people who haven't been there yet though.
Click to expand...

Ooh, sorry, I misunderstood your question. Well surely some people have made their first visit to A* since the FSS arrived, although I guess the sort of people reading this thread have mostly long since sold that data.. But if nobody has chimed in with it's scan value in six or seven weeks, I'll take note of that number when the fleet arrives and report back.
 

zombieapocalypse

zombieapocalypse
MattG said:
OK. I've used Median masses from my old analysis. These values will barely have changed, if at all.


Planet TypeTerraformable?Median massFSSFSS+FDFSS+DSSFSS+FD+DSS
Ammonia World0.439141434633730045977621724965
Earth-like World0.49803927029070275311262063249900
Water World0.780638997472593434156131199337
Water WorldYes0.45301126861669840011192313229773
High Metal Content Planet0.344919140703658158624169171
High Metal Content PlanetYes0.4669291639484262646831161971272
Icy Body0.01854500130015694527
Metal Rich Body0.3239333163282244131802380341
Rocky Body0.003359500130014764260
Rocky BodyYes0.1423121295043367115396011557130
Rocky Ice Body0.180686500130017525057
Class I Gas Giant69.551636384599971602146233
Class II Gas Giant476.2408752840573853118354341536
Class III Gas Giant1148.9215099952587414511963
Class IV Gas Giant2615.63537611192910466313457
Class V Gas Giant925.5758069662510402311609
Gas Giant with Ammonia-based Life170.455071774201432279312
Gas Giant with Water-based Life477.0018328832295367910616
Helium-Rich Gas Giant550.1418469002339374910818
Water Giant47.163769667173427798019


FSS = FSS but don't get first discoverer.
FSS + FD + FSS, and get first discoverer tag.
FSS + DSS = body scanned and mapped with efficiency bonus - but neither first discoverer nor first mapped
FSS + FS + DSS = body scanned, mapped with efficiency, and both first discovered and first mapped.

You could add plenty more columns for other variations, but I think this gives a gist. I've also not checked it at all, so don't blame me if it's totally wrong. Terraforming numbers assume maximum terraforming bonus, but that's by no means guaranteed.
Click to expand...
Great work, thank you so much for doing this!!! :D
 
Last edited:

TheBaumLord

T
I can confirm only minor changes to Sag A*, it's the same scan value as before (628318) plus the addition of the new bonus for main stars (Scan value of the other Bodies divided by 3).
047D12789CAB8114B308E22C0D59EACAFAC73533
Source 2 follows the new formula.
 

Allitnil

Allitnil
MattG said:
So rather than a formula and multiplier lookup table, I've thrown it all in a function as it's a bit easier to understand IMO (for me, anyway). It's not perfect, but it's close enough. It assumes you've looked up k already (and for terraformables/elws, k = (base k + terraformable k) for maximum terraformable value)
Code: 
        static int GetBodyValue(int k, double mass, bool isFirstDicoverer, bool isMapped, bool isFirstMapped, bool withEfficiencyBonus)
        {
            const double q = 0.56591828;
            double mappingMultiplier = 1;
            if(isMapped)
            {
                if(isFirstDicoverer && isFirstMapped)
                {
                    mappingMultiplier = 3.699622554;
                }
                else if(isFirstMapped)
                {
                    mappingMultiplier = 8.0956;
                }
                else
                {
                    mappingMultiplier = 3.3333333333;
                }
                mappingMultiplier *= (withEfficiencyBonus) ? 1.25 : 1;
            }
            double value = Math.Max(500,(k + k * q * Math.Pow(mass,0.2)) * mappingMultiplier);
            value *= (isFirstDicoverer) ? 2.6 : 1;
            return (int)Math.Round(value);
        }
The figures still need tweaking, but you could be doing this forever and not get it _quite_ right.

One more additional point of note. The data provided by BlackMirror (thanks, btw) seems to correlate with other data I have (and a small handful of iain's), and suggests there are 2 other potential multipliers. First off, if you have previously sold (non-mapped) data for a body (perhaps before 3.3) but were not first discoverer, and then later go back to map that body, then an additional multiplier of approximately 1.23524 seems to be applied. Similarly, if you were first discoverer of the body then the multiplier is around 1.89404. I've left this out of the base calculation because it's more difficult to determine this data from the journal (though not impossible, if you have a history).
Click to expand...
Is that code right? It seems to be what has been implemented in EDD but it is giving weird results such as some terraformable HMCs being worth as much as ELWs. In particular, it does not seem to be consistent with the results for the table you published a couple of posts later.
 

MattG

MattG
Allitnil said:
Is that code right? It seems to be what has been implemented in EDD but it is giving weird results such as some terraformable HMCs being worth as much as ELWs. In particular, it does not seem to be consistent with the results for the table you published a couple of posts later.
Click to expand...

I _believe_ it to be correct, but I'll admit I didn't test every combination gave an expected result.

That said, I've tested it against some of iain's data for terraformable HMCs. I called the function like this:
Code: 
            Console.WriteLine("Gludgoi OY-Z c13-4 1: (expected 1891752) " 
                + GetBodyValue(9654 + 100677, 0.241748, true, true, true, true).ToString());
            Console.WriteLine("Hypio Eaec TO-Z e20 9: (expected 1837746) "
                + GetBodyValue(9654 + 100677, 0.14631, true, true, true, true).ToString());
            Console.WriteLine("Wredguia NN-S b31-3 A 2: (expected 153372) " 
                + GetBodyValue(9654 + 100677, 0.15566, false, false, false, false).ToString());
            Console.WriteLine("Hypoe Phoe ED-I c26-13 B 2: (expected 400192) "
                + GetBodyValue(9654 + 100677, 0.165818, true, false, false, false).ToString());
            Console.WriteLine("Outorst UZ-P d5-0 7: (expected 431212) "
                + GetBodyValue(9654 + 100677, 0.555887, true, false, false, false).ToString());


And the output I get is this:
Code: 
Gludgoi OY-Z c13-4 1: (expected 1891752) 1891746
Hypio Eaec TO-Z e20 9: (expected 1837746) 1837743
Wredguia NN-S b31-3 A 2: (expected 153372) 153372
Hypoe Phoe ED-I c26-13 B 2: (expected 400192) 400192
Outorst UZ-P d5-0 7: (expected 431212) 431212

Which I think looks correct. There are instances with iain's data where this function is overestimating the payout - but it's not by much and I believe that's down to terraformability being a scale, and the function showing the maximum possible value whilst actual is slightly less.
 
Last edited:

Allitnil

Allitnil
Have the k values changed since the first post in the thread? That might explain the discrepancy. If not, I'll post some concrete examples later.
 

MattG

MattG
Is it just ELWs exhibiting oddness? I think the k might be wrong for those in EDD. Looks like they have this currently (in JournalEvents/JournalScan.cs, maybe line 1139):
kValue = 116295;

That's just the terraformable portion, it should actually be:
kValue = 116295 + 64831;


The k values have changed since post 1. They're here now (though the logic in that multiplier table there isn't quite correct). New values should be in EDD though (though see above). I didn't update post 1 yet as I wasn't 100% sure it was correct yet. I will try and update that tomorrow.
 

Nerix

Nerix
Question abou the full system scan bonus:
1. Will that add a multiplier to the payouts for scanning planets? E.g. an ELW will pay you 3.2mln, but with a full system scan times 1.5 = ~4.8? Probably it's just a fix bonus of x credits?

And 2. do we have any data regarding the payouts for FSS + FD? Sometimes I wonder if it's worth to fly 200kls, so it would be good to have a comparison between FSS+FD+DSS vs FSS+FD.
 
Last edited:

MattG

MattG
Nerix said:
Question abou the full system scan bonus:
1. Will that add a multiplier to the payouts for scanning planets? E.g. an ELW will pay you 3.2mln, but with a full system scan times 1.5 = ~4.8? Probably it's just a fix bonus of x credits?

And 2. do we have any data regarding the payouts for FSS + FD? Sometimes I wonder if it's worth to fly 200kls, so it would be good to have a comparison between FSS+FD+DSS vs FSS+FD.
Click to expand...

1. I believe full system scan is 10k per body bonus. Not worth the time or effort to go out of your way to specifically get this, but a token gesture if you do it accidentally.

2. You probably want this. TLDR; map untagged terraformables/ELWs and maybe AW/WWs if you're only in it for the money. I'd say it's probably only worth mapping 1 body per system, or 1 binary pair because the gravity well effect slows you down too much - but that's just me.
 
You must log in or register to reply here.
Back
Top Bottom