[RESOLVED] Blizzard's ABS script and Ccoa's UMS

[porkupine]

I am trying to use Ccoa's UMS to display messages over the heads of my party members. I am using Blizzards ABS caterpillar script. However, whenever I try to put a message over my partners head I get an error saying: "
Script 'UMS' line 1286: NoMethodError occurred. undefined method `actors' for nil:NilClass"
I have also tried disabling Blizz's script and using another, but that did not work

[Starrodkirby86]

The two scripts should be compatible with each other. Of course it is, but that error seems to be strange... I can try and emulate it, though I'll need to do a few here and theres.

You might have the script order wrong. Yes, the script order actually matters. Here's a link to the correct placement of various scripts: http://forum.chaos-project.com/index.php?topic=23.0

That's the only solution I can think of at the moment...

[porkupine]

I have them both between Scene_Debug and Main. Blizzards ABS is above the UMS and if i out it the other way around, it doesnt let me play the game. The error is
"Script 'UMS' line 1601: ArgumentError occurred. wrong number of arguments(1 for 0)"

[Aqua]

From Ccoa's manual:

Caterpillar Actor Centering

You can now center the message over a train actor in a caterpillar script.  This is set up to work with my caterpillar script.  For fukuyama's, please see the FAQ.

Her UMS doesn't support Blizz's caterpillar system.

For a fix, you can just make events that are on the same space as the caterpillar actors and have the message appear over those events.

[porkupine]

What if there is more than one place they can be while the messages are coming up?

[Aqua]

$game_variables[XXX] = 
BlizzABS.player.actors[1].x
$game_variables[YYY] = 
BlizzABS.player.actors[1].y

That'll store their Map X and Y in variables. 
Remember to change XXX and YYY to the right numbers and the '1' is the 2nd actor in the party.
(Arrays start with 0)

[porkupine]

I'm sorry but I'm really bad with scripting... Do i replace the XXX and they YYY with the coordinates? and if so i get an error saying
"NoMethodError occurred while running script. undefined method `player' for BlizzABS:Module"

[Aqua]

XXX and YYY are the variable numbers that you want to use.
This scriptlet gets the caterpillar's current map X and Y.

You would use a Set Event Location to make an event where the caterpillar is at

[porkupine]

I get an error saying
"NoMethodError occurred while running script. undefined method `player' for BlizzABS:Module"

[Aqua]

How are you doing that script call...?

[porkupine]

$game_variables[1] =
BlizzABS.player.actors[1].x
$game_variables[1] =
BlizzABS.player.actors[1].y

[Aqua]

You shouldn't have the same variables for $game_variables...  it'll just make it whatever the map y is...

Hm... do you have at least 2 members in your party?

If you do... I don't see why or how you're getting this error...

[porkupine]

I changed the variables to different numbers and I have 2 people in my party, but I still get the same error 

Are there any other ABS that would be easier to use Ccoa's UMS with??

[Aqua]

Hm... gimme a screenshot of the event with that scriptlet...

Blizz-ABS really is the best abs out there for functionality with parties...

[porkupine]

Spoiler: ShowHide

Yo, put images in spoilers, it's a new rule...Um...Rule number 9. ~Love, Starrodkirby86

[Aqua]

http://forum.chaos-project.com/index.php?topic=23.0
Do you have them in the right order?

If you do... then I dunno what's wrong with it then... =/

Oh wait!!!

What version of the UMS are you using?

[porkupine]

I am using v1.7.1

[Aqua]

Ah yeah... there was a bug with the newest version of that last time I checked (which was 3 days ago)

I know for sure that 1.6.3 will work fine with Blizz-ABS

I tried to post it here but then it messed up the board for me... so... yeah...

Lemme upload it

http://www.sendspace.com/file/o79zen

[porkupine]

I still get the error... i'm using v1.0.0.2 of blizz's abs if that makes a difference

[Aqua]

1.0.0.2 is a... very... very... old version...

If you upgrade to 1.99, the problems should all be fixed...