MZ - Cae_Tweaks - lots of little features

You are, unsurprisingly, correct. A longer sound effect plays correctly so maybe the one of first animation is just being drowned.

Is the lettering system based on:

D - Design
M - Mechanics
Q - Quality of Life


???

Close! My initial idea was:

• Mechanics - changes to player-facing mechanics.
• Quality of Life - mostly just changes to in-game UI/UX.
• Developer Tools - to make doing technically-already-doable (?) things easier.

There's been an increasing amount of overlap/drift, though: by now it's largely arbitrary. :kaoslp:

There's a lot here to learn from.
Some times i like just checking out what others make in order to learn more.

It's been a while since the last update! Just dropped v17 with some fixes and stuff:

• M08: the Block State check (TP > 0) now refers to .tp rather than ._tp.
• M28: added 3 plugin params:
  • "Minimum Empty Slot" - makes the empty slot (e.g. for new game) prefer lower slot IDs, rather than starting the search after the first occupied slot.
  • "Custom Save Path" - customise the local save folder path.
  • "Custom Save Subpath" - optionally add a subfolder named by game ID.
• M33: now only clamps the final strictness value to min 0, max 100. So <ai strictness: 200> and <ai strictness: 50> would yield 100 strictness (previously 50).
• M35: added plugin command to remove a party command by its switch ID.
• Q05: added "Portrait Opacity" plugin param.
• Q29: enabled new v1.9.0 feature for movie selection.
• D02: rewrote line raster algorithm from scratch, using the basic division algorithm. Raster is now independent of trace direction (e.g. left/right) and supports corners. Added 3 plugin params:
  • "Skip LoS at Target?" - sight checks always succeed on the target tile. The "JS: Is LoS Blocked?" plugin param has also had its default value changed.
  • "Check Corners" - perform sight checks for corners through which the LoS passes.
  • "Perfect Corners" - determines which corners are selected (if any) when the LoS perfectly passes through the corner of a tile without clipping through tiles on either side.
• D20: fixed reinforcements not acting! Also fixed an out-of-bounds error for certain setups.
• D24: enabled new v1.9.0 feature for map ID selection.

Added:

• Q56: destination sprite customisation. Normally this is just a white square indicating the player's touch-to-move destination. This feature lets you use a picture, specify the blend mode, and/or customise its animation (scale, rotation, opacity, hue, tone).

this is a amazing work, I try most of feature and they work really well

I just realised M28 has a problem with its new Custom Save Path parameter: it doesn't read correctly, always using M28_saveDir instead of whatever you input. I'll fix it for v18 (whenever that gets released), or you can patch it early if you like by editing e.g. line 9673, e.g.
[Edit: v18 has been released with a fix for this.]

I am using quite a few of your cae_tweaks features. I really like this plug-in because they mostly work independently and behind the scenes rather than changing the whole visual display. I have a player that I want to be unable to cause any type of damage in battles, including damage producing items. There is an item, Lightning Bolt, that is usable in battle, but I don't want her to be able to use it. I can use the Visustella plugin to achieve this, but it makes the item window just so busy and complicated and, for my target group, I just want to keep it simple. I used your M27 ("item" skill type) and it works great but not perfect. My pacifist healer is unable to select the Lightning Bolts in battle, but neither can she select any other items. Is there a way to designate just one specific item unusable in battle for one specific actor? If not, I can quite happily live with what cae_tweaks can do.

I'd like to also say that I am so appreciative of not only this plug-in, but also all your help in the forum with engine/javascript questions. I always read your responses, no matter the subject matter, because I know I'll learn something valuable.

@Lady_JJ - aw thanks! You're welcome~

M27 isn't designed for per-item requirements, but I have a different plugin, Cae_OnUseEffects, that can do that. In case you're interested, it can be found over here:
Amongst other things, it offers this Item/Skill notetag:

---

<enable condition: SCRIPT> e.g. <enable condition: return 100 <= subject.mat;> - Replace SCRIPT with valid JavaScript. If this returns falsy, the skill/item will be disabled in-game. Local vars: item, subject (a.k.a. user).

---

So, with that, you could try tagging the Lighting Bolt item like this (untested):

---

<enable condition: return !user.isActor() || user.actorId() !== 23;>

