Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Quick question - Is there anything to carry over to my project besides the image folder and the plugin files? I copied over the settings verbatim and I can pull up the window to select the tools, but the tools themselves are grayed out and the button is unresponsive. It doesn't break the game, it just doesn't do anything. I scoured the demo to see if there were any kind of initialization events or anything and didn't see anything; just the discoverable plugin command on the chests (Excellent streamlined process, btw). I switched all of the other plugins in my project off to see if it was a conflict, but it behaved the same way, which makes me think I overlooked something that needed to be brought over.

(1 edit)

Hi, if you are talking about copying settings from the demo, the demo is most likely out of date so depending on the settings you copied over you might need to load the parameters up for your tools and let any new defaults load.

If tools are not enabled, make sure you have turned tool access ON via the plugin command Change Tool Access.

That got it, thanks so much!

For what it's worth (and for anybody else curious), this works perfectly within the Phoenix Kage Desu ABS-Z framework.

This works amazingly. I put a link up on the ABS-Z Discord recommending it. The only thing I'd like to see added (if possible) is the possibility to add variables or scripts upon contact instead of just self switches. That would add even more versatility for these items in on-map combat.

Hi, I hadn't thought about on-map combat when making this plugin. I do want to eventually integrate it with [CGMZ] Event Movement to allow things like the arrow / hookshot / boomerang to stun events using CGMZ movement.

Generally I do not add script parameters to my plugins, but I could add a common event on contact / when a tool is used, would that work for your use case?

Actually, that would probably be better in the long-run; variables and CE.