Currently the userscript takes it from the package.json, but the semantic-release does the publishing without updating it

nonCombatStats are the skilling bonuses.
combatStats are the combat bonuses.

So people know where to open issues and not bother in the Discord

Currently only incoming messages are appended to the chat, but we could add the history as well.

It seems redundant to have to write a getter in every plugin.

• Add a getter for all features of game and _game itself
• Rewrite all old plugins to use the new getters

As a user I may want to change the size of the icons in the icon gutter. It would be nice if there was a config option I could change on the fly to accomplish this.

export enum IconSize {
  Regular = "",
  Large = "text-lg",
  ExtraLarge = "text-xl"
}

Depends on #33

Add a plugin with a tab where users can input what item they want to enhance with which settings. Calculate the xp and items gained

Bonus points if you autoload their max resources, skills and such from the client.

Bonus bonus points, loop over some common settings to calculate the max xp gain

We should add Histoire to the project to allow fast development and iteration of UI components. This will help us build a nice design system for MooLite.

Create a new plugin and when the player consumables updates to empty, throw a notification.

See ChatNotifierPlugin for inspiration

Depends on #27

Add an event for food and drink separately.

Make sure to add a notify option turned off when called from client info.

What part of the game does your Plugin relate to?
All parts of the game

What should your feature do?
Open up one of the features on the sidebar

What kind of input and output does your feature need?
Ctrl+shift+i to open up the item finder for example, and simple shortcuts for the rest

gameVersion and versionTimeStamp can both be added as an attribute of Game

Will be useful for the combat simulator if we ever port it

Vitest will help us build more robust plugins and ensure they continue to work as we iterate on the platform.

As a developer I would like to control the width of my plugins UI.

Currently, we set MooLite to a fixed width when there is an active plugin tab. Instead, the width should be decided within each plugin. The current width could be set as the default, but a developer should be able to override the value. This could be in the form of a developer defined class string or a MooLite defined enum.

ClientInfo.enhancementLevelSuccessRateTable and ClientInfo.enhancementLevelTotalBonusMultiplierTable.

Implement helper methods to calculate chance of success, xp gain and resource cost per level

Milky Design System

Hey hey! It's time to fall in line my fellow plugin developers! We'll be using Histoire to build a brand-new design system to use in the project. This will help ensure that our UI is aligned with Milky Way Idle.

Initially we'll cover the components and atoms we already have in the project. Then, we'll take inventory of the components used in all of the plugins and rebuild those as well.

• Create one issue per component.
• Create one issue per plugin update.

Planned Components:

I'll update this list with issue links as they're created.

• #119
• #111
• #112
• #113
• #114
• #115
• #116
• #117
• #118

Describe the bug
When opening MWI in a new tab, the MooLite bar does not appear if you wait too long to switch to that tab. MooLite is likely still running because the empty white space can still appear and Tampermonkey says that it is active. It seems that the script does not correctly run if the game has already been loaded.

To Reproduce
Steps to reproduce the behavior:

1. Open "https://www.milkywayidle.com/game" in a new tab.
2. Switch to tab after it loads.
3. See error.

Expected behavior
Expect to see MooLite bar appear.

Screenshots

Browser
Chrome Version 113.0.5672.64 (Official Build) (64-bit)
Firefox 112.0.2 (64-bit)

Additional context
Other browser extensions do not seem to affect this bug. No other Tampermonkey scripts are installed or active.

https://eslint.org/docs/latest/rules/curly

This breaks HMR and is just an all-around nuisance to work with

What part of the game does your Plugin relate to?
Enhancing

What should your feature do?
Display the chances of getting a +(whatever enhancement level I input), the amount of mats it takes and the xp I get.

What kind of input and output does your feature need?
I will be able to enter what tea I will be using, the level of enhancement I want, and the duration. The plugin should fetch all the bonuses like the global xp buff, enhancer success rate, action speed, etc

Currently every plugin sort of makes their own input elements. It would be nice if these were added as atoms and shared between plugins and their config menus

• Tables
• Checkbox
• TextInput
• TextFieldInput
• Dropdown
• Button

