Soooo.... Is the item editing array a good idea? I thought of it since not all games have the same items...

I was also wondering if different armour changed how Link looks since it does in every LOZ game created so far...

At the moment, with the armours... well, they kinda don't change any graphics

Sorry, I should introduce myself, my name's Mark, I'm doing all the scripting work on the Zelda engine.... and I"m kinda the main reason that it's being delayed at the moment (sorry, I'm in my exam period, and I also have my duties as moderator).


SilentResident knows how I've implemented the items/weapons/armors available in the menu's, and I'm assuming he's keeping it as a surprise, but I'll tell you this, it's a lot easier and a lot more powerful than arrays, and lets you have complete customisation over your menus
I've put a lot of thought into it, much more than any other script I've made, and it's something that I don't think's been done before

Or course SR will probably just sign in and tell you now that I've hyped it up


Since I'm posting here now, I was just wondering what people though of the Zelda Engine? Any special requests for me with the scripts or events (nothing too big, we're still hoping to get Patch #3 out before 2012 )?

i look look look and look for darkworld tilessets but fined none

@Night_Runner

was hoping to work along side of you, SR said she would like to experiment with moving to xasabs 4.0 in the future, but that wouldn't be any time soon, rather experimenting to see if it can handle any other scripts beside the hud, and if a rewrite or small modifications are in order, I'm thinking we could aim this at least 3-4 months after the release of patch 3.0, so everyone will have a nice break and some time to relax, i will be making a better features video, any features I should look for, I will play all the Zelda games I can and watch videos for features and ideas after I move, anyways I could get a demo of the current work so I can see what scripts I should look for, or what needs to be added thats not there.

My idea is a map screen the shows what room of the dungeon you are in, also button mapped from page up page down for the 4 screen menu to other buttons.

so whats up with the boss men or should i say boss women she has not made a post in over a week

@wormy677
I'm wondering the same thing

It's exam time for us in the southern hemisphere, SR said that they were under a bit of pressure to knuckle-down.

I wouldn't worry

I would have thought silent would be back by now.

would like a progress report btw

HELLOOOOOOOOOOOOOO!

I am back! I missed you, dear friends and teammates! Finally I am done with those June's university examinations.

OK, now my answers to your comments



@ Klokinator: we in the team -at least some of us- were having some duties in real life, which cannot be avoided. Thus, we are implementing even more changes to the engine such as the Dynamic Boomerang and Hookshot that can gather small items for Link, the Dynamic Lens of Truth, of which the Eye's effect moves with the player in real time, and now the player can see invisible items only within the inner cycle of the Eye (instead of the whole screen as of now), the expanded menus and the way items work, and more. With few words, we don't care about release dates. We care about bringing you an even bigger Update Patch 3!!! :-)



Aye, as Chakanevil said, we are not willing to limit the PZE, and we are expanding it in all possible ways.



Aye, in UP3 those issues are addressed. And in UP3, indeed, both the Boomerang and the Hookshot can gather small items.
The Boomerang and the Hookshot can gather the following items:
Rupees and Coins
Small Magic Jars
Small Heart Recoveries
Small Keys
Other common items of small size

Items the Boomerang and Hookshot cannot pick up are:
Big Magic Jars
Fairies
Bomb Supplies
Arrow Supplies
Rare Items or items with big size

It is obvious that the weapon supplies such as bombs and arrows cannot be picked by using other weapons. They have to be picked up by Link himself.




Well, our dear Night_Runner has a big surprise for everyone about the editing of the item arrays.
The Project Zelda Engine will come with an encyclopedia-based Tutorial (in HTTP or PDF format), that can be expandable and it will contain all the tutorials for how to edit the item arrays, the maps, configure the settings, edit the events, and anything else regarding PZE!




Aye, indeed, as of now, the armor is not reflected in Link's sprites, but I am planning to make it work in the future. I got some ideas -including the use of conditional branches- to make this work in the future, although it can be a tedious work and require many new sprites to be added to the PZE, increasing the total file size of the engine to more than 300 MB. ^^
And, my dear Night_Runner, how comes you feel responsible for the PZE's delays? I don't think so. The delay of a hobby's work is not something that we can call "delay" at all. Anyways the PZE is not a "duty" at all. The PZE is just for fun! People need to relax when it has to do with RPG Maker XP and have fun working on their free-time hobbies such as RPG Maker XP, otherwise they get stressed! If we are worrying about time and delays while doing our hobbies, then I am not surprised why the Western World suffers from stress.


