Is there an option to remove portraits upon the battler's death?
That will be the default behaivor, even. Going to change it in the next update (likely this evening or tomorrow morning)
Dear Ellye,
I am very glad to see ATB plugin come so fast after launch of MV.
I just want to give you some suggestion or request:
- Can you add option for ATB Type? AFAIK there is three types of ATB: 1. Active (ATB always run), 2. Wait (ATB will stop when player choosing item or skill), 3. Passive (ATB always stop when one of actors ATB gauge is full);
- Can you add a way to escape during battle?
- Can you add option for not moving window player status to the center everytime ATB is full? Personally I find this behavior is a little bit annoying.
Thank you very much for your effort.
Regards,
Ryan
1 and 2. are planned
3. I can take a look at that.
Any idea when will release Cast Skill support? It is mainly what I'm interested in the plugin.
Shouldn't take long - it's just that today I had to be away form the PC for the whole day (boardgame party, worth it).
My first priority as far as features go is finishing up the turn prediction system, and skills with casting time are right behind it.
Is there a way to show the enemy's TP bar?
If you meant ATB, yes, it's something I plan to implement later on after the core features are done.
Thanks all for the feedback!
Update:
For now, I'm publishing the changes that allow for ATB formulas to be setup in the [Note] field (plus some other new goodies). Those will be needed for the CTB prediction, and they also avoid many possible pitfalls of using the Formula field.
Do check help, because they work slightly different. Or, to quote the Help text here:
Code:/*: * USING THE [NOTE] FIELD TO SETUP SKILLS THAT INTERACT WITH ATB: * In each Skill or Combat Usable Item, you can set up [NOTE]s that interact with the ATB system. * There's the following notes: * <self_atb:FORMULA> * <target_atb:FORMULA> * * It's important to note that those need to be ARITHMETICAL FORMULAS, not commands. * The following examples are valid: * <self_atb:25000> #This would make a quick skill, as your next turn will come faster. * <self_atb:-25000> #This one would delay your next turn * <self_atb:50*a.agi - 20*b.agi> #This would give the user some ATB based on the difference of AGI between him and the target * <target_atb:25000> #This would GIVE the target some atb, making his turn come quicker. * <target_atb:-10000> #This would DELAY the target next turn * <target_atb:-50*(3*a.mat - b.mdf)> #This would DELAY the target next turn based on the difference between the attacker Magic Attack and the target Magic Defense * * So: * It needs to be a formula that results in a NUMBER, not a command. Do not use "a.atb+=5000;" or similar assignments. * You do can use methods like Math.random or Math.Max; you do can use if-else conditions; just make sure that the end result will be a number and that you aren't executing any action except calculating that number. * POSITIVE numbers will always GIVE ATB, no matter if for caster or target. * NEGATIVE numbers will always REMOVE ATB, no matter if for caster or target. * Important note about SKILL WITH MULTIPLE TARGET: The "self_atb" parameter applies ONCE PER TARGET HIT, so balance accordingly (this was also the case with the Formula field). */
