v3.0.0 release (#19)

* v3.0.0 release candidate

* Update README.md

* Update README.md

* fix unique multipickup

Author: ChapelR

dist/simple-inventory.css

@@ -106,7 +106,7 @@ Both of the above would remove 10 items with the ID `"wood"` and 5 items with th
 > [!TIP]
 > If the inventory doesn't contain an item it's asked to drop, nothing happens. No errors will be thrown, and the items that are present in the command, if any, will be removed as normal. Please be careful as this may hide some bugs.
 
-You can also remove all of the items in one inventory from another inventory by <em>**un**merging</em> the latter drom the former. Like merging, unmerging does not affect the giving inventory, if you want to remove the items from one inventory and add them to another, see [transfers](#transfers) below.
+You can also remove all of the items in one inventory from another inventory by <em>**un**merging</em> the latter from the former. Like merging, unmerging does not affect the giving inventory, if you want to remove the items from one inventory and add them to another, see [transfers](#transfers) below.
 
 ```
 <<newinv _stolenItems>>
@@ -282,7 +282,15 @@ Want to add an option to drop all items? And how about a way to inspect the item
 
 ![Inventory with everything](media/inv-fully-loaded.jpg)
 
-You may also provide the flag`stack` to allow players to drop/transfer entire stacks of items all at once:
+There is also a built-in search/filter UI element you can add with the `filter` flag. This will allow players to type to filter the inventory.
+
+```
+<<inv $backpack use drop inspect all filter>>
+```
+
+![Inventory with everything](media/filter.jpg)
+
+You may also provide the flag `stack` to allow players to drop/transfer entire stacks of items all at once:
 
 ```
 <<inv $backpack use drop inspect stack all>> 
@@ -317,23 +325,23 @@ You can change the default strings used by the built-in interfaces, for example,
 
 The strings that can be changed in the special passage are as follows:
 
-- `inspect`: **not used** in the default interface, since the user clicks on the names of items to see their descriptions, however, a link for inspecting items may be needed in the future or by users. Default: `"Inspect"`
-- `drop`: appears as link text when users can drop items in the interface. Default: `"Drop"`
-- `take`: can appear as link text when users can transfer items in the interface. Default: `"Take"`
-- `give`: can appear as link text when users can transfer items in the interface. Default: `"Give"`
-- `use`: link text for the action allowing consumables to be used. Default: `"Use"`
-- `stack`: the text used to refer to an item stack when dropping or transferring whole stacks in the default interface. Default: `"stack"`
-- `stackPre`: string appears before the item stack counts. Default: `"&nbsp;&times;&nbsp;"` (that is,&nbsp;&times;&nbsp;)
-- `stackPost`: string appears after the item stack counts. Default: `"&nbsp;"`
-- `empty`: this string appears when an empty inventory is displayed. In the API, this is handled by a separate property, `Inventory.emptyMessage`, passing this value to `Inventory.strings` won't have any effect! Default: `"&hellip;"`
+- `inspect`: **not used** in the default interface, since the user clicks on the names of items to see their descriptions, however, a link for inspecting items may be needed in the future or by users. Default: `Inspect`
+- `drop`: appears as link text when users can drop items in the interface. Default: `Drop`
+- `take`: can appear as link text when users can transfer items in the interface. Default: `Take`
+- `give`: can appear as link text when users can transfer items in the interface. Default: `Give`
+- `use`: link text for the action allowing consumables to be used. Default: `Use`
+- `stack`: the text used to refer to an item stack when dropping or transferring whole stacks in the default interface. Default: `stack`
+- `stackPre`: string appears before the item stack counts. Default: `&nbsp;&times;&nbsp;` (that is,&nbsp;&times;&nbsp;)
+- `stackPost`: string appears after the item stack counts. Default: `&nbsp;`
+- `empty`: this string appears when an empty inventory is displayed. In the API, this is handled by a separate property, `Inventory.emptyMessage`, passing this value to `Inventory.strings` won't have any effect! Default: `&hellip;`
 
 For example, an `inventory.strings` special passage may look like this:
 
 ```
 :: inventory.strings
-use: "Activate"
-take: "Swipe"
-empty: "The inventory is empty!"
+use: Activate
+take: Swipe
+empty: The inventory is empty!
 ```
 
 To do the same thing with the API, the JavaScript code would look like this:

dist/simple-inventory.js

@@ -205,6 +205,7 @@ These macros can be used to show the default user-interface components for manag
   - `use` allows the player to "use" an item if it is considered a consumable, and using it will expend one of the items and cause it's use code, if any, to be run. Refer to the `<<item>>` macro below.
   - `stack` shows a "Drop/Give/Take stack" option at the end of each item listing with more than 1 item in it. 
   - `all` shows a "Drop/Give/Take all" option at the bottom of the inventory list. 
+  - `filter` shows filter/search box for players to filter their inventories with. 
 
 #### Examples
 
@@ -226,6 +227,12 @@ These macros can be used to show the default user-interface components for manag
 
 ![Inventory with everything](media/inv-fully-loaded.jpg)
 
+```
+<<inv $backpack use drop inspect all filter>>
+```
+
+![Inventory with filter box](media/filter.jpg)
+
 ```
 <<inv $backpack use drop inspect stack all>>
 ```
@@ -314,8 +321,9 @@ For example:
 
 ```
 :: inventory.strings
-use: "Activate"
-take: "Swipe"
+use: Activate
+take: Swipe
+drop: Discard
 ```
 
 The strings you can change are:

docs/Guide.md

@@ -1,9 +1,9 @@
 # Simple Inventory 3
 
-> [!NOTE]
-> Simple Inventory v3 is in beta right now. It should work, but there may be bugs and rough edges. Please [report any issues](https://github.com/ChapelR/simple-inventory/issues/new) you encounter!
+ The new simple inventory system. No longer a part of [my macro collection](https://macros.twinelab.net/), it's now its own thing. If you need the old version, grab [an older release (v2.10.0 or lower) of my custom macro collection](https://github.com/ChapelR/custom-macros-for-sugarcube-2/releases). If you find any bugs or have any issues, please [let me know](https://github.com/ChapelR/simple-inventory/issues/new)!
 
- The new version of my simple inventory system. No longer a part of [my macro collection](https://macros.twinelab.net/), it's now its own thing. If you need the old version, grab [an older release (v2.10.0 or lower) of my custom macro collection](https://github.com/ChapelR/custom-macros-for-sugarcube-2/releases).
+ > [!TIP]
+ > New to Simple Inventory? Start with the [guide](Guide.md) and [recipes](Recipes.md) to see what the system is capable of!
 
 - [Downloads](https://github.com/ChapelR/simple-inventory/releases)
 - [Installation](#getting-started)
@@ -20,19 +20,17 @@
 - [Demo](demo.html ":ignore")
 - [Source Code](https://github.com/ChapelR/simple-inventory/)
 
-Version 3 includes most of the features and functionality of v2, and adds:
-
-- Consumables. Items can be associated with SugarCube code (sort of like a widget) or a callback function that can be executed when the item is "used."
-- Item descriptions (as dialogs).
-- Item names. You can provide items with both names and IDs, using the ID in code while the name will be used for displaying it in the game.
-- Item and inventory tags. You can add tags to items and inventories as metadata.
-- Item stacking. Duplicate items in an inventory can now *stack* meaning they'll take up one visual "slot" in the inventory, but will have a counter showing how many are present.
-- More robust built-in UI options and components.
-- A cleaned up, mostly simplified API and code structure.
-
-Most new features are optional; you don't have to define items, for example. With the exception of stacking, it's possible to use this inventory in almost exactly the same way as v2.
-
-This new simple inventory is totally incompatible with previous versions. Updating will require rewrites, so you may want to stick with v2 in ongoing projects.
+Features:  
+- Support for an arbitrary number of inventories, so they can be used as player inventories, chests, rooms, NPC inventories, etc.  
+- Simple interfaces for complex operations, like inventory transfers, merges, and comparisons.  
+- Items can optionally be predefined, but you may also just use bare strings for ultimate simplicity.  
+- Premade logic for unique and un-tradeable items.  
+- Built-in support for "consumables" like potions, which can be paired with a code "handler" for easy item creation.  
+- Duplicate items in a given inventory "stack" automatically.  
+- A suite of customizable UI components for displaying and allowing users to manage inventories easily.  
+- Text search/filter system built-in as an optional UI component.
+
+Most features are optional; you don't have to define items, for example. With the exception of stacking, it's possible to use this inventory in almost exactly the same way as v2. Note that this new simple inventory is totally incompatible with previous versions. Updating will require code rewrites, so you may want to stick with v2 in ongoing projects.
 
 ## Getting Started