Each plugin can have the following attribute credits

export interface Credits {
  // The original creator of the plugin, this can never change.
  author: string;

  // The current developer of the plugin, changes when the author is no longer interested.
  maintainer: string;

  // Anyone who ever did anything to aid this plugin, add your own name if fix something here.
  contributors: string[]
}

Describe the bug
An empty white space appears next to the plugin utility bar when the browser dimensions are either very wide or very tall (for example, split screening two browser windows). It appears regardless of whether one of the plugin menus is open. It is not always the same size as the menu.

To Reproduce
Steps to reproduce the behavior:

1. Be on 'https://www.milkywayidle.com/game'
2. Snap browser window to half-screen or other weird dimensions.
3. See error

Expected behavior
I didn't expect to see the plugin creating empty space.

Screenshots

Browser
Chrome Version 113.0.5672.64 (Official Build) (64-bit)
Firefox 112.0.2 (64-bit)

Additional context
Other browser extensions do not seem to affect this bug. No other Tampermonkey scripts are installed or active.

Component: Dialog

Feature Request:
The Dialog component is needed to present information or requests to users in a modal-type overlay. It serves as a crucial element for displaying important messages, confirming user actions, or collecting user input.

Reasons for the Component:

• Modal Interaction: Dialogs provide a focused and attention-grabbing interface for displaying critical information or requesting user input without losing context from the underlying content.
• User Feedback and Confirmation: Dialogs allow us to present users with confirmation messages, such as success notifications or error alerts, ensuring that they are aware of important actions and their outcomes.
• User Input Collection: Dialogs facilitate the collection of user input through forms or specific prompts, enabling interaction with complex or multi-step actions.

Variations and Special Options:
The Dialog component should support the following variations and special options:

• Customizable Content: Allow the Dialog to render custom content, including text, images, buttons, forms, or any other desired elements.
• Size Options: Provide options for different dialog sizes to accommodate varying content and design requirements.
• Overlay and Background: Include options to control the visibility and styling of the overlay and background behind the dialog.
• Modal Behavior: Implement the ability to control the modal behavior, such as closing on outside click or pressing the Escape key.

Describe the bug
When i try to copy the equipment ill get the popup: Copied Equipment to Clipboard.
But it is not copied to my clipboard

Describe the bug
The PluginManager element is thinner than expected because it has a class of w-full in its component, but we define the default width in App.vue.

To Reproduce
Steps to reproduce the behavior:

1. Run the MooLite dev env on the develop branch.
2. Observe that the plugin manager has both classes.
3. Observe that the w-full class takes priority.

Expected behavior
I expect the plugin manager to conform to the default width.

Screenshots

Browser
Arc

I'll leave it up to the plugins to handle saving and loading, although they should not crash

I am assuming there are events when community buffs start and end, I haven't been able to capture them yet.

What part of the game does your Plugin relate to?
Related to non-combat actions.

What should your feature do?
When crafting/gathering show the total time left based on amount of actions left.

What kind of input and output does your feature need?
Possibly just a time left counter in the xp tracker or a seperate menu or somewhere around the progress bar on top.

Store all relevant data in the Chat class.

It likely won't ever be used, but hey it gets us closer to completing init_client_info

What part of the game does your Plugin relate to?
Most/All skills

What should your feature do?
A Notification when a community buff is added/expires

What kind of input and output does your feature need?
configuration around which buffs trigger the notification

Currently there are no mechanics to update the game DOM with new information. This would be incredibly useful and take MooLite to another level of QOL.

We could add custom buttons to inspect people with the LeaderboardPlugin, display time left for actions. Lookup items with ItemFinderPlugin, or run simulations with LootSimulator.

I'm not sure what the best way is to reflect the UI?
Each "feature" could store and expose its own ui section with a mapping to the HTML elements? But that can break easily with updates

Describe the bug
MooLite stops reading messages from the server if MWI has to reconnect. This happens on my MacBook if I close the lid and reopen it. MWI does a little Attempting to reconnect... animation and comes back, but, for example, the XP Tracker plugin doesn't update when actions are taken.

