45 replies to this topic

[JetBox]

This is just a place where you can say what you would like in the next version of Zelda Classic. It could be an item, or enemy, or a little more combo types, or anything. No one nows when it is coming out, and for all we now, there could not be another version. This is not saying when you would like it to come out, just what you would like it to have. I think having a d-map type that is a side scroller that has gravity. To go along with it, a sidescroller where you are swimming like in the oracle games and LA. And also maybe a flying Gleok that flies around the room a bit, then lands for a while then flies again. That would be coll, especially for a fire Gleok. It would make it seem like a real dragon.

[Saffith]

I'm looking forward to some separation of concerns.

[Russ]

In the next version, like post 2.5? To be honest... not too much. With scripting, I can make pretty much anything I want in 2.5. Sure, it might be nice to have some features built it, rather than scripted, but if ZC 3.0 were never released, I wouldn't be too bummed out.

Also a Tooth Gleeok.

[Moosh]

I'd like to see a tooth gleeok. Also maybe an ear patra.

Most of all though, I'd like to see 2.5 completed and that isn't going to happen if stuff keeps getting added on...

[The Satellite]

I think he means for after 2.5.

At least, I hope he does... Me? I'd have to think on that for a bit. But custom boss editing (or being able to select from more than just Z1 bosses) would be nice...

For the next version, not 2.5.

[Giggidy]

IIRC, the plan was that when 2.5 was finally finished ZC would be scrapped and it'd be remade from the ground up.

This was like back in 2006 though so plans have almost certainly changed (or at least evolved) since then.

[HylianGlaceon]

I think he means for after 2.5.

At least, I hope he does... Me? I'd have to think on that for a bit. But custom boss editing (or being able to select from more than just Z1 bosses) would be nice...

For the next version, not 2.5.

Yeah, new bosses would be great. Bosses are probably the only area I dread having to work with more than the overworld. Not to say they're horrible, just it kinda feels like anyone playing would see that I just used the Enemy Editor on some of them and changed a few things.. There's not really much you can do without scripting..

For me #1 would be to have the Roc's Cape implemented without scripting and following that would be to fix the Sword/Spin Attack compatibility issues that the Roc's Feather has with them.

(I.e in LA and the Oracles, you can charge you sword and even use the Roc's Cape while charging or keeping the charge. In ZC you can't do that. I think in FS and TMC it worked the same too, but I don't remember for certain).

#3 Would be a way to be able to scroll through items when you have the "Can select A Button item on Subscreen" rule set. My quest could really use that as it's a pain to switch between items with it on, and some rooms are much easier if you can have say the Roc's Feather and Hammer equipped at the same time, instead of needing to switch constantly. Or possibly do #4 instead..

#4 For me would be to implement two more button items like A and B (Perhaps EX3 and EX4 could become X and Y? I don't think they're really used, even in scripting). That way you could have say the Sword, Feather, Hookshot and Hammer all assigned to a button at one time with very minimal switching.

There's a lot of other things too, but I probably shouldn't list a like a dozen things.. I feel like I'm already stretching it with these..

(Oh and a big thanks to the ZC devs for what they have done. I was so glad when the Feather was added in 2.5)

[Tree]

Right now, I just want the Moldorm problem fixed.

[ShadowPC]

If we would have carrying rocks and such. And built in NPCs. That would be wild fantasies.

Edited by ShadowPC, 12 August 2012 - 02:50 AM.

[aaa2]

In Zelda Classic everything seems to be static arrays that means limited number of combos, static amount of combo types. Please implement it as a pointer with an unsigned int for size. Whenever i use Zquest i always get the feeling that all memory is being managed static. Also just out of curiousity: is it really true that zelda classic is not implemented with object oriented programming paradigm.

What i would suggest for example to handle combos on screen really fast with a vast amount of combos:
once you have tiles build a combo by making a class that consists of a tile and a function pointer and an unsigned integer. The function pointer can point to multiple functions, the number will tell you how many numbered functions you have to go through. This should be pretty efficient and very easily extendable(that is how i now implemented something like combos in the game-engine i make).(of course this requires proper error management)

Edited by aaa2, 12 August 2012 - 05:41 AM.

[JetBox]

I actually thought of something else. Maybe they could make a version for your smart phone and tablet and iPad.

[ShadowPC]

Zquest would be too small to build quests with and touchscreen could be hard to use.

[peteandwally]

really, all I'd like is maybe some revamped help documents. Like a pdf with screenshots of what it's talking about. Or, which tiles are referenced for different enemy movement types (up down shooting, etc.) or item animations. I think it would allow people to make more custom graphics and sprites if there were an easy template to follow. (Maybe there is one and I haven't found it?)

[bobby_light]

A new ZQuest UI. Note I'm not talking about ZC. Besides being more noob-friendly and less frail on newer OSes, better tooling makes for more productive users, which in theory would lead to better/more quickly-created quests.

Of course I understand that moving away from the Allegro UI would be a nightmare, but in the long run I believe the pros would outweigh the cons. The key would be getting one or two folks with the know-how and extra time; give them an empty repository, a couple of weeks, and see what they come up with. They would work in parallel with other folks doing bug fixes or whatever else for 2.5.1. A maintenance release would be a particularly good time to do such a thing, as the "old" UI would still be there and would be considered the "stable" toolset; the "new" UI, once stable enough, would be released in alpha- or beta-form. Once enough people have tested with it, and verified that quests generated with it are identical to those generated by the "old" UI (a simple cksum is likely sufficient here I'd assume), you could then move towards making the new UI the standard ZQuest.

But, failing that, a feature request:

Scripting has been a huge boon for quest makers. The quality of quests, and what you can do in them, has been greatly expanded because of it. Thus, the tooling related to script writing and maintaining needs a large amount of improvement. One small but useful thing you could do is replace the script editor in ZQuest. Instead of using a built-in text box, you could fork-and-exec an external process. The default could be whatever the system editor is, e.g. Notepad on Windows, but the user could even configure what process they wanted to launch, such as Notepad++.

To avoid hassles with inter-process communication, the editor could be opened with the script file contents, likely stored in a temp file. When the user saves and exits the editor, ZQuest reads the temp file back in for the edited content. That way, the script writing experience is enhanced with almost zero new code written for ZQuest.

[Chakaa]

Ability to lift objects, ice magic, and maybe official NPC's and some items from other Zeldas. But all of that can pretty much be done with scripting already.