[XP] Ring menu mods [RESOLVED]

mroedesigns · December 29, 2010, 10:00:49 pm

I absolutely love the ring menu for RPGmXP. I think it's super awesome, so I'm using it. But I'm also using Blizz ABS, so I had to add options for Hotkeys, and AI Behavior and Triggers. I don't know a whole lot about scripting, but I can do basic things like this. I got the additions there, and they're working, but there are a few little errors and things that need changed.

First off, does anyone know how I can bypass the actor selection window? My game only has one character in the party at any given time, so there's really no need for that window to pop up.

Another issue I can't figure out how to fix, is that when you use one of the new additions (Hotkeys, behavior, or triggers) and hit 'Esc' to return to the menu, it instead takes you directly back to the map.

If anyone could help me, that'd be great.
Here's the modified script.

Spoiler: Show

yuhikaru · December 30, 2010, 07:28:17 pm

Hi there. First of all, I'm not a scripter. But it's really easy, so I think I can help you.

In def update_command you have to change what happens when the player selects equipment, skills and stats. What the code says is to show and activate the @status_window (the character select thingy). You just have to remove that and call the scene directly from there.
Taking 'Skills' as an example, in def update_command:

when 1  # Skills
      # ???? SE ?????t
      $game_system.se_play($data_system.decision_se)
      # ?X?e?[?^?X?E?B???h?E???A?N?e?B?u?????
      @command_window.active = false
      @status_window.active = true
      @status_window.visible = true
      @status_window.index = 0

Would become something like this:

when 1  # Skills
      # ???? SE ?????t
      $game_system.se_play($data_system.decision_se)
      # ?X?e?[?^?X?E?B???h?E???A?N?e?B?u?????
      $scene = Scene_Skill.new

After you did that for all the other options, you can remove all that refers to the @status_window in this script, in def main, def update, def update_status and so on, as you won't be needing it. I'm almost sure that's all you have to do, if not, someone please correct me =/

As for the other question, you have to search where the scene is closed. As you said, pressing esc (B). In this script for example, it would be this part, in def update_command:

if Input.trigger?(Input::B)
    $game_system.se_play($data_system.cancel_se)
    $scene = Scene_Map.new

When you press the cancel key, it calls $scene = Scene_map.new. You just have to change that, type $scene = Scene_Menu.new instead. You can use it like $scene = Scene_Menu.new(1), 1 being the index of the command menu. This way it would return to the command menu on the skill option.

Hope it helps, good luck with that ^^

mroedesigns · December 31, 2010, 01:13:09 am

Quote from: yuhikaru on December 30, 2010, 07:28:17 pm
Hi there. First of all, I'm not a scripter. But it's really easy, so I think I can help you.

Any help is appreciated

Quote from: yuhikaru on December 30, 2010, 07:28:17 pm
In def update_command you have to change what happens when the player selects equipment, skills and stats. What the code says is to show and activate the @status_window (the character select thingy). You just have to remove that and call the scene directly from there.
Taking 'Skills' as an example, in def update_command:
#...
Would become something like this:
#...

Ahh, that fixed that problem

I was just making it too complicated :p Thanks!

Quote from: yuhikaru on December 30, 2010, 07:28:17 pm
As for the other question, you have to search where the scene is closed. As you said, pressing esc (B). In this script for example, it would be this part, in def update_command:
if Input.trigger?(Input::B)
    $game_system.se_play($data_system.cancel_se)
    $scene = Scene_Map.new
    
When you press the cancel key, it calls $scene = Scene_map.new. You just have to change that, type $scene = Scene_Menu.new instead. You can use it like $scene = Scene_Menu.new(1), 1 being the index of the command menu. This way it would return to the command menu on the skill option.

One would think. However, here's the odd thing.

Only the three options that I added (Hotkeys, Behavior, and Triggers) return to scene_map. All other options return to the menu, however they return on the previous index. (Equipment returns on the hotkeys option, stats returns on the equipment option, ect) Items and skills, the two before 'Hotkeys' work fine and return correctly.

So it's obviously got something to do with the way that I added the options, or something that I did incorectly in the indexes. But since the script isn't mine,
im not a very skilled scripter, and there are no comments, I'm somewhat lost. That and the fact that some of them are returning correctly, makes me thing there must be something in the script I'm missing. Here's the current script, I commented on the parts that I edited.

http://pastebin.com/WHwF9biY

yuhikaru · January 01, 2011, 07:32:02 am

Actually, it's in the scenes themselves. You have to search in each scene (Skills, hotkeys, equipment.....) for the exiting part and change it.
The default indexes are 0 = items 1 = skills 2 = equipments 3 = Stats 4 = Save 5 = Exit.
But with your modifications, it became 0 = items 1 = skills 2 = hotkeys 3 = equipment 4 = stats 5 = Behavior 6 = Triggers 7 = save 8 = quit
So the equipment scene, by default, returns to the command menu index 2, that's why it returns to hotkeys.

(I'm assuming you are using the default scenes)
In the Scene_Equip you have to look for

$scene = Scene_Menu.new(2)

in def update_right and exchange (2) for (3), the new index.

The same for all of them, stats, save and exit.

Now, in the hotkeys, Behavior and Triggers scenes you probably just have to look for:

$scene = Scene_Map.new

And substitute it for

$scene = Scene_Menu.new(x)

x being 2 for hotkeys, 5 for behavior and 6 for triggers.

Well, try that xD I'm not familiar with BlizzABS at all, so I'm not sure... =/
Happy new year, by the way <3

mroedesigns · January 01, 2011, 04:01:50 pm

Ahh! I figured it out, thank you!!

It was a pain because a few of them were in the Blizz ABS script [pt 3 if anyone else is wondering], and a few of them were in the Z-Hud script I was using.
But I got it all working now, I'm gonna go post it in the scripts section for others.

Thanks a ton guys!
And happy new years to you as well

Chaos Project

[XP] Ring menu mods [RESOLVED]

mroedesigns

December 29, 2010, 10:00:49 pm Last Edit: January 01, 2011, 04:31:50 pm by mroedesigns

yuhikaru

December 30, 2010, 07:28:17 pm #1 Last Edit: December 30, 2010, 07:30:42 pm by yuhikaru

mroedesigns

December 31, 2010, 01:13:09 am #2

yuhikaru

January 01, 2011, 07:32:02 am #3

mroedesigns

January 01, 2011, 04:01:50 pm #4