From: | streu |
---|---|
Thread: | EchoView discrepancy |
Forum: | Titan 15 |
In reply to: | Re: EchoView discrepancy |
Date: | Thu, 2020-06-25 19:17 GMT |
I'm not sure why PHost creators decided to have break so drastically from THost behavior on extreme-climate planets, in everything else they made efforts to emulate THost behavior pretty closely.
Could be that the exact behaviour of Tim's host was unknown at the time. As I understand it, its behaviour also changed over time.
PHost's formulas are pretty intuitive for my taste. Climate-Death-Rate = X% means: if there's overpopulation X% die until we're at the limit again.
Now, in THost, Climate-Death-Rate = X% means the population limit increases by (100-X)% of the actual population, which effectively increases the population limit by a factor of (100/X). PCC shows this value as "won't die until" in the planet overview. PHost authors probably saw that their formulas do not match what THost does, so they added the MaxColTempSlope option.
Overpopulation-eats-supplies means: 40 clans eat one supply, period. As far as I can tell this applies to both hosts. My memory says that this also is the original definition (but I cannot find any reference to that now), and also that I already saw different formulas in disassembly (but cannot find a reference to those either).
Back to the original problem, I would assume that EchoView supports PHost formulas. It boasted extensive PHost support for as long as I know it. So it could be that it just didn't detect the configuration correctly.
Games at PlanetsCentral use shortened configuration files. In particular, they don't contain MaxColTempSlope. Try adding a line "MaxColTempSlope = 1000" to your pconfig.src. If that helps (or if you find any other config modification that helps) I'll gladly add these to the server-side copy for the future.
--Stefan