search

chrisboyle / sgtpuzzles

Android port of Simon Tatham's Puzzles
https://chris.boyle.name/puzzles
Other
597 stars 168 forks source link

Untangle: show number of moves #600

Open GfEW opened 1 year ago

GfEW commented 1 year ago

Version 2023-02-10-1537-bd5c0a37-fdroid

Is your feature request related to a problem? Please describe. There's currently no indication of move count in Untangle, neglecting the full potential of this nice puzzle. ("One move" refers to one pass of the procedure "press a point and move it somewhere while still holding it, then release".)

Describe the solution you'd like

  1. Display the number of moves in Untangle, too.
  2. In Untangle custom setup, provide an option to set a target count of moves.

Describe alternatives you've considered Counting moves in memory is doable but much less fun than actually seeing sth like "COMPLETED! Moves: 2 (target 2)"!

Additional context For people who find solving Untangle with an arbitrary number of moves trivial, striving for the shortest sequence of moves that solves the puzzle can be more interesting of a challenge. I've frequently found myself undoing all four to six moves of my initial quick solution and then, more thoroughly, crafting just two or three moves that solve the same entire puzzle. One fact about Untangle that I particularly like is, aside from the obvious combinatorics brainwork, it's also about skillful placement - even more so when minimizing move count. Each moved point's new position should readily pave the way for everything else, so you don't have to touch it again.

GfEW commented 10 months ago

Does the label "upstream" imply this feature request has been promoted there, or do I have to file it on my own in order to make upstream developers aware of it?

In the latter case, could you please point me to the relevant upstream repo?

chrisboyle commented 9 months ago

The label "upstream" means it doesn't fit the goals of this Android port to implement it just for Android, since I want to keep the same rules, the same gameplay, and as far as possible the same game features as the upstream project, with the Android differences being related to things like controls and display where there are Android-specific (or mobile-specific) reasons to make a change. I've just recently clarified these goals in README.md.

The upstream website is https://www.chiark.greenend.org.uk/~sgtatham/puzzles/ and there is no issue tracker there, just a feedback section at the bottom with Simon's email address.

I haven't forwarded this issue to him myself because it seemed quite similar to previous requests for additional scoring criteria in various games, that I've mentioned to him a few times over the years.

As noted in the readme, upstream feature requests are welcome for discussion here in the absence of an upstream issue tracker; they just won't be implemented in this Android-specific repo first.