[XP] Blizz-ABS

[raXor]

You haven't set up your passability properly or you have turn on your hero's "Through" flag which allows him to go through anything.

everything is set correctly ... also because the tileset and the heroes are the default ... My "pixel moviment rate" is 3 ... Maybe it's a bug I just me ... I hope not! 

[elmangakac]

Hello... I check the manual and i dont see one thing... (if its there... Sorry)....

Is that a way to do that the enemie active the action withuot die... And only when the player hit with a CRITICAL HIT??

Example:

The player hit the enemy with a critical hit and the enemie moves 6 tiles away from the player but...without die...

???


Thanks To All

[winkio]

no, there's no critical hit trigger yet.  Sorry.

[elmangakac]

no, there's no critical hit trigger yet.  Sorry.

Ok...Thanks anyway to all ^_^

[raXor]

qualcuno sa risolvere il mio problema?? 

[winkio]

try using a different key for running.

[PhoenixFire]

Not sure if this is the place to post this or not...


Blizz ABS 2 encountered a runtime error on line 1351. Line 1351 is: var=0


Blizz ABS 2 is just the second part of the script, and that's how i named it. I get this error when I encounter an enemy, on the second map that has enemies in it, third map overall.

[winkio]

I don't see how that's possible, it's just initializing a variable, check the line number

[PhoenixFire]

Script 'Blizz BAS2' line 1351: RuntimeError occurred

2

[The Niche]

Erm, post the line?

[PhoenixFire]

Blizz ABS 2 encountered a runtime error on line 1351.

Line 1351 is: var=0

[winkio]

I'm not joking when I say that's impossible.  try re-downloading/re-copying the script.

[PhoenixFire]

Well, I did some troubleshooting, and I narrowed it down.. It only happens when I try to fight enemies other than ghosts.... I made a new test map, threw in a cheat to transport me there, and, I just skipped the map with the issues... The "new" creature on the new map, gave no issues, and, the first map, populated with only ghosts, gives no problems.. I'm gonna try to edit the enemies and see what happens from there... But even still, an enemy type shouldn't affect initializing a variable... That's practically impossible...

[Blizzard]

Best you make a demo and post it.

[PhoenixFire]

If the problem is what I think it is, I'll just change some enemy stats and such, and see if that affects it. If not, I'll probably have a demo posted up tomorrow

[raXor]

try using a different key for running.

Thank you Winkio, now it works! 

[winkio]

Yeah, RMXP has this thing where when debugging, holding down a certain key (I think it's ctrl) allows you to move through any tiles.  It won't affect normal gameplay though (when the game is run through the exe not the RMXP editor).

[PhoenixFire]

Okay, so, my issue with the crash error is solved, however, the battle-scenes are still the same as what RMXP uses by defaukt, and, I can't for the life of me figure out how to make it work.. As in, the fighting styke of zelda, with the battle taking place on the map instead of a cutscene.

[Blizzard]

You don't call the battle scene. You don't create troops at all. You just put events on the maps and name them properly. Blizz-ABS doesn't change the battle scene, it changes the map scene.

[PhoenixFire]

oh... 

-feels stupid-

how the hell did I miss that in the manual?