---

I.e. "this item is enabled iff the subject is either not an actor, or not actor ID 23". Replace 23 with the ID of your healer. (I've included the "not an actor" check just to be super safe, because actorId only exists for actors.)

:kaojoy: And, it, of course, works perfectly! Thank you so much!

Updated to v18!

• M05: now correctly uses custom tag name, if defined. I also made its shouldAddNextState function externally moddable by defining it on the feature namespace, just in case.
• M26: redesigned how it fetches the speed modifier value. It should be more compatible with other stuff now, including (for example) new feature D29. (It previously patched realMoveSpeed for each character type, now it simply defines different move speed modifier functions for each type.)
• M28: now reads Custom Save Path plugin parameter correctly.
• Q03: when specifying which params to show on the status scene, you can now use the identifier, e.g. "mhp" for Max HP. This is mostly to help interface with e.g. new feature M39. (Param IDs still work too.) Buff threshold "neutral" values now support JS. Neutral values and "lower is better" flags can now be customised for all param types - note that this means those updating from a previous version will need to re-enter any non-default values for that stuff.
• Q32: hue updates now sync to map update rate and do not reset on scene change.
• Q33: added plugin commands to show/clear auto-messages, and a plugin parameter to enable/disable automatic conversion of parallel Show Text. Also now supports showing auto-messages in battle.
• Q41: setting the Option Default plugin parameter to false now works as intended.
• Q43: out-of-bounds values are now handled a tiny bit more efficiently.
• Q53: blank Navigation Key no longer crashes the game.
• Q55: fixed a memory leak. Yay!
• Q56: fixed angle units used for dynamic rotation. Before it was using radians for the initial angle and degrees for rotation...now it uses degrees for both.
• D20: added "Advantage?" command argument. So your reinforcements can arrive and immediately act out.
• D21: added "Safe Load" plugin parameter & code for it. It's enabled by default: it basically just sends you to a "loading" scene to avoid the error-prone mess of clearing and replacing map data while on the map.
• D26: added "Mode" plugin parameter, to change when the custom defaults are applied. Don't change this unless it's not working correctly as-is.

Added:

• M39: allows defining custom formula overrides for core parameters, and new parameters each based on a custom formula. Mostly intended for display in the status menu via feature Q03.
• D28: notetag for Enemies: <replace: EVAL>. Largely based on what I posted here. Replaces tagged enemies immediately before battle starts, based on the result of the eval:
  • Positive: replace with enemy ID.
  • Zero: replace with nothing, i.e. remove.
  • Negative: replace with all members of that troop.
  • Not a number, e.g. null: do nothing.
• D29: "glue" characters together so that they move and collide as a single unit. Gluing is directional: if A is glued to B, then B is the "parent" and controls all movement. I was thinking of block-pushing puzzles, but might also be helpful for land vehicles, large enemies, overlays, etc.

OK, rushed out a v19 update. Just some bits & pieces:

• M07: added "Damage Formula" & "Variance Bias" params. The first just scales the formula result by the luck effect rate. The second (currently) shifts/scales the range of variance based on luck, e.g. at high luck (relative to your target), negative formula variance becomes impossible...and vice versa.
• M35: added "Options Command" & "Quit Command" params - exactly what it says on the tin, in-battle access to options/quit scenes without breaking battle flow.
• M36: added support for a "Transfer" gameover option. You can change the transfer target mid-playthrough using a plugin command.
• M38: patched behaviour of nested transforms. E.g. if transform B is applied on top of transform A, then transform A is removed, removing transform B should then correctly revert you to your original form.
• Q41: added support for multiple FoV angles. The FoV angle parameter is now a list: the first one (FoV ID 1) is used for the player's "natural" FoV. Previously the <light> tag accepted either 0 or 1, to specify a point or FoV source; now 0 is a point source, and other numbers indicate the respective FoV angle. With this update there is also support for inverted FoVs (light/dark swapped within radius): just specify a negative FoV in a <light> tag.
• Q55: map state overlay redesigned to catch edge cases.
• D29: rewrote some code for readability/efficiency.

No new features~

(This has been mostly ready for months, I just hadn't bothered testing the lighting stuff. :kaoslp:)