What's up, RMers?

[Taylor]

I've made an overdrive/limit-break-esque system for my game from scratch, with it being surprisingly unpainful. In the least, it only took somewhere about two-three days, and any frustrations weren't really with trying to do something so much as me being a dumb.

My only concern now is the power of the skills themselves. Since they're supposed to be combos between characters, they should use the combined power of those characters... and I'm not sure how to do that. Would creating a fake Actor instance to serve as the caster of the skill work, maybe?

[BeJeremiah]

If both characters are in the party, you could make party skills like those seen in Chrono Cross...oh, im gonna go look at that game. Have not seem much reproduced from that lately. But yea, maybe use the party class as a base for stats behind the skill. im not sure which engine you use so I cant say for certain what option would be best.

[Taylor]

I'm using VXAce, and my problem is, is that as far as I'm aware, VXAce will refer to the Battler using the skill - so I need someone to have those stats, I can't just define them as it is. Hence, creating a fake Actor/Battler that'll get those stats added up, and be referred to in damage calculation.

Of course, then the engine might have a spat about other functions when trying to deal with an actor I just had it create on the fly.

[MechanicalPen]

I think the best way to do a combo would be to edit the damage formula of the skill to take into account the multiple users? If you don't know how to do that, maybe open a thread about it and we can get it worked out.

[Taylor]

Theory One: Make "@subject" (the caster/active battler) an array, and all subsequent references to @subject loop through the contents over a single battler.

PHP Code:

       @subject = []
        for a in real_item.unity_conditions[:actors]
          @subject.push($game_actors[a])
        end
        @subject.each {|a| 
          a.make_actions; a.current_action.set_skill(real_item.id)
        } 


Problem with that I discover though, is that it could run into trouble down the line - I could end up with every characters in the combo set trying to use the skill, each one after another! Not quite what I want. (I'm not saying this does happen, but it probably would if I wasn't careful.)

Theory Two: Only have reference to an array of battlers in the conditions they're expected.

PHP Code:

       @unity_subjects = []
        for a in real_item.unity_conditions[:actors]
          @unity_subjects.push($game_actors[a])
        end
        @subject.current_action.set_skill(real_item.id) 


With this, I then wrapped animated battler processes for casting animations in code to play casting animations from an array of casters. It would either only contain @subject, or the users of the combo in @unity_subjects.

The first theory was my initial plan. While it would be adaptable for other systems down the line or other projects, it could easily turn my code into a convoluted mess if I got lost or screwed up, and I didn't want to risk that. The second theory sort of follows MP's suggestion in that it tries to focus on specific elements to edit.

The first also assumed I would later edit a lot more code, but this sounded a bad idea, and as it turns out... unnecessary. Ace lets me write my own formulas per-skill! Why would I make things harder for myself? All I needed was to put something like $game_actors[1].mat+$game_actors[2].mat in as the formula in the database, and it would work.

[Kain Nobel]

I'm back in action! A couple months break from a ten year project doesn't change the fact that I've still got 50 billion things to do lol.

Spent the past five days on miscellaneous stuff; cleaning up old sprites, improving old battle animations, making a custom SE for one of my spells, etc.

A little more ReGaL planning in progress, thinking about battler AI. What I mean by that is giving the developer full control over the logic and actions of enemies (and even computer controlled allies.) It wouldn't be anything too difficult for the user to work with, it'd be just like setting up events and such. Battle entities would even have their own local switches and variables with AI pages dealing with 1.) initial battle setup, 2.) main turn logic, 3.) end of turn logic, 4.) reaction logic and 5.) on death logic, plus whatever else I probably haven't thought of yet.

With that said, I'm off to figure out what tonight's main objective will be. ;)

[Taylor]

I have a bunch of tiles I need for the protagonist's house. Some of them I could probably find and put in, but some I might need to do from scratch, especially if I want a specific feel. (Like 16x16, modernism(?), not too exact tiles, like those obvious CT benches.)

But that sounds daunting, weh.

[MechanicalPen]

Does the Old School Modern pack have what you need? I think it just might. http://cdn.akamai.steamstatic.com/steam/...1391137430

[Taylor]

I might have to take a look at that. I have these modern, futuristic, and RMDS "DLC" packs, but as they're VXAce's natural 32x32 resolution, I'd probably have to edit them a bunch. I also may have avoided the set for its FF4-5 scale, whereas I'm working at a scale more like FF6 or Romancing Saga 3... or Chrono Trigger. Taller characters, objects, all that.

EDIT: Actually wait, are those Old School Modern tiles 2x 16x16 tiles after all? It's annoying when the DLC site resizes the screenshots because it distorts the images, making it hard to tell what you'll actually be getting.

I bet the DLC has been updated since I downloaded them too, but I don't think you can get free upgrades unless done through Steam.

On a related note this set looks incredibly nice, especially to see the RM2k3 characters in a detailed style.

[MechanicalPen]

Ohhh that looks nice.

What's up with me is I've been dreaming up mechanics for a game I'll probably never make. It is still nice to explore how these things would work.

EDIT: I just checked, and the old school modern stuff is in fact x2 scaled. So you can just cut it down in your favorite image editor and use it for your whatevers.