[XP] Blizz-ABS

[Blizzard]

if result && !(@charge.action == BlizzABS::CHARGESkill && BlizzABS::Skills.type(@charge.id)[0] == BlizzABS::SUMMON || @charge.action == BlizzABS::CHARGEItem && BlizzABS::Items.type(@charge.id)[0] == BlizzABS::SUMMON)
  @charge = nil
end

[RoseSkye]

if result && !(@charge.action == BlizzABS::CHARGESkill && BlizzABS::Skills.type(@charge.id)[0] == BlizzABS::SUMMON || @charge.action == BlizzABS::CHARGEItem && BlizzABS::Items.type(@charge.id)[0] == BlizzABS::SUMMON)
  @charge = nil
end

I put this under..

    def self.summon(id)
      return [SUMMONNone, 0, 0]
    end

Amirite?

[Landith]

NO!

Part 3.
Lines 642, 680, 715

Change the @charge = nil

to what blizz said

(I think...)

[RoseSkye]

NO!

Part 3.
Lines 642, 680, 715

Change the @charge = nil

to what blizz said

(I think...)

I told you guys whenever I try to edit the RGSS it ends with dead kittens >=/.

*sniff* I read tutorials and everything *sniff*


Also Line 642 = comment. :/ I'll just search for @charge = nil.


I broke it >.>

[Jragyn]

Curious question, pointed at anyone knowledgeable of the system behind the BlizzABS:

Can I use a controller this script instead of the WASD+all the keys required to...control?
I notice that when I plug in a my Logitech controller, this script just seems to disable it entirely.
No buttons respond, no anything works, and I think it'd be nifty to not need the entire keyboard.
I know, there are more keys required than available on even a PS2 controller equivelant...
but should at least -some- of my buttons work?
If I could function essential things, like movement, attack, menu, run, etc...leave out a few things
like switching on/off the HUD, or the skill display, etc...
I dunno.
Can it be done?

[Landith]

@Rose: Send my your script and I'll see if I can get it to work (only part 3)

@jragyn00: I believe that because blizzard uses the Input::Key["BLAH'] which makes it were you have to use a keyboard for it... :/

[RoseSkye]

I can't upload the pt 3 of the script.
I assure you it is unedited, so .. if you have pt 3 of Blizz's ABS 2.23 you have my pt 3.

[Blizzard]

@charge = nil is in Part 3. It should be at the position that Aqua mentioned.

@jragyn00: Use Joy2Key or whatever the program is called like. We've discussed it a few times at the forum, try running a search.

[RoseSkye]

@charge = nil is in Part 3. It should be at the position that Aqua mentioned.

@jragyn00: Use Joy2Key or whatever the program is called like. We've discussed it a few times at the forum, try running a search.

I did it but I didn't do it correctly.

 @charge = nil if result
    # return result
    return result
  end

I replaced those lines with the ones you told me and an error popped up.

[Blizzard]

Not all of them, only "@charge = nil if result"

[RoseSkye]

I think this is a valid bug.. instead of my annoying inquisitive prattling.



I tried disabling ABSEAL on that map.. but.. nope.. still buggy.

[G_G]

Curious question, pointed at anyone knowledgeable of the system behind the BlizzABS:

Can I use a controller this script instead of the WASD+all the keys required to...control?
I notice that when I plug in a my Logitech controller, this script just seems to disable it entirely.
No buttons respond, no anything works, and I think it'd be nifty to not need the entire keyboard.
I know, there are more keys required than available on even a PS2 controller equivelant...
but should at least -some- of my buttons work?
If I could function essential things, like movement, attack, menu, run, etc...leave out a few things
like switching on/off the HUD, or the skill display, etc...
I dunno.
Can it be done?

It can be with a ps3 controller I've dont it before.

[RoseSkye]

Also

undefined method `action' for nil:NilClass

[Landith]

When reporting a bug, describe what you did before the bug...

The event tileset option isn't working at this point in time, but Blizz is working on it. It's been reported about 5 times so yeah...

[Blizzard]

I'm not working on it, I simply lack the time to just open Blizz-ABS. There's always stuff that's currently more important. ._.

@RoseSkye: That's because of the code I gave you. Try this fixed one:

if result && @charge != nil && !(@charge.action == BlizzABS::CHARGESkill && BlizzABS::Skills.type(@charge.id)[0] == BlizzABS::SUMMON || @charge.action == BlizzABS::CHARGEItem && BlizzABS::Items.type(@charge.id)[0] == BlizzABS::SUMMON)
  @charge = nil
end

Man, what a conditional statement. #_#

[Jragyn]

After investigating the forums a bit, two programs came to light.
JoyToKey, and Xpadder.
I've tried both of these programs, and they work.
At least, they work everywhere but in RPG Maker.
Originally, the RPG Maker XP does carry its own controller compatibility thingy,
which works just dandy by itself,
but in any project that has BlizzABS in the scripts, my controller is useless.
Even in conjunction with Xpadder, or Joy2Key (which I will restate: work flawlessly anywhere else.)
Neither of them seem to work and go utterly unrecognized.

I don't get it.
Why does the controller work anytime but when BlizzABS is installed?
I don't even get partial control.

Spoiler: ShowHide

BlizzABS is too cool for failure.
I will find a way.

[Blizzard]

Because Blizz-ABS uses a custom control module which isn't working with joypads. Those programs should actually work on a keyboard basis so that when you press a button, it simulates key input. GAX had no problem using JoyToKey in Chaos Project that uses an almost identical input module.

[G_G]

After investigating the forums a bit, two programs came to light.
JoyToKey, and Xpadder.
I've tried both of these programs, and they work.
At least, they work everywhere but in RPG Maker.
Originally, the RPG Maker XP does carry its own controller compatibility thingy,
which works just dandy by itself,
but in any project that has BlizzABS in the scripts, my controller is useless.
Even in conjunction with Xpadder, or Joy2Key (which I will restate: work flawlessly anywhere else.)
Neither of them seem to work and go utterly unrecognized.

I don't get it.
Why does the controller work anytime but when BlizzABS is installed?
I don't even get partial control.

Spoiler: ShowHide

BlizzABS is too cool for failure.
I will find a way.

I've done it before google a program Total Game Control, download it install it, then open it. Start a new profile called Blizz ABS then in the device list choose your USB Controller. Then go to the Control Tab and press new then type in the following things

Description - Action Key
Trigger - Check the box, hold down the button you want to be teh Action Key then hold it down while you uncheck the box.
Key(s) - h (all you type for this is a lowercase h)
Click OK

Do a new one again type this in
Description - Cancel/Menu
Trigger - Check the box, hold down the button you want to be teh Action Key then hold it down while you uncheck the box.
Key(s) - f

Do this until you have all of the keys done for Blizz ABS. And I recommend instead of using the Analog Sticks to move use the Direcitional Pad. I used both analog sticks to select my hotkeys. Here are the special keys you'll need.

<UP>
<DOWN>
<LEFT>
<RIGHT>
,
m
w
a
s
d
j
k
l
i
o

Now when you're setting the analog sticks to be hotkeys 1-9 hold up the analog stick, uncheck the trigger box then type in 1 in the key(s) box and do the same. This way you'll only be able to have 1-8 hotkeyed but it still works out for me.

[RoseSkye]

*looks up*
  *looks down*
*looks up*
  *looks down*


Holy crap! Blizz didn't know something about his own ABS!
WHERE IS MY GOD NOW! I NEED HIM!

[Blizzard]

What did I not know?