Elemental weakness/resistance without popups.

[Rhaeami]

Edited.

I'm using Yanfly Battle Engine, which does pop-ups for strong or weak hits. However, pop-ups are not feasible for my project. I would like to take those messages and push them to the Battle Log instead, but I can't for the life of me figure out how. I can't figure out how Yanfly actually got it to work in the first place, which is why piggybacking off of it as it is would be easiest.

I know that you can push a message to the log with the "add_text()" method, but only from within the right classes(?), so I can't just call that method at the point in the script where the pop-up would be displayed. Likewise, I can push a second message to the log at the point in the script where damage numbers are displayed in said log, but THAT part of the script can't reference the variable for the damage multipliers.

Thank you for any help.

 

[bgillisp]

I use Yanfly's battle engine too, and the damage is in the log already so that part is done. Now if you want it to say resisted or weak as well, that might require editing the code and Yanfly didn't actually add to it, they just used the default code to put the message there. So you'd have to find that and edit it.

The pop-ups can be disabled too, there's code in there somewhere for it. I know as I added an extra popup to the engine myself, it took a little tweaking but it wasn't too bad. But I'm sure you can disable all popups pretty quickly, though you may need to disable it in more than just the Battle Engine as I do recall seeing it in other scripts of Yanfly too.

 

[Rhaeami]

I mean, it's just that the part that puts the damage in the log, and the part that displays a pop-up for the weakness/resistance, seem to be entirely different sections that can't talk to each other easily.

Having slept on it, the best I could come up with is to write in my own custom, insanely long if/then tree right after the damage message to determine expected weakness/resistance by reading the skill ID, target ID, an array containing every "fire" spell in the game, and whether the target has an element (via states). Luckily I found ways to reference these things from there. It'll be a pain but it should, theoretically, work.

 

[Engr. Adiktuzmiko]

You dont need an array of every fire spell just to check if its fire because if you know the skill, you can simply get its element_id value and see if it corresponds to fire. You can also check the target's fire resistance value via getting the approriate trait.

 

[Rhaeami]

You dont need an array of every fire spell just to check if its fire because if you know the skill, you can simply get its element_id value and see if it corresponds to fire. You can also check the target's fire resistance value via getting the approriate trait.

EDIT:
Tried it out, no luck.
undefined method 'element_id' for #<RPG::Skill:0xf61d6a4>
Possibly a problem with the Yanfly engine, I don't know.

For the record, this is within the display_hp_damage method of the Window_BattleLog class, as aliased in Yanfly's Battle Engine. The method is receiving two variables, "item" (which seems to be the skill), and "target". I tested it by way of the following line:
add_text(item.element_id)

 

[Engr. Adiktuzmiko]

Its a wrong call, I just said element_id but I'm actually not sure that its the right one.

Try doing a global search (Ctrl+shift+f) in the script editor for elem and see what things come up. I'm not with my maker right now so I cant pick the right call

 

[Rhaeami]

It was item.damage.element_id. But, as feared, it only shows the system-assigned one, so I'll still need to make a list of the secondary elements. It does save some time, though, so thank you for your help.

 

[Engr. Adiktuzmiko]

So your game uses two elements per skill or something?

 

[Rhaeami]

Some of them, yes. Sorry, I thought I had mentioned that.
Lest you wonder, the secondary element is essentially for slashing/piercing/blunt. It uses one of Victor Sant's scripts to set additional elements in the skill's notetags.

 

[Engr. Adiktuzmiko]

I see. In that case, studying Victor's script should lead you to discover how to quickly determine the second element, or you can simply learn how to read notetags and load them yourself. Doing so, you wont need a list for the second elements too.

 

[Rhaeami]

Honestly, at this point the process has been simplified enough to just use the list method for the rest, since the game is near completion and the applicable skills are set in stone. Again, thanks for the help.

 

[Engr. Adiktuzmiko]

I see. If you're fine with that then that's good, its something you can look at in the future though