To be clear, it's still functioning. It's still keeping track of xp/hr, but it just ramps down the value as it's not reading the messages from the server.

To Reproduce
I only know how to force MWI to attempt to reconnect by closing and opening my laptop. If you know a better way, please leave a comment. These steps are based on my circumstance.
Steps to reproduce the behavior:

1. Be on a laptop.
2. Open MWI with MooLite loaded.
3. Queue up some actions.
4. Open the XP Tracker plugin.
5. Observe that it updates each time an action completes.
6. Close the laptop lid and open it again.
7. Observer that MWI attempts to reconnect.
8. Observe that the XP Tracker plugin is no longer reacting to actions.

Expected behavior
I expect MooSocket to also reconnect in this circumstance.

Browser
Brave

Sometimes it adds dev: true to all devdependencies, and sometimes they are all removed, what up?

Component: Accordion

Feature Request:
The Accordion component is needed to create collapsible sections that allow users to expand or collapse content sections, optimizing space and providing a structured and interactive user interface.

Reasons for the Component:

• Content Organization: Accordion components facilitate the organization of content into collapsible sections, allowing users to focus on relevant information while reducing clutter and improving readability.
• User Control and Interactivity: Accordion sections enable users to expand or collapse specific content areas based on their preferences or the information they need, enhancing overall user control and interaction.
• Space Optimization: By using Accordions, we can optimize space utilization, particularly when dealing with content-heavy interfaces or when there is a need to present information in a hierarchical manner.

Variations and Special Options:
The Accordion component should support the following variations and special options:

• Single or Multiple Panels: Provide options to configure the Accordion to allow the expansion of only one panel at a time or multiple panels simultaneously.
• Customizable Panels: Allow for customization of each panel's content, such as text, images, icons, or any other desired elements.
• Transition Effects: Include options for animation or transition effects when expanding or collapsing the Accordion panels to enhance the user experience.
• Default State: Support the ability to set a default state for the Accordion, either with all panels expanded, all collapsed, or a specific panel expanded by default.
• Keyboard Accessibility: Ensure the Accordion component is fully accessible using keyboard navigation, allowing users to navigate and control the panels using standard keyboard interactions.

Describe the bug
I made a mistake in the UI update. Scrolling of the plugin window should be up to the plugin, not MooLite. It can be handled in the plugin view, and scroll should be disabled for the plugin tab.

To Reproduce
Steps to reproduce the behavior:

1. Create a new plugin with a view.
2. Add enough elements to overflow in the y direction.
3. Observe that you are powerless to prevent this.

Expected behavior
The plugin tab should be a relatively fixed height. The plugin itself can enable overflow in it's own view.

Screenshots
This is causing my whisper manager to overflow when there are many messages in the conversation, for example.

Browser
Brave

• Create it in the appropriate folder
• Naming conventions
• Explain plugin API
• Enable it in main.ts

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

Good luck with your project ✨

Your semantic-release bot 📦🚀

What should your feature do?
When opening a lootbox, it should keep track of the items gained.

What kind of input and output does your feature need?
No input, but it would be nice if we could export the data to csv so people can crowdsource droprates

Should have one for feature request and bug report

Component: Checkbox

Feature Request:
The Checkbox component is needed to provide users with the ability to select or deselect an option from a set of choices. It serves as an important form input element for capturing boolean values or multiple selections.

Reasons for the Component:

• Enhance user experience: Checkboxes provide a clear and familiar interface for users to make selections, improving the overall usability of the application.
• Accessibility: Checkbox components play a crucial role in creating accessible forms, ensuring that users of all abilities can interact with and understand the selection options.
• Consistency: By introducing a standardized Checkbox component, we establish a consistent design pattern across the application, promoting a cohesive and intuitive user interface.

Variations and Special Options:
The Checkbox component should support the following variations and special options:

• Different sizes: Provide options for small, medium, and large Checkbox sizes to accommodate various design requirements.
• Disabled state: Support a disabled state for checkboxes that should not be interactable or selectable.
• Indeterminate state: Allow the Checkbox to be in an indeterminate state, indicating that it represents a partial selection.

Component: Button

