Skip to content
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

Remove two TODO comments from the help text #4280

Open
jostephd opened this issue Aug 26, 2019 · 2 comments

Comments

@jostephd
Copy link
Member

commented Aug 26, 2019

Remove the two TODO comments added in #4217. I need some input about how to fix this, see #4217 (comment)

This issue is just about those two comments. For other todo comments in the help see #2964

  • Fix At all difficulties except “Beginner” (TODO: and “Easy”?),
  • Fix TODO: link to a forum thread
  • Fix At least for the 1.15.x series before 1.16.0 (see next comment)
@stevecotton

This comment has been minimized.

Copy link
Contributor

commented Aug 26, 2019

Thanks for logging this, it's probably a good ticket to fix the save-loading page's related "refer to the forums" line too:

wesnoth/data/core/help.cfg

Lines 289 to 294 in c4ffade

The following points are under discussion on the forums. At least for the 1.15.x series before 1.16.0 please assume that the forum threads are more authoritative than the text on this page.
In the mainline campaigns, on hard:
• A sufficiently skilled player will have a good chance to win each scenario on the first time that they see that scenario, without foreknowledge of what will happen.
• This assumes that the player picks up all of the clues given in the dialogue.
• There are more experience points available than on easy, and the player will be able to train enough troops to cope with losing some L2 or L3 units.

@jostephd jostephd added the Blocker label Aug 27, 2019

@jostephd

This comment has been minimized.

Copy link
Member Author

commented Aug 27, 2019

Agreed, added a checklist to the first post. Also marked as blocker, not in any technical sense but because it's the sort of thing that should be fixed before a final release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.