RELAX DEAR GAMERS! STRESS DOES NOT BELONGS IN GAMING WORLD!!!




Aye, same for us in the northern hemisphere. Cool that both hemispheres have same "schedules"

welcome back Silent, congrats on the tests, hope they went well for you.

was wondering what other scripts you would need, played with transitioning to xasabs 3.9 i got the hud working some what, but ran into a few errors when copying over the map. i will try to integrate more features of pze into xasabs in the next few days.

The problems I have encountered is xasabs has it scripts and pze has its scripts as well, they could be conflicting, and placement is a bit of a pain, knowing what to add or remove is guess work for me, I'm just experimenting as of now to see if it would be sensible to transition to xasabs.

Edit: I wasn't very successful, I'll leave it to the pro's

reserved

looks like 4 posts will be enough to cover the needs, it will be 11 spoilers per a post, there are 44 topics that needs to be covered, and i just think that this guilde will help the team decide if it would be worth the time to transition to it in the future.

Nice post! Really a nice one. Really I love XASABS. Well, excuse me but I didn't understood very very well those details you are saying in your comments, as those other combat systems are not well known to me. XASABS is confusing me abit, but I could love to learn using it!
I am sure Night_Runner understands your comments better than me as he has some experience with those combat systems.
Even if I am abit confused about that battle system, I think I got the idea about how XASABS works now. I also understand how item/weapon's interact with events such as shrubs and walls, etc, in XASABS, and I can say, it is great! You can post more comments about it.
The good is that, as Night_Runner told me, the revamp to the Inventory Screens of PZE (from the old event-based inventory to the script-based inventory) opens the way for the integration of better battle systems to the PZE, such as XASABS.

All what I am worrying about so far, is the compatibility of XASABS with the Sticky Switches script of Project Zelda Engine. The sticky Switches are needed to give certain weapons/items an area of effect zone (instead of full-screen effect). For example, for the Lens of Truth, which makes nearby invisible items to get revealed when Link is 3-4 tiles close to them, or for the Ocarina's music to affect the nearby events in a map in a radius of 4-5 tiles (such as standing near an old stone monument at least 4-5 tiles near to it - and play Zelda's Lullaby to trigger an event on the monument).
The Sticky Switches, with few words, allow certain weapons such as the Lens and the Ocarina to have an Area of Effect radius with the player's location being the center of the AOE.

Really, the game could be very unrealistic if those weapons's effects are full-screen wide.

yhaaaaaaaaaaaaaaaa shes back

saw the updates. Great work so far. I told you that i have near every char from zelda in A Link to the Past style and that i wanna upload them for you..but i had a long exam period. Today is my last one and then i have a lot of free time so i can upload the sprites.

I have sprites who work allready (can be used in the maker) and some chars are done but i didnt make the charset for them. In the end
its rlly easy to make char sets from these sprites because like i said allready..they are done.

I made allready a folder with all the stuff. Uploading soon but it would be better if you tell me some chars you wanna use (my char/tileset
folder is over 800 MB and its all from Zelda ^^)

For example: i made the scarecrow from Zelda (OoT,MM) and you remember..there was a ocarina song for the scarecrow and after
you used it..the scarecrow starts dancing.

or Hyrale Guards, Gerudos and of course a link set where he is using every mask from majora + the godlike mask and i have an

evil link too (with 2 swords) + animation. This one was made by a friend and long time ago i wanted to make a evil link mask of this set
so you can transform into the dark link with 2 swords. Its not hard to make a mask from this set (just use the face from this link) but i didnt
had the time to finish him. Perhaps i got some time in my freetime.

@zhoul

Excellent! Simply excellent! We can't wait!

I was wondering if perhaps we could use sensors for items that are hidden?



just modify the page so that when switch, or variable, or self switch, which would be assigned to the lens of truth, it shows the cracked rocks, which work with the bomb tool, lift tool, run tool, ext...

Good idea that sensor you mention. I guess the Sensor has all the features of Sticky Switches? Because they are gonna be needed for non-NPC / non-monster events.

But how customizable the Sensor is in terms of radius per event? The Sticky Switches allow you to set different radius per event - even for events on the same map, by just putting a comment (green colored text) to the event with the title STICKY SWITCHES, and set the number of Radius below it. The rest is done automatically by the Sticky Switches.