Feature Request:
The Button component is needed to provide users with interactive elements that trigger actions or perform specific functions within the application. It serves as a primary element for user interaction and engagement.

Reasons for the Component:

• User Actions and Interactions: Buttons enable users to perform actions, submit forms, navigate through the application, or trigger specific functionality, making them a fundamental element for user interaction.
• Visual Feedback and Call-to-Action: Buttons provide visual feedback when interacted with, giving users a clear indication that an action has been triggered or is in progress. They also serve as call-to-action elements, guiding users towards important actions or next steps.
• Consistent Design Language: Incorporating a standardized Button component ensures a consistent design language and user experience throughout the application, promoting usability and familiarity.

Variations and Special Options:
The Button component should support the following variations and special options:

• Button Types: Include variations such as primary, secondary, outline, text, icon-only, or any other desired styles to accommodate different design needs and emphasize specific actions.
• Sizes: Provide options for different button sizes, allowing flexibility in visual hierarchy and accommodating various content or design requirements.
• Disabled State: Support a disabled state for buttons that should not be interactable, indicating that the associated action is currently unavailable or not applicable.
• Loading State: Include an option to display a loading indicator within the button to provide feedback when an action is in progress or requires additional time.
• Customization: Allow for customization of button styles, such as color, border, typography, and hover/focus effects, to align with the overall design system or specific branding requirements.

Whenever community buffs are updated we get the following message. Reflect this game state so later we can factor in the boost into xp calculations and create a notifier plugin

    "type": "community_buffs_updated",
    "communityBuffs": [
        {
            "id": 17,
            "hrid": "/community_buff_types/combat_drop_quantity",
            "experience": 157235.5,
            "level": 20,
            "startTime": "2023-05-03T02:19:40.82Z",
            "expireTime": "2023-12-07T11:30:40.82Z",
            "isDone": false
        },
        {
            "id": 15,
            "hrid": "/community_buff_types/enhancing_speed",
            "experience": 156034.5,
            "level": 20,
            "startTime": "2023-04-17T14:57:41.53Z",
            "expireTime": "2023-11-20T08:06:41.53Z",
            "isDone": false
        },
        {
            "id": 12,
            "hrid": "/community_buff_types/experience",
            "experience": 470240,
            "level": 20,
            "startTime": "2023-04-17T07:03:55.087Z",
            "expireTime": "2025-01-29T09:43:55.087Z",
            "isDone": false
        },
        {
            "id": 16,
            "hrid": "/community_buff_types/gathering_quantity",
            "experience": 111564.5,
            "level": 20,
            "startTime": "2023-04-17T14:57:43.869Z",
            "expireTime": "2023-09-19T13:46:43.869Z",
            "isDone": false
        },
        {
            "id": 14,
            "hrid": "/community_buff_types/production_efficiency",
            "experience": 319242.5,
            "level": 20,
            "startTime": "2023-04-17T14:57:39.409Z",
            "expireTime": "2024-07-04T00:22:39.409Z",
            "isDone": false
        }
    ],
    "communityActionTypeBuffsMap": {
        "/action_types/brewing": [
            {
                "uniqueHrid": "/buff_uniques/experience_community_buff",
                "typeHrid": "/buff_types/wisdom",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            },
            {
                "uniqueHrid": "/buff_uniques/production_community_buff",
                "typeHrid": "/buff_types/efficiency",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.197,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            }
        ],
        "/action_types/cheesesmithing": [
            {
                "uniqueHrid": "/buff_uniques/experience_community_buff",
                "typeHrid": "/buff_types/wisdom",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            },
            {
                "uniqueHrid": "/buff_uniques/production_community_buff",
                "typeHrid": "/buff_types/efficiency",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.197,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            }
        ],
        "/action_types/combat": [
            {
                "uniqueHrid": "/buff_uniques/combat_community_buff",
                "typeHrid": "/buff_types/combat_drop_quantity",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            },
            {
                "uniqueHrid": "/buff_uniques/experience_community_buff",
                "typeHrid": "/buff_types/wisdom",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            }
        ],
        "/action_types/cooking": [
            {
                "uniqueHrid": "/buff_uniques/experience_community_buff",
                "typeHrid": "/buff_types/wisdom",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            },
            {
                "uniqueHrid": "/buff_uniques/production_community_buff",
                "typeHrid": "/buff_types/efficiency",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.197,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            }
        ],
        "/action_types/crafting": [
            {
                "uniqueHrid": "/buff_uniques/experience_community_buff",
                "typeHrid": "/buff_types/wisdom",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            },
            {
                "uniqueHrid": "/buff_uniques/production_community_buff",
                "typeHrid": "/buff_types/efficiency",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.197,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            }
        ],
        "/action_types/enhancing": [
            {
                "uniqueHrid": "/buff_uniques/enhancing_community_buff",
                "typeHrid": "/buff_types/action_speed",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            },
            {
                "uniqueHrid": "/buff_uniques/experience_community_buff",
                "typeHrid": "/buff_types/wisdom",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            }
        ],
        "/action_types/foraging": [
            {
                "uniqueHrid": "/buff_uniques/experience_community_buff",
                "typeHrid": "/buff_types/wisdom",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            },
            {
                "uniqueHrid": "/buff_uniques/gathering_community_buff",
                "typeHrid": "/buff_types/gathering",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            }
        ],
        "/action_types/milking": [
            {
                "uniqueHrid": "/buff_uniques/experience_community_buff",
                "typeHrid": "/buff_types/wisdom",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            },
            {
                "uniqueHrid": "/buff_uniques/gathering_community_buff",
                "typeHrid": "/buff_types/gathering",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            }
        ],
        "/action_types/tailoring": [
            {
                "uniqueHrid": "/buff_uniques/experience_community_buff",
                "typeHrid": "/buff_types/wisdom",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            },
            {
                "uniqueHrid": "/buff_uniques/production_community_buff",
                "typeHrid": "/buff_types/efficiency",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.197,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            }
        ],
        "/action_types/woodcutting": [
            {
                "uniqueHrid": "/buff_uniques/experience_community_buff",
                "typeHrid": "/buff_types/wisdom",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            },
            {
                "uniqueHrid": "/buff_uniques/gathering_community_buff",
                "typeHrid": "/buff_types/gathering",
                "ratioBoost": 0,
                "ratioBoostLevelBonus": 0,
                "flatBoost": 0.29500000000000004,
                "flatBoostLevelBonus": 0,
                "startTime": "0001-01-01T00:00:00Z",
                "duration": 0
            }
        ]
    }
}

