Author Topic: Using a Common Event to Add/Switch Equipment? (Read 2044 times)

#1 • Apr 10, 2010

I'm trying to rig my skills with a common event that allows them to equip weapons or armor for my Grappler class. For example 'Fist' as a weapon. The idea seemed straight forward:

Make a skill called "boxing" or "fist", occasion always, scope the user, common event: "Boxing'
make a weapon called "boxing" or "fist",

then make a common event "Boxing" that only works when called,
1: Text: Switching to Boxing
2: Change Equipment: [My Guy], Weapon = [Fist]

But when I tested it, while the text popped up, "Switching to Boxing', my Equipment list didn't display the "Fist" weapon.

What am I doing wrong?

#2 • Apr 11, 2010

ok so i have to change weapons (weapon choice) to +1
then I have to change equipment weapon = (weapon choice)

if I don't do both, it wont load right.

I now have to figure out a way to only add the weapon to inventory once per person.

#3 • Apr 13, 2010

Here's a simple loop for switching between three fighting styles: Brawling, Empty Hand, and Street fighting. They are represented as both weapons and as skills which call the common events.

For common event: Empty Hand

Spoiler for:

For Common Event: Brawling

Spoiler for:

For Common Event: Brawling

Spoiler for:

For the Common event: Clean Inventory

Spoiler for:

I find this combination works pretty effectively as long as the monk doesn't unequip their weapon/style. Even if that happens, the use of a style, or even a different style will clean the inventory automatically. The only problems occur when you have more than one monk in the group or if you sell the weapon to a shop or something, it looks kind of stupid. I would like to gray-out or lock the styles in the inventory box through script of some sort, but don't know how.

Any ideas on how to make a non "droppable" or non "removable/sellable" item/weapon?

#4 • Apr 19, 2010

Ok, so I have a few things here. First, I don't think this is the right place to request this. Troubleshooting is more or less (from my understanding) a place for tech problems, like say if your game project just wouldn't open. This would be probably pretty posted somewhere like RMXP or RMXP Tutorials. One more thing, instead of posting like you have, which I guess is fine, I understand bumping a topic, but the way you posted...you probably should of just Edited you're first post.

The next thing I'd like to add, is that it seems the way you're going about this might be a bit much. Four Common Events, and loops. These things combined with a full or semi full game would equal lag (Meaning, that you;d most likely will have alot of Common Events and maybe some more loops). I guess it seems, to me at least, that there is an easier way. But to be honest I haven't looked into to, nor have I tryed anything. Your method seems sound, no doubt.

I think I'm going to check into this, try you're way, then try and find a new way. I hope I have and will be able to help. Cheers!

#5 • Apr 19, 2010

The way he's doing it isn't wrong either (though I can think of a slightly more efficient way that I'll explain in a second). He needs a common event per skill. If you REALLY want to create lag, do this all in one common event. That'll blow the game's mind.

To make it a little more efficient would be to add 1 more common event that is the only one that updates. Turn the rest of your common events off and make them have to be called. In that new first common event, constantly check to see if the player is pressing whatever button to check if they want to switch their stances. If the player presses the button, then pull up a choice box and the player can pick from the choices as to which stance to move to. Which ever you choose, will then activate that corresponding common event.

Example:

Conditional: IF Player Press[A]
   .Text:
   ..What stance will you change to?
   .Choices:
   ..Bare Fist
   ...Call Common Event [Empty Hand]
   ..Brawling
   ...Call Common Event [Brawling]
   ..Street Fighting
   ...Call Common Event [Street Fighting]
   ELSE
   ---

So again, you can stop having to check if the player is pressing a button from like a million different common events. Just have it check from one and use that one to then decide the rest.