Every reagent draws its own botanical plate from its own data - Herbarium.js
Every reagent draws its own botanical plate from its own data(Author:Core Systems Asset Factory) - Herbarium.js
https://en.plugin-mz.fungamemake.com/archives/12522
Every reagent in your project mounts as a botanical plate generated from that item's own data. Ten morphological axes and eight humoral tinctures. No image files and no atlas to import.
Plugin desc :
Every reagent in your project mounts as a botanical plate generated from that item's own data. Ten morphological axes and eight humoral tinctures. No image files and no atlas to import.
License :
・Copyright: Retained
・Commercial Use: Allowed
・Modification: Allowed
・Redistribution: Prohibited (This does not apply to works made using the material.)
・Details: See Download Page / In-plugin documentation
============================================================================
Herbarium — generated botanical plates for RPG Maker MZ
============================================================================
Every reagent in your game mounts as a botanical plate DRAWN FROM ITS OWN
DATA: habit, leaf, margin, venation, phyllotaxy, inflorescence, floral form,
root, fruit and surface, pressed in one of eight humoral tinctures. There are
no image files in this product and no atlas. Nothing is supplied by you but
the properties.
----------------------------------------------------------------------------
THE PLATES ARE LEGIBLE, AND THAT IS THE POINT
----------------------------------------------------------------------------
Because the drawing is generated FROM the properties rather than chosen from
a set of pictures, the mapping runs both ways. A player who has studied a few
specimens can read an unfamiliar plate on sight:
the TINCTURE it is pressed in → its humour
which ZONE of the sheet is inked → the part you harvest
the ROOT form → how its potency behaves
the MARGIN of the leaf → how it must be prepared
No display plugin can do this, because a plugin that shows pictures you
supply has no relationship between the picture and the data. That
relationship is the product.
----------------------------------------------------------------------------
STUDY LEVELS — the plate is the record of the player's own scholarship
----------------------------------------------------------------------------
0 UNSEEN the sheet is empty, ruled and numbered but bare
1 FIELD SKETCH habit and one leaf, in pencil line, unlabelled
2 PARTLY STUDIED root system lifted, inflorescence drawn, name written
3 FULLY PRESSED fruit packet, surface detail, full label, seal
A level is never lowered. Recording a specimen you already hold at a higher
level leaves it alone.
----------------------------------------------------------------------------
DECLARING A SPECIMEN — two ways, and you can mix them
----------------------------------------------------------------------------
1. In the Specimens plugin parameter, which is where the properties live.
2. On the item itself, with a notetag, which is enough on its own:
⟨herbarium: moonwort⟩
The key ties the item to a Specimens entry. If no entry exists, one is
derived from the item's own name and its morphology is stable forever
after — see DETERMINISM below.
----------------------------------------------------------------------------
DETERMINISM — a plate never changes once a player has seen it
----------------------------------------------------------------------------
Any axis you leave blank is derived from a seeded hash of the specimen KEY,
never from Math.random. The same key always produces the same plate, in every
playthrough, on every machine, forever. That is a hard requirement rather
than a nicety: a plant that looks different after a reload is a bug the
player can see.
----------------------------------------------------------------------------
COMPATIBILITY
----------------------------------------------------------------------------
This plugin EXTENDS core methods (originals saved and called) and CLOBBERS
none. It is designed to sit ALONGSIDE, and is declared compatible with:
DSI Foraging System / Farming Engine PRO they decide where a plant grows;
this draws what it looks like
CGMZ Encyclopedia keep it — it lists, this draws
Hendrix Crafting Master, CGMZ Crafting keep your crafting system
VisuStella MZ Core Engine load VisuStella first
Load order: HerbariumFlora.js, then Herbarium.js, then HerbariumCabinet.js.
Order is not depended on — every read of the corpus is deferred to
Scene_Boot.prototype.start — but it is the tidy arrangement.
----------------------------------------------------------------------------
PLUGIN COMMANDS
----------------------------------------------------------------------------
Open the Herbarium opens the cabinet scene
Record a specimen mounts or advances a plate
Advance study +1 study level
Is it fully pressed? → a switch
Count pressed plates → a variable
----------------------------------------------------------------------------
SCRIPT CALLS
----------------------------------------------------------------------------
CSAF.Herbarium.record('moonwort', 1);
CSAF.Herbarium.study('moonwort');
CSAF.Herbarium.level('moonwort'); // 0..3
CSAF.Herbarium.pressedCount();
CSAF.Herbarium.keys(); // every declared key
============================================================================
TERMS
============================================================================
One licence per developer. Use in any number of commercial or free projects.
Do not redistribute the source as an asset. Credit is welcome, not required.
============================================================================
A reagent list is text. Herbarium turns it into pictures and the pictures are generated rather than drawn.
Every herb and root and fungus you mark as a specimen mounts as a botanical plate built from that item's own database properties. Ten morphological axes carry the meaning. No image files.
Because a plate comes FROM the properties the mapping runs both ways. A player who has studied a few can read an unfamiliar plate on sight. Unstudied specimens mount as field sketches and finish as the player learns them.
Redistribution is prohibited so no file is attached. This entry is a link and an introduction.
Disclosure. This plugin is AI authored. Code and artwork are AI generated and every storefront listing says so.