i need some help with some difficult work.

[monkeyman1188]

Hello everyone.

So im new here but im not a newbie as such, im a very quick learner but some things i just cant figure out on my own, even with staring at the tutorials for a few hours, i think im trying too much too soon.

so I've created a battle event thant is all good and fine, but it doesnt disapear once its finished. i can just walk onto it again and again, which i dont want to.

I've written lots of different lines and codes to try to make it a one attack thing but it still stays on the map or should i say, in the basement. lol

thats one problem.

the next is, that monster who i've just killed has dropped a key. This key will open a door, but i cannot seem to find the correct writing for this to work.

i think i have tried almost all of the combination but where i have been thinking so hard, ive burnt out.

And one more thing, sorry peeps.

Can you make events that change certain tiles on the world map??

You see i want to cut down a tree, ive made it so it is impassible and that i need a certain item or weapon to use on it, but i cant seem to make that tile piece go from a tree to a normal floor tile. Is that even possible.

I know ive started hard but i always dream big, start hard and everything seems to fall into place.

many thanks

Rob

 

[Lunarea]

All three of your issues can be solved with a use of switch and a conditional page. In the case of a tree, it would involve using an event for the graphic (rather than just mapping in the editor), but the rest of the process is still using a switch and a condition page.

Here is a link to a switch demo/tutorial that will walk you through the process.

 

[Euphoria]

That's not really starting hard, those are basics of eventing. You should have learned that in the tutorials :x

Tree, make the event graphic for the tree, set a conditional branch on if you have an axe or whatever, then if you do, set a self switch, and open a second event page. On the new event page leave the event blank. Done.

 

[Lunarea]

It might seem super simple once you've got the basics down, but it does take a little while to start thinking in eventing terms. Things that seem to be simple and logical to us (like when to use a switch, for instance) are simple because we've trained ourselves to approach eventing problems with a good knowledge of what different commands do. So, it's a bit like a puzzle where we're familiar with all the shapes and just need to figure out how to fit them together. But it's more challenging for those who are just getting into the program. They might read a tutorial and know what a command does in theory, but still not how to apply it to an obstacle/challenge/problem/feature/etc in their project.

So, please keep working with RM, monkeyman! It'll get easier once some of the concepts click for you.

 

[Zoltor]

It might seem super simple once you've got the basics down, but it does take a little while to start thinking in eventing terms. Things that seem to be simple and logical to us (like when to use a switch, for instance) are simple because we've trained ourselves to approach eventing problems with a good knowledge of what different commands do. So, it's a bit like a puzzle where we're familiar with all the shapes and just need to figure out how to fit them together. But it's more challenging for those who are just getting into the program. They might read a tutorial and know what a command does in theory, but still not how to apply it to an obstacle/challenge/problem/feature/etc in their project.

So, please keep working with RM, monkeyman! It'll get easier once some of the concepts click for you.

Infact, frankly I wish people new to RPG Maker wouldn't run to a tutorial right away, they should spend upto a month familiarizing them selves with all the event commands, and toying around with figuring out how eventing/each event command works(pay no mind to working with the database, you can start with that at a much later date).

Odds are overwhelming that they'll pickup on things fairly fast(learn how to event, by doing), and they'll have a much better understanding about eventing in general, opposed to having someone try to explain how things work, which there's a pretty high chance, the new comer wouldn't really understand what the person is trying to convey anyway, because they're not familiar with the "functions" of the event commands to beginwith.

Say after a few weeks or so, if they find themselves having problems with certain things, then they should check out tutorials. This way, tjhey should at very least already have a grasp on most of the basics, and could easily understand what a tutorial is saying.

 

[monkeyman1188]

hello everyone

First of all thank you for posting and trying to help.

i have a reply for all of you,

Zoltor, i completely agree, i need to play around myself, that i have done a little bit, i know the basics of the event commands and how they run, but i want to know the more difficult things, thats why i went to the tutorials, but i learn more through being shown than just reading, so thats why i asked the forum.

Euphoria, ill give that a go to see if it works. thanks

Lunarea, thank you for your understanding that some things that look easy to some people may be harder to grasp to others. and thank you for the demo, that will hopefully help me pull through this switch nightmare lol

all of you, many thanks

Rob

 

[Andar]

You also might want to follow the link i my signature to an overview that should help you select what tutorials and how to start learning RM.

 

[TheGreenHorse]

Really? I just figured out what and how to do all this in my first event. Not offensively saying but euphy is actually quite true.

 

[monkeyman1188]

Hey Green horse,

what input is that?

if you didnt like my questions, why post anything at all.

please push off, you're cramping my learning.