Problen with fusing "Advanced Targeting" and "RTAB"

[Ultimoore]

Hi, For a while now I have been trying to fuse together Tricksters "Advanced Targeting system" and Minkoff's "RTAB system" my only problem is this
When I tried to test play a problem occurs in the "Edits to Classes" in Tricksters system.

Script 'Edits to Classes' line 172: NameError occurred
undefined method 'main_database' for class 'scene_Title'

So what is did was check it out and see how this could have cause the problem, well after a while I check throught and didn't see any real error in the coding so what I did was deleted the second 'main database' on line 172 and applied the changes. Well after that i started up the test play and a new error came up for line 173 telling me i had a syntac error.

So at this point i got frustrated and came here for help. If i could get some help with this that would be awsome.

 

[Juuhou]

Meh, I wouldnt try integrating any of trickster's scripts with RTAB. The cogwheel RTAB has rewritten many variables which make it incompatible to many scripts. Trickster is working on his own RTAB that will probably work with that script? Oh and its COGWHEEL's RTAB...not Minkoffs.

 

[Ultimoore]

XD Well I'm still working on it the only problem is this error pops up when selecting attack , a spell or targeting with any item.
http://img72.imageshack.us/img72/6055/example1kq8.jpg[/IMG]

Now I went in to check the script to see if I had to change anything into a "true" statement but saw only this.
http://img214.imageshack.us/img214/3488/example2ky2.jpg[/IMG]

as you can see all I did was add the RTAB script and everything else I wanted with that system in with it the "Advanced Targeting " Demo . It's going to be a slow process but progress will be made. My new question is what is the next step from here?

 

[DerVVulfman]

RTAB does not use the value of @active_battler all that much, let alone the combination of @active_battler.current_action. Closest match... could be @active_actor.current_action, but don't quote me.

The thing is... values/variables with the @ prefix are reused throughout a class and if multiple battlers use the same variable (@active_battler)... yeeeaaahhh... Then you'd get the battlers all doing the same thing by accident.

You need to find the currently working battler which would use the code:
battler.current_action which would mean finding a way to identify that single battler in action.

Then again, maybe @active_actor.current_action ... may work...