itch.io

The plugin will always stretch them automatically 

The notetags are explained in the respective tabs (Item List Window & Item Detail Window (Image). Basically, when your image file has the name "Potion.png" and is located in img/pictures/items, then the notetags are

<Menu Grid Image: items/Potion>
<Menu Image: items/Potion>

The second one is used for the item inspection window on the right.

A sample game is not planned for this project as making some and keeping it up to date is a lot of additional work.

Open the config file in your game/uicustom/config.json and remove the line that contains the incorrect file. Watch for trailing commas.

As last resort, delete the config file to reset the plugin. The plugin will create a new one automatically when starting the game.

Templates are managed in the plugin manager, and no, they don't need to be downloaded somewhere. Read more: https://aerosys.blog/templates

The error sometimes appears because the "useSnippets?" settings is incorrectly set. Make sure that in the command to generate a dungeon, the setting "useSnippets" is either on or off. This setting is also explained here: https://aerosys.blog/eventing-rpg-maker-mz

I quickly checked the code, and while one could indeed disable some mouse-click actions for windows, it would take some work to disable ALL actions (e.g., mouse wheel should be disabled, too? What about clicking on enemies for target selection?), and it would also raise the risks of interfering with other plugins

Awesome!

Yes, you can open the "rmmz_windows" / "rpg_windows" file in your game directory with a text editor and then browse for all the different window names, and then simply repeat the code snippet that we did for the Window_TitleCommand.

My plugin doesn't support the Title Screen. However, you can easily add a new plugin file (with any name) and paste this:

/*
 *: @target MZ
 */
Window_TitleCommand.prototype.getBackOpacity = function() {
  return 196; // any number from 0 to 255
}

In "Windows General", you will find an "opacity" setting. That should work.

In the Plugin Manager -> MKUIcustomizer Main, you can now assign a different action key to open the toolbox, hope that helps

Glad you like it!

It took me actually a few hours to design the icon picker

Visustella is really proactive here, and their modifications on gauges precede mine. Again, you have 2 plugins that do similar things, so in the end, one plugin (in this case, VS) will "win" over the other. By the way, in this case, it doesn't matter which plugin is loaded "more on the bottom" in the plugin manager.

In my opinion, VS should add more toggles to let the game devs decide whether they want VS to modify the gauges, or not. I'm a bit reluctant to implement a procedure into my plugin that actively force-reverts a feature of another plugin. By the way, that has nothing to do with their code obfuscation (the debugger already exposes how to revert VS functions), but it's more of a psychological question.

Fortunately, VS shows some mercy and lets the game devs actually revert their gauge modifications via some hidden way:

• Go into the Plugin Manager -> VS SkillAndStatesCore -> Skill Cost Types
• Repeat the following for HP, MP, TP:
• Open the setting "JS: draw Gauge", clear everything, and paste:

// Declare Variables
const sprite = this;
// Draw Gauge
sprite.drawGauge()
// Draw Label
sprite.drawLabel()
// Draw Value
sprite.drawValue()

From a technical point of view, this is the cleanest way to drop VS modifications for gauges, and let my plugin take over control again.

Get the latest versions of all my customizer plugins, then open the toolbox in the main menu. In "Gauge Settings", you find a new option "enable further modifications" that gives you more control over gauges.

In the end, both VS and my plugins modify the gauges. I think you understand that I'm a bit reluctant to make my plugin deliberately revert another plugin creator's features.

Yes, you were absolutely right, I somehow missed this.

I just uploaded a new version (1.0.2) - please try again!

Thank you for your report!

Sometimes it's just the "Scale with Minimap?" setting in the Event Template that makes the indicator so tiny it's no longer visible, especially on large world maps. Setting it to "disabled" is usually the best choice.

Verify that the plugin's version is 2.0.1. Sometimes you need to force-refresh the page when downloading my plugin.

Fixed, please try again!

I just scanned my code and it looks like there's an error that happens only in the MV version when a tilesets/event/... has an empty graphics assigned. That truly was difficult to spot.

I fix this as soon as possible! Thanks for reporting!

Have you already tried switching off all other plugins?

My Discord is visible on my blog

https://aerosys.blog/

(Not yet on mobile, use desktop version when visiting this link)

I just uploaded version 3.2.4 to fix this problem. Please try again.

Yeah, this is actually an impression that I receive a lot!

It takes some time to learn, but at some point, it clicks to the devs and then they are super happy with all the options they have!

By the way, to finally reduce this coonfusion, I'm looking for alternative terms for this "layout settings"; I'm thinking about terms like

• Floor arrangement
• Level arrangement
• Map arrangement
• ...

Without too much thinking, what would be a term where you think that sounds intuitive?

I just uploaded a new version 1.0.2 (I was working on that anyway).

With this update, please follow this procedure:

• In the Plugin Manager -> MK_Capture, set "On Capture Action" to "just disappear"
• right below, assign "Actor -> Variable" to a fresh new Variable
• then, assign "Run Common Event" to a new Common Event

This Common Event is now run each time you capture an enemy. The Variable holds their ID. So, inside this Common Event, you can do anything you need, e.g. flipping a Switch "Werewolf captured" to ON.

This sounds like some slight missunderstanding about how Random Maps understands "layouts" and "exits".

Layouts manage how all the maps are connected to each other, see: https://aerosys.blog/room-layouts It does not affect how the small "rooms" on one generated map look like. Instead, 5x5 means that Random Maps will pre-generate 25 maps in total that are connected in a 5x5 grid. Meaning, that there ARE horizontal exits in each map.

To only enable vertical exits, the simplest way is to use a "tower" room layout.

Well, usually I would have asked you to ask the Rosedale dev for support, since I don't own this plugin. Unfortunately, he passed away while ago.

I quickly made this fix: https://downloads.aerosys.blog/plugins/MK_BackgroundSpriteFiltersFix.js (right-click, save as...)

Please tell me whether it's working for you, then I can integrate it to plugin for everyone.

Have you already tried different plugin orders?

The changelog is now available :)

