I have to confess: my current priority task has been playing... er, researching a certain quest called "Twilight Princess" (What? ZC developers are required to be all up ins on the canonical games!) But rest assured that working on ZC isn't far from my conscience. I mean, mind. So, in the interests of full transparency, here's my list of things I'm personally ensuring will be in 2.5.
Also, I hereby assert that, until the final 2.5 is released, I will only work on these tasks, and I will not add tasks to this list.*
Note: these are, in fact, subject to cancellation if I deem it necessary.
Note 2: hey, other developers, I won't take offense if you decide to implement any one of these yourselves after deciding that I'm being too laid-back and summertime about them. The previous sentence is not reverse psychology.
---
* Bottomless Pits and Drowning (currently in progress)
Rating: Mostly Easy
Desirability: High
Chances of producing difficult bugs: Mostly low
This requires one new Link sprite, one new combo, and one quest rule. The tricky part is getting the Stepladder to work. (If put under pressure, I'll just have to make the Stepladder incompatable with them...)
* Sideview Stepladder (currently in progress)
Rating: Easy
Desirability: Medium
Chances of producing difficult bugs: Low
Link can use the stepladder on the edges of platforms in sideview. This lets him cross one-block gaps, or shorten a gap which he must jump over. This would also entail some MISC: sprites depicting the ladder (and, while I'm at it, the raft) when viewed side-on.
* Choose fonts in the String Editor
Rating: Easy
Desirability: High
Chances of producing difficult bugs: Minimal
This requires a font-selecting menu similar to that in the Subscreen Editor. The slightly tricky part will be making that font displayed in the preview pane. (Owing to the nature of jwin, this information isn't immediately "visible" to the preview pane code.)
* A few more String Control Codes
Rating: Easy
Desirability: Mostly low (I've made the most vital codes already.)
Chances of producing difficult bugs: Low
People have asked for a "Give item" code, but I'm also thinking of a "Player name" code, where the name of the player's save file is inserted into the string at runtime.
* Translucent string panes
Rating: ???
Desirability: Medium
Chances of producing difficult bugs: ???
I'll have to look a little harder at maps.cpp before I can gauge the difficulty of this.
* Signpost combos
Rating: Easy
Desirability: Required!
Chances of producing difficult bugs: Low
This requires six new combos ("Signposts A-F",) and five new Message Strings per screen. When you walk into a signpost combo, the appropriate screen message string is displayed.
* Ladder combo
Rating: Easy
Desirability: Required!
Chances of producing difficult bugs: Low
This requires one new combo which enforces restrictions on Link's movement when he's on it, and one new Link sprite.
* Bugfixes (yes, this is in progress as well, of course.)
Rating: n/a
Desirability: Required!
Chances of producing difficult bugs: n/a
This is the domain of all developers. However, I suppose I ought to take more responsibility for bugs of my own doing.
---
COMPLETED TASKS:
* Solid Damage Combos
Rating: Mostly Easy
Desirability: Medium
Chances of producing difficult bugs: Low
I can already make solid damage combos that hurt Link when he walks into them straight-on. The slightly annoying part is dealing with diagonal movement, as well as "shimmying" along a row of them - but nothing that about an hour's work couldn't overcome.
* Quest Rule: Messages disappear
When this rule is set, pressing the A button when a completed string is onscreen makes the string disappear. (What it will actually do is make the string "Next" to the zero string.)
* Making the Lens of Truth sounds play when you toggle it on and off.
Rating: ???
Desirability: Mostly low
Chances of producing difficult bugs: Minimal
* Making the screen shake when you use the quake hammer.
Rating: ???
Desirability: Mostly low
Chances of producing difficult bugs: Minimal
---
If you wish to argue for the abandoning of any of the above tasks, feel free to state your case!
*Escape caveat: silly little alterations that take half an hour to implement from inception to conclusion and can be scientifically proven to be bug-free (like, for example, the Wealth Medals) don't count.