For example, the event A can have STICKY SWITCHES: 5 tiles radius while another can have STICKY SWITCHES: 15 tiles radius and that on same map.

Also I hope that the Sensor you mention, can be customized so they wont go to 3rd page of an event only? Can it also be appointed to go to 3 or 4 different Event Pages on the same Event, depending on the player's actions or distance from event? For Example, with Sticky Switches, if player within 10 yards radius, Event Page with Self Switch A turns on. If player 3 tiles close, go to page with Self Switch B, etc. Just I am saying that in case the Sensors only switch to the 3rd page of an event.

@SilentResident

I didn't really catch that, could you clear that up?

perhaps a small drawing or a picture, or a demo?

also could you tell me how you make thumbnails on here?

i made an image i hope this is what you mean?

Image?

edit: I posted what I was after and someone made a demo on how to do it, it may need a bit of tweaking, but here's the demo, give it a try, do you like the way it works or would you rather have the boulders all cracked at once, instead of the player being in range? I added my own little touches, btw.

The way it's done is quite easy, you just create, an enemy, call it lol, lol will be number 68, make E Item a B instead of C, make sure it has a graphic, then create a enemy troop on # 68, name it lol, go to battler, ENEMY_SENSOR, make a new line, enter on line 136, and type in 68=>2 # lol, make sure you place a coma "67=>2, # enemy bomb" you always need a coma after the last one if you are droping done one more, then when you want to use it in an event you need to put <Enemy68> as the event name, then you can choose what ever graphics you want for the event, hopes that makes sense, if not there's a girl who has an explanation in the demo, it didnt take me very long to catch on.

Lens of Truth Demo

@Chakanevil

There is a way to create thumbnails in your comments. You have to upload a picture to a site such as Imageshack and it will generate thumbnail links as soon as you make the upload of the picture. In the Imageshack, it is called "Embed Thumbnail of this image" You can use those thumbnail links anywhere.

Thumbnail of a big wallpaper (Click it to enlarge to full size)


Uploaded with ImageShack.us



Edit: And about the whole thing with Sticky Switches and Sensors, I have to say that, from what I have seen in your demo, the sensor's abilities seem exact to those of the Sticky Switches but I still prefer the Sticky Switches over the Sensor as they are much more easier to customize. I can give radius to an event without a need to open the Script Editor at all, and without a need to give the event a certain name such as <Enemy66>.

With the Sticky Switches, all what you have to do is to place the following comment to an event's page (Insert>Comment...):




and we are done. The rest is done automatically by the Sticky Switches script. Very simple, heh? The Sticky Switches script will translate the above comment as: If player is 4 squares away from the event's location, turn automatically the event's self-switch A on. More info of the sticky Switche's features can be found in the script itself in PZE.

I don't know why we are doing the whole discussion about Sensor and Sticky Switches... if they are the same, then lets stick with the Sticky Switches in case we are gonna add XASABS to PZE. The Sticky Switches are easier to use and its functions can be used and customized without a need to edit the script at all.

Anyways, the Sticky Switches are a script that came with Project Zelda Engine itself, and the previous PZE team had their reasons to add it in the PZE.

So far, I don't see any reasons of replacing Sticky Switches with Sensor (unless the Sensor is part of XASABS and also it conflicts with Sticky Switches?)

@SilentResident
im not sure if they will conflict, lets hope not, im no scripter, lol!

i wanted to ask how exactly do the items work, are they working with the common events, and if the new version isnt using common events, is there any way i could get a demo of that?

@Chakanevil

No point for a new demo here, as since the last demo I gave you, there has been no change to the way the items function. The Items are working with Common Events, just like always.

From what I saw the v3/patch#3 of this SDK/Engine you have majority done why not release it because it seems to be a huge improvement from v2 of this. and why dont you release regular updates? why do you cram it all into one huge release/download?

@KingCharizard

I don't think it was possible to cut the Update Patch 3 into smaller updates, as the changes to Inventory/Menus are not something that can be divided into smaller updates (otherwise they could not work properly at all). That is why the Update Patch 3 is bound with the work's progress on the Inventory and Menus.

