Immortal Defense

- Made the "Love 3" medal campaign level easier. Not by doing anything to the level itself, but by increasing the cache reward for the "Love 2" level. Now instead of 160,000 bonus cache as a reward, the player gets 260,000 bonus cache instead. It's still a good idea to save up as much money in Love 2 as you can, but it should now be easier to beat Love 3 even if you come into it somewhat cache-starved. - Likewise made the "Love 1" medal campaign level slightly easier, by increasing the number of lives from 17 to 20, and slightly reducing the enemy spawn rate. - Graveship starting HP nerfed a bit in the sixth campaign. - Pride Points were a bit overpowered. I did some extensive testing where I'd play several levels that had all the Points available, spend equal amounts of money upgrading all the Points, and then play through the level, giving each Point an equal amount of money on upgrades, and the Pride Point almost always did the most damage. I didn't like that, but I didn't want to nerf it too much, so I kept its growth rate and its starting damage rates intact, but simply lowered its firing rate a bit. Now the Pride Point fires about 2/3 as fast as it used to, across all levels. - Did some more testing, and Pride Points were still too powerful; reduced their damage growth after 30 kills (it's the same as the old formula prior to that, but less after that). - Three of the levels in the sixth campaign, which were three 'boss rush' stages (85, 86, and 87, using the game's roman numeral numbering system, or 90, 91, 92 using the absolute path level numbering system which includes raberata levels) were made easier, changing the number of lives from 1 to 3, to give people some margin for error. - Reduced the number of lives for the first two levels from 20 to 10. This is because, before, on the default difficulty level, even if you just stand there, you can beat those levels (with a low percent success) without shooting or attacking anything. So the number of lives was too high -- it should at least be possible to lose the first two levels, even though it's still very difficult to lose them. - The 'Defender' enemy sometimes randomly spawned with a 0 defense rating (there is a random element to what its starting defense value is). I don't think that quite makes sense because it's supposed to be distinguished from the Form enemy by having a higher defense rating. So now I made sure that enemy at least has 3 defense when spawning, at the minimum. That might not sound like a lot, but when your cursor is doing 8 damage in levels 1 or 2, having at least 3 defense is significant. I also made its maximum defense now vary based on campaign, instead of always being 140 as a hard cap, it now ranges from 125 to 150 (5 more for its cap for each of the campaigns). INTERFACE - Added help description mouseovers for the four bottom option toggles: shaking the gui, backgrounds on/off, path width, and stage select music choice, just to clarify what those options do. - Improved the visual contrast on the manuals (enemies list, towers list, game manual, and similar). The background that the white text appears on is now not as bright of a blue. - Likewise, improved the visual contrast for the leaderboard display, file loading (to play custom levels), file saving (in the level editor) (which all used the same code anyway). - Lastly, improved the visual contrast for the help window pop-ups for the enemies, points, and lives/time/cache displays. - Updated a few of the achievement descriptions on Steam to match the in-game descriptions (for those achievements which have changed since release). BUG FIXES - Fixed a bug that caused the formatting of the leaderboards to be jumbled. Leaderboards should now be more legible and appear correctly. Longer Steam names are shortened for the leaderboard for this purpose. They're shortened more in Japanese due to font width issues. - Fixed a bug that made hellspace hard to unlock, particularly for legacy save files (now it doesn't count the percent success of the second Brother Bavakh battle). - Fixed (hopefully) a bug that caused the success % ratio to not correctly go down when you first beat a level with a higher success %, then go back again and beat that level again at a higher challenge but with a lower success %, and if you didn't score a new record score. Previously it would raise your challenge score but not lower your success score in that unique case, but now it should correctly lower your success score. - Fixed a bug that caused Noyaties 19 to have zero HP and be unable to be killed in the 'Cold Immortal' custom campaign (and presumably any custom user-made level as well). - Fixed a bug that allowed you to complete a level on 100% challenge, with any% success, then complete it on a lower difficulty with 100% success, and get 100%/100%. Now instead, the success% is not updated when you complete a level on a lower difficulty than your previous highest difficulty, only the challenge score is improved. I'm ashamed it took me this long to figure out the logical problem in how I had coded it, but it should work correctly now. Here's an illustration of how that last bug fix works now: 1) let's say your first attempt at a level is: 0 challenge, 30% success 2) you then try again at 50% challenge, and get 10% success. both of those are updated, it doesn't keep the old higher success rate of 30% anymore. 3) then perhaps you tried again at 0 challenge, got 100% success, but neither value was updated, because it's a lower challenge level than the highest challenge level you completed the level on. previously, the success would have incorrectly been updated to 100%. 4) and then perhaps you tried the level yet again at 50 challenge, and got 15% success, 5% higher than before. then it'd be correctly updated with your success going to 15% instead of 10%. So now you can't get 100/100 merely by beating a level once at 100% challenge at any success rate, and then playing it again at a lower challenge and getting a 100% success rate, giving you 100/100. This is *not* retroactive, your old scores will remain. It's just the new scores that will from now on be updated using this system, where the success rate will not update unless you are completing a level at or above your highest challenge setting that a level was previously completed on.