[XP] Blizz-ABS

[The Niche]

I'm pretty sure it's there, just hard to find. Or maybe that's something else, can't remember.

[winkio]

nope, I compiled it wrong, Rose is right.  It looks like htm2chm is acting up again...

[The Niche]

Woops...that must've been xp I was thinking of.

[Futendra]

When using items that heals + gives positive status effects (or status effects in general) I get this error;

'BlizzABS pt. 3' Line 954: NameError occured
undefined local variable for method `_battler' for #<Game_Player:0xa48e620>

change _battler to @battler, in both lines

[winkio]

That doesn't fix it, that just makes the battler think it's attacking itself.  Keep them commented.

[RoseSkye]

That doesn't fix it, that just makes the battler think it's attacking itself.  Keep them commented.

Did you think I'd be stupid enough to take advice from Futendra?

[winkio]

Nope, that was directed at Futendra, not at you.

[megaman30796]

does mode 7 work with blizz abs?

[The Niche]

There's a plugin for it somewhere.

[Futendra]

That doesn't fix it, that just makes the battler think it's attacking itself.  Keep them commented.

Wait I got it fixed with something similar to that, I'll check it up if I have time

[RoseSkye]

Wink, I hate to say it... but... without force action the Blizz ABS becomes really limited. I can't do anything custom anymore because everytime I use force action there is a syntax error which I assume is because you made the skills use force action on top of the force action that I script call.

[winkio]

no, shouldn't be...  Let me test it, what's your script call?

EDIT: Syntax error probably means the script call got split up at a weird place in the event code.  Make sure it's not splitting on square brackets [] or other dumb stuff like that.

EDIT: On another note, 2.83 is up.  New features:
Fixed bug with Manual Event Creation where event name tags would not process.
Added last_hit_by and last_action accessors
Added Multi-Body Enemies.
Added Custom Event Size using pixel movement
Added \cspr tag to center the sprite and hitbox of events.
Completed Combat Memory system, which keeps track of last attackers and targets.
Added experience modes to give exp only to the actor that made the kill, or the entire party, or both.

[LiTTleDRAgo]

there are error in script

      if item.plus_state_set.any? {|s| $data_states[i].slip_damage}

[winkio]

there are error in script

      if item.plus_state_set.any? {|s| $data_states[i].slip_damage}

fixed and reuploaded.  For anyone that already downloaded, change it to

      if item.plus_state_set.any? {|s| $data_states[s].slip_damage}

[RoseSkye]

no, shouldn't be...  Let me test it, what's your script call?

EDIT: Syntax error probably means the script call got split up at a weird place in the event code.  Make sure it's not splitting on square brackets [] or other dumb stuff like that.

EDIT: On another note, 2.83 is up.  New features:
Fixed bug with Manual Event Creation where event name tags would not process.
Added last_hit_by and last_action accessors
Added Multi-Body Enemies.
Added Custom Event Size using pixel movement
Added \cspr tag to center the sprite and hitbox of events.
Completed Combat Memory system, which keeps track of last attackers and targets.
Added experience modes to give exp only to the actor that made the kill, or the entire party, or both.

This is the same force action code I used with previous versions nothing has changed.
$BlizzABS.enemy_force_action(2, ACTORS, 0, SKILL, 11)

[winkio]

All I can say is that I copypasted, changed the enemy ID to match my game, and it worked.  Demo me if you can.  And does everyone have problems with force actions, or is it just Rose?

[RoseSkye]

It's F-Zero's add ons. I had it with v. 1.80 and it worked fine though.

[winkio]

Are the addons above or below Blizz-ABS?  Also, could you give me line numbers or which addons error?

[RoseSkye]

Are the addons above or below Blizz-ABS?  Also, could you give me line numbers or which addons error?

Above (like ToA). The range conditions were causing the error (which was the only reason I used it).

[winkio]

really?  I just put it in and turned on range conditions, and my force actions still work.  What's the error message?