Well, the Update Patch 3 brings many changes to the core engine of Project Zelda, and it is only 5-6 months old and near to its completion, while the Update Patch 1 (which also was big), it took 3 years to complete.
So as you see, we are already completing our work on the Update Patch 3 at a much faster rate than we did with the UP1.

I downloaded this and tried it out, and i'll admit this is impressive! However its not a good SDK(Starter Development Kit)/Engine at all, in fact its horrible to use for make a zelda game, yeah it has all the graphics and cool features but it takes atleast 5 switches to make a text speech thats crazy, for instance you gotta freeze link make the menu freeze and other crap, instead of just letting the user enter text of course someone can copy and paste a text event but the amount of editing the'd have to do to get the event exactly like they want it is too much and they might actually mess up something, now while i may be disappointed and a little frusterated concidering i had high hopes for this may i suggest a solution? perhaps trying writing scripts to do the nessary steps to setting up things such as text and what not, so the user doesnt have to do as much work.. for instance write a script that turns the switches off and on and and take the other nessasary steps so the user(me) only has to use the script command.. im gonna try to do this for myself but suggest you get a scripter or become one other wise you wont see anything actually finished with this kit.

This is NOT beginner or USER friendly at all, this is a huge mess and unless you have the patience to figure it all out no one will be using this to complete their game.

@KingCharizard

...

Excuse me, what Zelda Starter Kit have you expected to see for the RPG Maker XP platform? Maybe a Starter Kit that is as easy to use as to eat a biscuit? Or to be as easy as possible as a fairy tale?
I don't know why you are thinking that way, I don't know what you expected from it, but I am pretty sure there is no other complete Zelda Starter Kit that is easier than the Project Zelda Engine and the Zelda Classic...

And what you find that disappointing or frustrating in it? Can you be more specific? Is perhaps not the engine but the fact that you are an impatient person?

You should know that, much like as with all the RPG Maker XP, the users of Project Zelda could have patience and understanding of how the engine works rather than just giving it a look and then come here in the forums to call it a "huge mess" or whatever. And all that just because you are not trying to understand it.

What did you disliked more? The fact that there are several functions and switches for each of them?

And let me explain why there are switches for the text speech.
Pause Link Switch: As the Project Zelda Engine (PZE) has an advanced message system, the controls of the player's character are flexible. The Pause Link Switch ensures that any player's controls during the conversation are disabled and the player is paused, preventing him from using any weapons for the duration of the conversation. Because, thanks to the amazing Hermes advanced message script, the opposite is also now possible: the player can walk or use his weapons while a NPC speaks and the text box appears. This feature, not available in the standard RPG maker XP, allows the player to be able to move during conversations, and it is excellent for giving immersion in towns and villages, where the player can hear nearby NPCs having conversations/dialogs with each other, without the player actually having to stand idle to hear them.
The Pause Enemies Switch: Allows or disallows the enemies to move or make actions during a conversation/dialog/cutscene. Very handy for many cases and for giving a "living breath" to the game's world.
The Pause NPCs Switch: Same as above - it lets the nearby NPCs such as villagers, guards, creatures, etc, to continue their wandering patterns or patrols (aka move routes) during a conversation or dialog. Turn the switch ON if you want to force the NPCs to stand idle (freeze) during a conversation.
And more!

So, as you see, every switch and variable in the Project Zelda engine is not here to mess your game but to open the way to further customizing the cut scenes and events in your game. There is always a good reason behind anything in the Project Zelda Engine. Our goal is to give a flexible and expandable engine to the player rather than a simplified, non-flexible and hard to use starter kit.

We will of course create a PDF/HTTP manual guide that explains anything in the PZE - from switches to features - and we hope this will help simplify and clear things for the people who are confused with the engine's functions and are seeking for our help.

Now, it is up to you if you wanna use the PZE or toss it away. Feel free to toss it away, but you can't come like that in the forums and start blaming it for failing to understand it what the engine does offers to you..

All of the things you have mentioned can be done on the back end with scripts with the proper scripting skills the creator of the zelda Fangame need not know what that does or should know, and if they need to specificly call the move while dialog function of whatever then would simply use a script command. I will take this and try to script every event/switch or action into a script. because this is just too much work for you the others trying to build games with this and so forth... and with script knowledge this coulda been done alot easier and faster.



This is the event for the brush, aka grass. With a script not only could the users of this make a game a focus on actually building the game, but they wouldnot have to go through this and figure out what this does. Like i said this engine can be made "easy as pie" (as you put it) to use for others if you or whoever had created this had proper scripting knowledge.

