What if you try setting it to <1, 2, 3>. Assuming that 2 is for shields, a dual wield type actor should convert that slot into a weapon slot, while other actors would see it as a shield slot. I think it has something to do with a combination of equip requirements, and differing slot types than I was expecting in the dual wield plugin that is causing this issue.
Viewing post in MV - Optimize Equips on Class Change comments
I tried that out and with the slots set to 1, 2, 3 it did convert it to dual wield but it still removed the slot 3 item=(
Is there one way to set it that would play better with your plugins by chance? ie. <1, 1, 3> or <1, 2, 3>
But unfortunately for me the problem isn't any of your plugins it is definitely yanflys.
Hey there I thought I would let you know where I'm at. I have been searching and trying many things and so far nothing. I really thought I had something just now but for some reason it isn't working and I thought I would run it by you to see if you had any thoughts about why it wouldn't be working.
So I add the 2 hander as equippable by a dual wield class. Then I add this to the weapon.
<Custom Equip Requirement Condition>
if (user.isDualWield()) {
condition = false;
} else {
condition = true;
}
</Custom Equip Requirement Condition>
That works to block the 2 hander correctly but then it still removes the item in slot 3. where as if I allowed the dual wield class to equip the 2 hander they would equip it and the slot 3 item stays in place. But I don't want the dual wield to be able to use the 2 hander of course.
I'm getting to where I am kind of at a loss here and have no idea how to come up with a fix after everything I've tried.
Ok so a possible fix donned on me and it worked. And it was pretty simple overall. I removed the equipment restriction on 2 handers and made them their own weapon type. I'm probably lucky I was able to go this route with the complexity of my game and not mess anything up. I am so happy to have this fixed now the system is just one step away from being perfect.=) I just hope now that the sub class optimizing issue is a simple fix.
A huge, huge thanks from me for all your help with all of this bud, I couldn't have done it without you.
So, after looking into the problem, the issue I found causing it means that it probably never worked to begin with. Which is weird, because I was sure I tested that feature when I added it.
Anyways, it's fixed now. You can download v1.71 from the download page and see the underlying cause of the problem here.