Component: Input

Feature Request:
The Input component is needed to allow users to enter text or select options from various input fields. It serves as a fundamental element for capturing user input in forms and interactive components.

Reasons for the Component:

• User Input Collection: The Input component provides a means for users to enter textual information, make selections, or interact with form fields, enabling data submission and interaction within the application.
• Input Validation: By incorporating the Input component, we can implement validation and error handling to ensure that users provide valid and expected input.
• Consistency and Reusability: Having a standardized Input component allows us to establish consistent design patterns and behavior across the application, making it easier to maintain and enhance.

Variations and Special Options:
Regarding handling different types of input, there are two possible approaches:

1. Single Component with Options: Create a single Input component that supports various input types and provide options to customize its behavior. This approach allows flexibility and reuse, as the same component can handle different input types (text, number, email, etc.). The options can include:

   • Input type: Specify the type of input (text, number, email, etc.) using a prop or attribute.
   • Validation: Provide options for input validation rules, such as required fields, character limits, and format restrictions.
   • Icon and Label: Include options to display icons or labels based on the input type to enhance usability.

2. Multiple Component Approach: Create separate components for different input types. This approach offers specialized components tailored to each input type, providing more focused functionality and potentially better user experience. For example, having distinct components like TextInput, NumberInput, EmailInput, etc., each with specific features and validation rules.

Consider the specific needs of the project and the trade-offs between flexibility and specialization to determine the preferred approach.

Whatever it may be used for...

In src/MooLite/core/server/messages/, create a new ItemsUpdated class, and create the -Message and -Parser. See ActionsUpdated.ts for an example

In the application of the parser, update the inventory accordingly