Would you mind if I used this framework and converted the kit into a cleaner, more user friendly kit and redistributed it?

FYI: I was never confused or didnt understand the feature, function or whatever else you think i misunderstood I just simply didnt like all the clutter and unessasary events.

@KingCharizard

we and the team are looking at other systems to use, it is unkind to take ones work and pass it off as your own, so please with out the go ahead please refrain from doing so, if silent wants to allow you to clean the code then that would be fine, but as of yet there is no word, a little reading will show that we are currently cleaning the code up, and are looking at alternatives options, I would love to transition from pze to Xasabs, but as of now the team is under a heavy work load, and we are planning a transition, if there will be one for patch 4, or even 5, that way this doesn't not become demanding and tensions are on the rise, but rather in the free time, and for enjoyment. Silent is well aware that the engine relies on common events, as i said we are looking into eliminating as many as possible, it'd be great if you can help, but that has to be cleared with silent and the scripters first and foremost.

I have tested the very first engine and I have to say major changes have been made, this was a starter kit predated to Patch 1, so this came along way, and hopefully an even father way.

Speaking of xasabs even then you will need pages for each action you want to to perform, but these are minor switches that are controlled by scripts, and xasabs is very advanced, if you dont believe me have a look over the manaul

xas-manual

Although I do agree PZE could be more streamlined, I will admit it I'm in no hurry, because I know we will get there.

btw here's an example of how much more streamlined XASABS is, it uses two page and little commands to slice bush that block the way.

@Chakanevil

In all honesty I do not need permission to use this kit as i please, and if or when i clean this up, I have every right to re-distribute it as scripting ]work done by me(of course the graphics and other hard work will be credited to the right people), because you do not realize that each switch and conditional branch used here is gona take months of scripting to get this cleaned up and user friendly, and what i mean by user friendly is a person(creator) using the kit would only have to enter a script command/call like
(of course this is not actual code or even useable I just wanted to get my basic point across)
What this does is it will allow users to create a new event give it the shrub graphic and the condition branch and script command and when link interacts with the scrub the shrub script is activated, and the script will have everything that can happen with the shrub available for instance when link picks up the shrub, everything needed to handle that action will be scripted and done just like you guys have done with switches branches and the other mess... you got going on here... I am not trying to be mean or rude i'm sure your working hard its just in my opinion your working all wrong if your trying to create a SDK.. however if this was your own fan game of zelda and no one would have access to the files and what not just the game download your aproach/workflow would be perfectly acceptable


Exactly, my point im trying to make the xas system uses script commands. which is cleaner easer for users to implement all the systems features in their game and what not.

@KingCharizard

i know what your saying, I was the one that told silent that the system needed to be transitioned into an easier system, I just don't want anyone doing any work on her hard work, and claiming the system as their own, when clearly it is not, but rather a cleaner version of what we are planning to accomplish, it would be nice to have another scripter around but that is ultimatly her decision, I'm thinking possibly with your skills and knowledge we could get patch 4, the transition to xasabs converted over, with a few hassles and changes besides major hassles, you will need to talk to silent about it though.

@Chakanevil

I dont steal, I said I would redistribute a modfied version, I wont be joining the team, I have my own people to help with the transition. and I pmed you on this matter, this kit doesnt need xas what it needs it its own special system like xas but made speficially for this kit. again I will see what i can do and if I achieve anything worth realeasing with in th month i'll release a download, and you should re read my edited post above this one..

The features xasabs offers is a lot easier then writing a new system, it's easier to transition over to there. you should try the xasabs demo to see what i mean, and play everything through.

let me see if i can find the demo video i made



Sorry this one isn't english but here's 3.82.



and here's what xasabs 4 promises, it's not released yet,





I been trying to get this guy to release sprites to me, but he said project is down.



btw silent here's what i had in mind for a new hud and new/load screen, i think they are way more streamlined and detailed, i love the way this hud works.

@KingCharizard

