Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Huh, I wonder what in that plugin specifically was so incompatible with Dualtechs to cause all that. I would guess we modify some function or another in different ways - likely candidates are selectNextCommand or removeCurrentAction.

I went through the Weapon Unleash plugin and it does have 2 lines pertaining to selectNextCommand.  They appear when replacing the skill ID used for Attack and Guard in Scene Battle. Hope this clears things up?

(2 edits)

Wow, I actually found Weapon Unleash in a download from ages ago, and the issue is not even close to anything I expected. In essence, it's a... bug? maybe? in Weapon Unleash that may or may not affect things normally (still piecing this mess together), and to be honest, I'm a little surprised it works when Dualtechs ISN'T installed. 

I'm still piecing things together, but the Dualtech is being resolved when it isn't supposed to be. Actually, I'm not even sure it's necessarily Weapon Unleash that has it wrong, but something isn't communicating correctly with other things.

EDIT: I'm understanding a little better what's going on here, and... I'm not actually sure it's a bug in Weapon Unleash OR Dualtechs individually, but it's certainly a weird interaction when both are together.

All right, I fixed compatibility. It might not affect your project any longer, but someone else might want to use the plugins together in the future, right?

Yes, that's true. I did a test and it works perfectly in a new project. My old project is still acting weird, so there might be other compatibility issues (or maybe just plugin order) that needs to be sorted out.