Full Games List
Featured Games
New Games
Reviews
Media
Images
Blogs
Game Updates
Images Feedback Summary
Game Design Highlights
Tutorials
Articles
Scripts
Utilities / Plugins
Resources
Engines
Engine Bulletins
What is Makerscore?
Past Events
Achievements
Misaos
Forums
Post History
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
RM2K3 HAVING ISSUES IMPLEMENTING IDEAS
Posts
Dark-Watcher
View playlists
CloseYea that tutorial was what I had used first. But somehow it didn't work out. lol jumping back and forth between to Monster viewing systems is so fun (not) I'll check out what Trihan said first and if that doesn't work blah!
author=Dark-Watcher
Are these right?
OK for easy understanding I made an illustration.
scene 1 You see him he doesn't see you
scene 2 You don't see him he does see you
scene 3 You see him he doesn't see you
scene 4 You don't see him he does see you
scene 5 You see him he doesn't see you
scene 6 You don't see him he does see you
scene 7 You see him he doesn't see you
scene 8 You don't see him he does see you
(obviously)
So for each of these would I be using 2 or 4 fork conditions?
ex.
If hero facing up
--If monster facing up
----If hero Y is greater than monster Y
that would be scene 6 right?
Now would I have to make one for say
If monster facing up
--If hero facing up
----If hero Y is greater than monster Y
would the first one only work since it only when hero is facing up?
MakoInfused
210
Yeah, sorry you had to switch-- but what kind of a system name includes "radial" and yet is actually directional? Lol.
Well no, the two examples you provided are exactly the same. Neither one will execute unless all of the conditions are fulfilled, and they're both exactly the same except in a different order (the two facing checks are ordered differently).
Well no, the two examples you provided are exactly the same. Neither one will execute unless all of the conditions are fulfilled, and they're both exactly the same except in a different order (the two facing checks are ordered differently).
O.k I'm lost...
I have:
Branch If this event facing Up
--branch if if hero y is greater than monster y
then monster moves towards hero
else
If hero y is less than monster y
nothing happens.
and he still detects you even when he is facing up and you are behind him
I have:
Branch If this event facing Up
--branch if if hero y is greater than monster y
then monster moves towards hero
else
If hero y is less than monster y
nothing happens.
and he still detects you even when he is facing up and you are behind him
TheNecromancer
3160
I have some suggestions.
First of all, in regards to your monster events. You should remove any pages that will be used to control the monster in any way, and put them in their own events. If you make other pages on the monster trigger, it will stop it from tracking coordinates or whatever.
As for the sight detection, I suggest a new method entirely. As what you're trying to do now seems to have a lot of branches.
Start by adding this in your game - http://rpgmaker.net/tutorials/16/
Get it working and understand it a little. It's much less work for a full radius of sight.
Then you would add a branch to make it only see in the front half of that radius. So check facing and only allow it to trigger if X is greater than something, or less than something. I forget exactly how I set up mine.
I think that pretty much solves the problem of knowing when the hero is in front of the monster.
You're doing well for a newbie :3 Are you making an ABS game in 2k3?
Did you get the answers you needed for your second question from the OP? I just skimmed through the posts.
First of all, in regards to your monster events. You should remove any pages that will be used to control the monster in any way, and put them in their own events. If you make other pages on the monster trigger, it will stop it from tracking coordinates or whatever.
As for the sight detection, I suggest a new method entirely. As what you're trying to do now seems to have a lot of branches.
Start by adding this in your game - http://rpgmaker.net/tutorials/16/
Get it working and understand it a little. It's much less work for a full radius of sight.
Then you would add a branch to make it only see in the front half of that radius. So check facing and only allow it to trigger if X is greater than something, or less than something. I forget exactly how I set up mine.
I think that pretty much solves the problem of knowing when the hero is in front of the monster.
You're doing well for a newbie :3 Are you making an ABS game in 2k3?
Did you get the answers you needed for your second question from the OP? I just skimmed through the posts.
Currently I have the monster set up with two pages. The one page controls it using the previous mentioned radial sight method, the other only triggers when a switch is on and makes it so when you touch it a battle ensues.
(edit) Also that tutorial you linked is what I'm using, the trouble I'm having with it is I don't want the monster to see you when you are behind it. However, when using the variable coordinates X and Y to determine where you are relative to where the monster is facing is causing me trouble. Right now the monster detects a 4x4 radius around it which is nice but it sees you when its not facing you and I don't like that.
No, this is just so you can avoid monsters when you want and other little things for later. And thanks!
I'm sure when I get to the battle system I'll be even more frustrated! >_<
(edit) Also that tutorial you linked is what I'm using, the trouble I'm having with it is I don't want the monster to see you when you are behind it. However, when using the variable coordinates X and Y to determine where you are relative to where the monster is facing is causing me trouble. Right now the monster detects a 4x4 radius around it which is nice but it sees you when its not facing you and I don't like that.
No, this is just so you can avoid monsters when you want and other little things for later. And thanks!
I'm sure when I get to the battle system I'll be even more frustrated! >_<
This is what is wrong. Say my monsters coordinates on the map is
010,008 so its x value is 10 and y is 8
now when its facing Up if hero is in x of 10 and y of 7 he would be infront of the monster and that would be
Branch hero y greater than monster y
problem here is even when hero is at say x of 10 and y of 9 the monster still sees you even while facing up...
010,008 so its x value is 10 and y is 8
now when its facing Up if hero is in x of 10 and y of 7 he would be infront of the monster and that would be
Branch hero y greater than monster y
problem here is even when hero is at say x of 10 and y of 9 the monster still sees you even while facing up...
TheNecromancer
3160
I'll make an example project and upload it for you.
I personally don't like the 2k3 default battle system. If you want to make an RPG, use the normal version. If you want to make a good RPG, add dynRPG u.u
I would also suggest using Ultimate 2009, if you aren't already. http://cherrytree.at/cms/lang/en/projects/ultimate/
I personally don't like the 2k3 default battle system. If you want to make an RPG, use the normal version. If you want to make a good RPG, add dynRPG u.u
I would also suggest using Ultimate 2009, if you aren't already. http://cherrytree.at/cms/lang/en/projects/ultimate/
TheNecromancer
3160
Click me
I hope you don't mind Star Trek xD I picked it because it's a project I already had created that has the proximity event already setup. I added the branches for each direction, and set up one to show as an example. You would just change the values for X/Y and greater than/less than for each direction.
I also added an extra bit as an example for how to show an exclamation point above the events head, although you'd probably want to use pictures instead an event/switch.
Often time when something doesn't work when it should, you should go in and check all the values again. Makes sure it's using the proper SET/ADD/SUBTRACT command, and pointing to the right variable. As I was doing this example, it didn't work when I first tested it heh I forgot to make it SET the variable, instead of subtract.
I hope you don't mind Star Trek xD I picked it because it's a project I already had created that has the proximity event already setup. I added the branches for each direction, and set up one to show as an example. You would just change the values for X/Y and greater than/less than for each direction.
I also added an extra bit as an example for how to show an exclamation point above the events head, although you'd probably want to use pictures instead an event/switch.
Often time when something doesn't work when it should, you should go in and check all the values again. Makes sure it's using the proper SET/ADD/SUBTRACT command, and pointing to the right variable. As I was doing this example, it didn't work when I first tested it heh I forgot to make it SET the variable, instead of subtract.
TheNecromancer
3160
author=Dark-Watcher
Says: the file system4 cannot be opened..
That's weird...it worked for me. That kind of error usually happens when the you don't have the RTP installed.
When you get an error like that in any RPGMaker game, you can fix yourself by placing a file with that name in the right folder. That one would go in the System folder. Sometimes another error will pop up with a different file. There are a few ways to fix the whole thing.
If you want to open that project in the editor, you should be able to look at the code. Find the hero starting point and look at the event called Ryker. It's all in there.
Or you can just see it here:
Anything referencing "Door" means this event. It used to be a door haha
Ugh! Finally got it to work. so basically what I was doing wrong was forgetting to re establish hero x,y and monster x,y
I had a parallel process running to constantly check them both so maybe it was interfering. After adding in the If facing (direction) re-check both x,y it works!
THANK YOU A BUNCH!
and thank you everyone else for helping as well~<3
I had a parallel process running to constantly check them both so maybe it was interfering. After adding in the If facing (direction) re-check both x,y it works!
THANK YOU A BUNCH!
and thank you everyone else for helping as well~<3