So it seems you are experienced with scripts, aren't you? Now from reading all those comments from you, it seems I was wrong with you. You are not an grumbler, you are an experienced player who believes that the Project Zelda Engine can be re-organized and revamped?.
I apologize for my "frivolity" of my answer to your very first comment yesterday. Sorry if I was a not so nice girl with you. Your not so nice and clear critic in your first comment didn't help me understand what you was talking about. I didn't expect that this critic it is coming from someone with ideas for PZE. I wrongly expected that you was just a grumbler... And I deeply apologize for this. I just realized, through your further comment posts, that you seem you got some ideas on the PZE. Why not joining the PZE developing team? This is what we are looking for. People like you, Chakanevil, and Night_Runner, people who have vision of a true starter kit that is more capable, more organized and easier in use. You may not be aware, but we already did the first step toward this way: We turned the Common Event-based Inventory Menu into a full script Inventory.

We have the same goals. The goal is to re-organize the engine and make it function better. Remember all those 5 switches for a simple Speech event you mentioned? I agree with you, they have to be eliminated and be absorbed by the Engine itself. But the problem is: I am not scripter at all! I have no idea about scripts! Here Night_Runner, Chakanevil and Derula come for! They are amazing guys, very kind, they always help on my efforts to improve the Engine and make it better! They have as goal to make the PZE even better and even better! Here you come! We need more scripters. The more scripters we get, who share the dream of a better Project Zelda Engine, the better! We really want anything the people can offer to the engine. To be scripted and more user-friendly. Make it simplified but without sacrificing flexibility. If you don't believe me when I am saying that you and we have the same dreams, and to see in the future, a more advanced, improved and organized Project Zelda Engine, then you can check the Update Patch 3's notes on the first page of the forums: We already did now the first step to this way: we are turning the whole HUD, the whole Inventory and all the game menus into scripts! As you see, the original Project Zelda Engine's inventory, menus and HUDs were made of Common Events...: Including the the rupees/weapon ammo (bomb, arrow) calculator, to the HUD and the inventory! Turning the event-based inventory into a script-based is a fact of what Project Zelda Engine we want.

After reading all those comments by Chakanevil and you, KingCharizard, I realized how many people are out there, who want the best for the PZE! It is up to you KingCharizard, if you want to unite your powers with us the community and help improve the Engine in ANY ways you can! In any ways you may know!

KingCharizard, what we are looking for, is more people like you and Night_Runner. I see you share same goals with us from what I read in your comments.

You said you downloaded the Project Zelda Engine and you tried it out? OK, I assume the version you downloaded is Update Patch 2 or older. Here I give you the most recent version of PZE, which you can download, and which has the Event-made HUD and Inventories turned into Script-based ones (The Inventory, for example, now is multi-screen and is seperated into 4 different screens: Equipment Screen, Quest Status Screen, Map Screen and Inventory Screen, in which you can navigate with PAGE UP and PAGE DOWN keys)









Night Runner's comment: How the Inventory Menu screen works from now:


