Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(2 edits)

Good news!

Dynamic Character in shop window GIF

Sorry that it took so long, life kept happening.
This should work in Ver. 1.7.13 after you confirm the plugin settings after updating.

Edit: I haven’t added a setting to exclude rules from on-window characters (only modifiers), but that’s possible. Let me know if you need it.

Terrific! That is working as described.

An additional feature that would be handy, is if when this sprite is displayed in a shop window and you hover over a piece of equipment that adds a sprite layer, if that layer was previewed on the sprite display.

Somehow I didn’t expect this to have an engine interface, but it turns out that it’s quite reasonable for Window_EquipStatus and only a bit more complex for Window_ShopStatus specifically. The latter fortunately is what BM_ShopCore uses.
(It would actually work already if those windows drew the temporary Actor they use to calculate stat changes, minus Character tags not being taken into account. I’ll fix the latter generally.)

Unlike making the sprites work, this is hopefully not fiendishly complicated, so I’ll give it a go this week.

Done: Ver. 1.8.14: Equipment Previews and paintOpacity support

I underestimated the complexity somewhat 🫠
On the plus side, I fixed more issues along the way.

There may be small differences (only with equipment slot plugins, I think) in how BM MV Shop applies equipment to calculate the stat differences vs. how Dynamic Characters constructs the preview (optimal slot). Players should be unlikely for to notice that, though.

That works perfectly, thank you for all the effort!

There’s currently still a small problem with how the 0/None-Actor condition (first party member) is checked. I’d used the object identity instead of the ID there and that check of course fails for equipment previews.

I’m a bit too swamped right now to do another release just for that, but let me know if you run into it and I’ll prioritise it. (Goes for anyone else too, of course!)

I’ve fixed it locally already, so at the latest it will be part of the next feature release. At which point I’ll hopefully get around to updating the store page here, too.