New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lunar Snowball Nerf #1418
Lunar Snowball Nerf #1418
Conversation
Reduced the number of completions from 2 to 1. Rewards are currently the same as previously.
replaced some spaces with tabs and removed unneccessary tabs at ends of lines.
Lowered the payout on later Lunar Impact missions by introducing arrays containing the payouts.
Lowered the payout on the second Lunar Orbiter mission by introducing arrays containing the payouts. Arrays were also added to hold the apsis, but with placeholder values
Sample return and rovers might also get some attention. |
Added far side lander contract with 2 completions. Currently set to same payout as the two Orbiter contracts. Contract currently becomes available after 2 completions of the normal landing contract. Reduced number of normal landers contracts by 1.
Lowered the payout for later missions by introducing arrays containing the payouts.
Changed max Aposelene on first 'Lunar Orbiter' contract to 3 000 km and fixed a typo in 'Lunar Lander Far Side' description
GameData/RP-0/Contracts/Moon Exploration/Lunar Landing Far Side.cfg
Outdated
Show resolved
Hide resolved
GameData/RP-0/Contracts/Moon Exploration/Lunar Landing Far Side.cfg
Outdated
Show resolved
Hide resolved
showMessages = true | ||
disableOnStateChange = false | ||
} | ||
PARAMETER |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A possible thing to consider here is to require all parameters to be completed in sequence. This way the contract could be completed with the help of a relay or alternatively by launching the lander into orbit again.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be solved with the latest commit, but not sure
Adds the longitude of the Alpha landing site to the contract to let players know where the contract wants you to land.
Deleted unused DATA node in Lunar Flyby, removed useless requirement on far side lander, made the two lander contracts unable to be accepted at the same time and hopefully prevented another vessel from completing parts of 'Far Side Lander' contract.
The payout for the new 'Far Side Lunar Lander' contract might need to be updated, since they are copied from another contract currently. |
@siimav Could you take a look when you have some time over? |
A few of the REQUIREMENT indentations appear to be off by 1 level |
Remove REQUIREMENT to have NOT completed 'Moon Boots'
Added calculations to display latitude of the landing site and make the location show magnitude instead of negative western/southern locations.
e668920
to
221ca2c
Compare
I'm currently testing these (might take some time to make through them in-career to check the rewards and so on. |
I think the only thing preventing this from getting merged is the point @leudaimon brought up about the orbiter contract max Ap requirements. Do others feel that 500km for second completion is fair or should we try to strike a middle ground between that and what we have now? |
500km doesn't seem unreasonable; but a quick look at historical missions suggests such a low Ap is fairly unusual. I wonder if requiring a higher Pe might make sense? Min 20km isn't much of a constraint. |
If the Pe isn't going to be changed, then this should be mostly done; if something else should be changed, let me know |
Implements the suggested changes in #1370, section 1. Lander revamp is to come.
Feedback about values or implementation is very welcome!