The bp are like boost points from octopath traveler. They are used to get more hits from your basic attack.
But I think it is more confusing than helping for to include them in my post. I´m almost 100% sure it´s not my action sequence, because my character still attacks twice, if I remove it entirely.
Like I said, I can't duplicate the problem in my test project, so it's either a configuration issue on your end (action sequence, passive state granting extra attack times+, etc) or a plugin conflict with something.
From a test play if your project, outside of battle, open the console, and type in $gameParty.actors()[0].isCurrentlyDualWielding() . It should return a true or false (replace the 0 with the party position of the two handing actor, 0 being the first party slot, 1 the second, etc).
Then, go into battle and do the same thing again while in battle. Once again, the result should return a true or false.
In battle, there are many extra checks made, including if the actor has a two handed weapon, a shield, a barehand, etc, so it's normal for the function to return different things inside and outside of battle.
Omg I soooo stupid... I know exactly why you can´t replicate my issue, because there is none. It was all a huge misunderstanding on my part.
Back when I purchased the plugin it was on version 2.69. I set it up and it was perfect for my needs, because a dual wielding char with 2 weapons in his hands was attacking only ONE time. That was exactly the behavior I was looking for. I just wanted one damage pop-up regardless if the char is one-handed, two-handed weapon or has two weapons in his hands.
Time went by and I was working on other parts on my game where the dual wielding character was not important and I think I never tested it again. Now that wrong behavior from version 2.69 is fixed and my brain thinks it´s wrong... there is a bug.. and so on... Completely blind by the fact that this was never an intended feature...
To finalize my post of stupidity I would like to suggest such a feature. An option to not attack twice, even if the character is holding two weapons.
Sorry for the confusion I have caused!
Hey there.
I'll see what I can do about that.
Just to be clear, you want actors to always only attack once, regardless of how many weapons they have?
Because of the splitting up of the mainhand and offhand attack values, currently the singular attack would deal only the damage of the mainhand weapon, not the combined damage of both.
I assume if you're trying not to get the second attacks to happen, you're only really using the plugin for the ability to make two handed equips, forbid wtypes, and such
Hey there.
Sorry I've been more than a little silent the last couple of months. I took some time this morning to see if I could implement what you were asking for into the next update, and good news, I seem to have done it.
Version 2.74 will be uploaded shortly, with a new parameter which essentially disables the combat effects of the plugin, leaving only the following:
The multiplier parameters for dual wield, two handed, and the off hand swing have all been disabled. The notetags for adding params to an item if it's being two-handed or wielded in the offhand, or main hand specifically have also been disabled. All changes to action sequences are reverted.
Skills can no longer be marked as main or offhand only skills. The action sequence addition to make a section repeat if dual wielding has also been disabled.
Normal attacks will only hit once, only showing the main hand weapon sprite (or the offhand one if there isn't anything in the main hand), showing both animations simultaneously, with the offhand animation mirrored on the target, and dealing damage with the atk value of both weapons (as was default in MV).
This should still work with switchable weapons, and monkeygrip, but I haven't tested them. In fact, I haven't done much testing on this at all, so if you notice anything let me know and I'll see about fixing it. The brief testing I did seemed like the basics still worked when the parameter was disabled (which means it shouldn't cause any bugs to everyone else using it), and it seemed to work correctly with it enabled.
~Ramza