https://aerosys.itch.io/custom-ui/devlog/1523126/version-200

Thanks for your report!

I quickly checked my coding, and it turned out to be a programming error on my part. I will fix it and upload a new version as soon as possible!

Don't worry asking questions, I really appreciate them! They tell me that you guys like my stuff :)

My plugin does not add a "new" layer, that would be too complicated. Instead, I designed it to follow RPG Maker's 6 layers world (i.e. A lower, A upper, B lower, B upper, shadows, region tiles).

I briefly tested this pattern, and it worked for me. I was able to first build the window (line 6), and then the flowers (line 7) on top.

Tell me whether this fits your needs!

Interesting fact:

Making plugins compatible with VS isn't that hard when you have some experience in plugin development in general. Other plugin devs often use the code obfuscation as an excuse when they are not experienced enough or just too lazy.

Hello itch.io team,

I'm playing around with my profile page (https://aerosys.itch.io/), and I think it looks cleaner when I hide all of my products and instead group them by collections.

However, all the price tags are now gone. I think they still should be visible. Otherwise, grouping by collections doesn't really make sense to me.

Best regards

Aero

Can you share a screenshot of the issue?

I played around with it, but it didn't work well, I regret.

I uploaded a new version to improve the handling with Gauges. Please try again!

This will be fixed with the next update, coming the next few days.

Yes, they also work in battles :)

Thanks for sharing the error messages, this is exactly what I need!

I try to fix this problem with the next update. In the meantime, open the toolbox of my plugin, and disable the "blur" filter for the menu background. Not 100% sure, but it may work.

In the next few days, I will publish a new version of my plugins that also improves the interaction with the gauges, so the issue may get resolved then.

You can also link here the hunger bar plugin you are using, so I can check it beforehand.

There are numerous ways to handle it, I kept it open by design to keep it more flexible to the game dev's preferences.

Here are 2 best practices:

Method 1 (requires the hotbar plugin that comes with the sandbox bundle):

• Make 2 Common Events: One to open the menu for "houses", one for "furniture"
• Using eventing, you can anytime replace a Common Event from the hotbar with the one that you want to use

Method 2:

• Inside the Common Event to open the menu, add a Variable OP and store the Map ID into a new Variable "Map ID"
• Next, make a Conditional Branch and check whether the Variable matches the ID of your outside map
• If yes, open the menu for houses, otherwise, for furniture
• You can have as many Conditional Branches as you need

Variable OP: current Map
If Variable current Map == 1
    MK.Sandbox.openMenu('houses')
If Variable current Map == 2
    MK.Sandbox.openMenu('furniture')

At some point in your game (usually inside a Common Event), you open the build menu with a plugin command (MZ)  or a script call (MV) like this:

MK.Sandbox.openBuildMenu('houses')

Now, only blueprints with the category "houses" are shown.

For the other question: Unfortunately, the source map must have the same tileset as the current map. RPG Maker doesn't support mixing tilesets well.