Download link of latest version of Project Zelda Engine (Update Patch #3)
http://www.4shared.com/file/AEkplzik/The_L..._Project_Z.html


KingCharizard, we only did turned the HUD and Inventory Screen into scripts so far. And I am pretty sure you will like them now.

I hope you will join the project Zelda Engine team and we will help each other (your ideas are highly welcomed!) and make a true Zelda-styled engine, which is easier for use. If you are interested in Project Zelda Engine, nothing can stop us from accomplishing those goals. I am not scripter, that is why you see poor work with scripts in the Project Zelda Engine. Because we only have 1 scripter in our team (Night Runner, who did the amazing script-based Inventory Menus and HUDs) and a starter kit usually needs more scipting hands to work on it
We may not have more than 1 scripter at this moment, but we have a tileset editor (yes, me, I am good at tilesets - most of the tilesets of the engine are made by me using resources from net, and a 25% of it's total tiles are created by me, from scratch). Our team also has a mapper, (me again), some eventers, sprite finders (such as Wormy) and of course Chakanevil who's the role is not very specific - he helped us in many ways I couldn't imagine at all. I also can make very good maps. (the maps and tilesets are my talent, see the OOT's Kakariko Village Map, you could love it!), Chakanevil has some experience on scripting and he is good at script finding and he searches the net for script resources. He will be glad to help you find whatever you need for your work with PZE. And Night_Runner is the only scripter our team has so far, but his job is very valuable, he has done so many nice things to the engine! Many nice scripts are by him! His work really makes a great difference between the old Project Zelda Engine (as it was 4 years ago), with the current Project Zelda Engine!

If you join, we can finally unite our powers, and revamp drastically the old Project Zelda Engine, and make it even better for the community to enjoy!
You will, much like Night_Runner does, have the free to do whatever improvements/modifications to the engine without worrying about us, we are always here to help the other team mates. We welcome any changes done/planned to do to engine and we always support the teammates in their work!, For any troubles you might find in the engine, feel free to ask me or the other team mates for help or resources. Although as a mapper, I am useless to you, because I only make events and maps, and I only maintain the PZE's forum pages.


The team is always open to people who are willing to revamp and improve the PZE. Our goal is to improve the way the Engine works and we really need you. We should unite our hands and efforts so to make an engine capable of the demanding gamer's community and be friendly for use. You are welcomed to join the team and do whatever changes you like to do in the engine if you want. Much better together rather than separately

so what do you think of the new hud i suggested Silent?

it would be pretty cool, if KingCharizard joined, even if he wants to create a system like xasabs, or even blizzard abs, but honestly I was kinda seeing xasabs as being the system to use, because it uses this feature. I think he could get some ideas from this system that would be useful even in the least.

@Chakanevil

Hehe, I love that HUD! Aye, a "intelligent" hud. But what I don't understand is how can a HUD understand what type of event the tile next to Link has, (NPC? Jar? Treasure chest?) is so it can show the appropriate action such as Talk, Pick Up, Open, etc...

No idea lol

The scripts are a big mystery for me and always will be. Too bad I know nothing about scripts and scripting.

Incredible Is this made with XP or VX

Platform: RPG Maker XP

@SilentResident
do you think maybe knight runner could look over it?

No worries, your previous comments are not ignored, mate. Just every thing on time!


Your comments are very helpful. Keep posting! We will add them in the plans list and set priorities which ones we shall do in the next Update Patch and which ones we will leave for later patches.

I played the download toyed with it a little and what not and while its an imporvement its not much, im curious who's making the switches and the common events ect? because if you didnt know all your doing by using the commands is having RMXP create the script fot you, because a conditional branch is basically a if loop, and from what i've seen this is a very complex kit using all commands and a few scripts. oh and i noticed an error with your rupee event it doesnt add rupies after you get one atleast it didnt add my red rupee as 20 rupies.. Also your invintory screen doesnt update as well the bombs and arrows..

and why does your link look like a fat retarded smurf.. hahahaha im curious is this a ported version of the rm2k3 sdk made back in 2005? if it is I had worked with the SDK and accomplished most of the working systems.

@KingCharizard


First of all: most of the switches were already part of PZE when I picked it up. I didn't liked it either, but I added even more switches to it, especially for the Loot settings, weather and time configuration, and weapon parameters. The new switches added by me are mostly for the functions of the weapons/items and because I had no scripting knowledge to do otherwise. It was just my love for the Zelda games that kept me continuing the work on it, with the hope that one day we will convert them into scripts.

About the error with rupees / bombs / arrows: sorry I forgot to let you know which events-samples we have updated as we are doing the new HUD and inventory:

Working rupees and bombs:

This is a shrub that has been updated to work with the new system - its loot is fully working with the new HUD.


And a working enemy


Just those 2 samples we updated so far. The rest will be, soon!


By the way, if you want the new menus to have weapons/items, go to the Cathedral map and open a treasure chest in front of the cathedral's entrance. Enjoy!

Oh hey cool you released V3! I didn't even realize it because the title didn't seem to change! I shall DL it and see what there is to do!

And this is my second most hotly anticipated project/GDK, after the Fire Emblem XP project.

@Klokinator
that's not the official patch 3, that's more of what i would call 2.5


@KingCharizard

Mastermind / Aceofspades is the original creators but they discontinued the project.

btw knight have you experimented with xasabs any, what else needs updated besides the hud, so I can come up with some fresh ideas, suggest some scripts we may need, so i can go look for them.

The Project Zelda Engine is a really old project, and it already counts 2 developing teams. Mastermind's team was the original one, they were the ones who created the basis for the future teams to continue the work on. nice zelda-styled pixel-based movement script, and the script that allows you to use spritesets of which their width is less than 4 tiles (such as 1x4, 2x4 and 3x4 spritesets - with few words, smaller width than the standard 4x4 the default RPG Maker XP is programmed to read), the animated Intro screen, the New/Load File Display screen, etc.

I'm currently working on a way to intergrate XAS battle system into this, if i have any success i'll let you know