Compatibility (between two specific battle systems.)

[Magus]

Okay, I'm pouring my time into a unique game, in which, I want to show everyone how much I improved and all.

However; I want it to use two battle systems.  1. Blizz-abs  2. Gubid's Tactical Battle system. ( http://www.creationasylum.net/forum/index.php?showtopic=20353)
Can anyone make it so that their more compatible with each other. As of now, they DO coexist, which is freaking awesome! HOWEVER, every once in a while, I'd get in error.

I really am sorry for requesting something this annoying; and thanks|Gratitude in advance:  I really want to release a new type of game here on this website..

[Magus]

Sorry for double post.

The main reasons to use these systems together is to provide a new type of game play which uses a dual battle system rather than just one alone.
This will keep the audience on their toes: And they'll particularly never know what to expect next. They won't be able to predict any battles, bosses, etc.

[Subsonic_Noise]

There is an edit feature, and it bumps your thread. Use it.

Also, I'm not sure if this is possible. Battle systems modify the engine rsther badly, and when it's about two on-map battle systems, it could get difficult. Then again, a good scripter could probably do it.. maybe you'd need to pay one or this though since it's a very specific request.

[winkio]

I'd say that you should think about this more. 

Consider this scenario:  I really like both basketball and tennis.  I want to make a game that combines both of them.  I want to splice a basketball and a tennis ball together, splice a basketball court and a tennis court together, and splice the scoring systems together.  Is this a good idea?

The answer is no.  It would be far easier to make and ABS using code from the tactical system, or a tactical system using code from the ABS, than to splice the two together.  Or, to go back to the sports analogy, it would be much easier to play tennis on a tennis court with your hands and a basketball, or basketball on a basketball court with a tennis ball and tennis rackets. 

This is all getting really abstract, but the point is, don't be a mad scientist and create a monster.  Think out your concepts and how to combine them, and then build a unified system.

[Magus]

But the battles are going to be used at two different times.  Like for instance, one battle could wind up as an ABS battle whereas a different scenario would call for a tactic battle.  Like for instance:

The main character is making his way to the boss. Instead of a long-drawn out tactic fight,  he can kill the enemies instantly and move onto the next map.

When he gets to the boss, let's say, King Death(not in my game), The king sends out a group of elite soldiers to attack. That's when a tactic battle starts.


After you defeat the soldiers, the king is obviously angry and then of course i can easily teleport the player to a duplicate map and began an ABS fight where the hero fights one on one with the king.


In other words, the systems will coexist, but not be used simultaneously.


Edit:  Unifying as One Massive system is quite frankly unnecessary -- but alternating from one system to the other: using them in a way where it almost seems as if they really are unified, but in the actually case: One map may use blizz abs while the other map uses Tactics.

[winkio]

Yeah, see, you are missing the point.  Scripts don't apply map by map, they apply to the whole game, even when they aren't "active".  So unless they are unified, they are just going to fight and break each other.

[Magus]

The owner did say that his script was made in separate code so that it could work with other battle systems. (He probably referred to the default system)
but I guess with Blizz-abs, that's where incompatibility lies.

[winkio]

Okay, let's say we are building a house.  We want some floors to be earthquake proof, and some floors to be hurricane proof.  The problem is that to make any part of a building earthquake proof, the foundation has to be built a certain way.  And to make any part of a building hurricane proof, the foundation has to be built a certain different way.  The foundation can't be build both ways, because then it would not be stable. 

Even though all we want is to have each room be it's own thing, the foundation can't handle both modifications.

[Magus]

Yeah, I knew what you meant with other place: The two systems breaking each other apart. Which is why I'm in an experimentation state. I still favor the idea of being able to turn blizz abs on/off in game using a call script.  (I searched the manual, but you can't)

The tactics system does have a call script to turn it off something like:  disable_tbs  enable_tbs 
(imagine  disable_blizz Enable_blizz )

[winkio]

No, you still don't get it.  You can't enable/disable code.  I can guarantee you that both scripts make changes to the Game_Map class.  These are not things that you can turn on/off, they are hardcoded into the scripts.  So if both scripts are trying to modify the same class, one of them will override the other, and that will cause errors.

[Magus]

http://www.creationasylum.net/forum/index.php?showtopic=20353  

Oh  It really did "appear" that you were able to enable/disable that abs  with the call script , but meh.   :/  I can't argue, you're the experienced scripter. :>

It's cool that his battle system works with the default system. :/ But no one likes the default system XD

[winkio]

You can enable/disable the active part of the system, but you can't just magically pretend like it was never there.

[Magus]

yeah,  you're right about that.