Brea Nonatomic
No reviews yet
A mod provides operator system which can create entities to follow and help you.
Neoforge is a fork of the Minecraft Forge available for versions 1.20.1+ of Minecraft. Many Forge mods are compatible with Neoforge and vice versa.
Community voices
Reviews
Click once to include, again to exclude, again to clear
No reviews yet. Be the first to review this project!
Get it on
Available Platforms
CurseForge
Modrinth
Compatibility
Supported Environments
About
Project Details
For authors
Embed Badge
If you're the author of this project, you can embed a live badge anywhere that supports HTML or Markdown. It updates automatically whenever ratings change.
Use HTML for any page that supports it, or Markdown for README files and Markdown-based descriptions.
Identifiers
Platform IDs
Resources
External Links
About
Description
瓦解核心：非原子单位 | Brea:Nonatomic
Overview
The Nonatomic Lib allows players to deploy Operators in the game. Operators correspond to Operator entities, and players can deploy them to perform various tasks.
This library provides a range of commonly used features for the entire Operator system:
- Operator Customization: Allows the customization of various types of Operators, each with unique attributes and behaviors.
- Operator Information Storage: In addition to customizable attributes, Operators have the capability to store mutable and persistent information.
- Entity and Information Communication: Operator entities and their information reference each other, with appropriate clearing and refreshing to ensure synchronization and proper status.
- Player Behavior Handling: Special player behaviors affect entity states to ensure proper functionality, including login, logout, teleportation, etc.
- Event Listening: The mod listens to game events, such as player login, logout, and the deployment and retrieval of Operators, to enhance flexibility.
Code Framework
Ideally, we can directly bind data to dimensions for unified management—this ensures that Operator data references are maintained when players are offline and avoids crashes due to excessive player data.
The data structure is roughly as follows, from broadest to most specific:
- World Data Storage. We do not provide a standard for this level,
but we offer
the
GroupProviderinterface for convenient handling of player and entity events. - Player Operator Data (
OpeHandler) Stores data on Operators owned by a player and a list of deployed Operators. Since a player might have multiple Operator data under different mod implementations, you need to configure the appropriateContainerIdto ensure the entity correctly captures the corresponding data upon loading. For data capturing, refer toFindOperatorEvent. If theGroupProvidermentioned in the first step is implemented and registered, related events can be automatically handled. - Operator (
Operator) Is the unit that can be directly captured and referenced by the Operator entity and is responsible for storing Operator information. This includes methods related to basic Operator behaviors such as deployment, withdrawal, legality checks, as well as basic information such as Operator type, status, last recorded position, etc. The referenced Operator entities will not be null as long as the entity exists and is loaded. - Operator Data (
OperatorInfo) Responsible for storing additional information about Operators. If needed, Operator entities can store similar types of information and request merging at appropriate times to implement temporary information functionality.
You can refer to the TestObjects class to see our
test code.
Calling the TestObjects#initTest method in the mod's main class will activate it—don't forget to remove it afterward.
You can also view the provided events in EventHooks.
Each event class contains javadoc content about its usage.
Additionally, you can refer to our TEST_LIST to see and verify the features that can be automatically implemented under correct configurations.
Contributing
We welcome contributions to the Nonatomic mod. You can submit Issues to report problems or Fork this project to submit your improvements.
Developer
- Mon-landis: Provides technical support and development.
瓦解核心：非原子单位 | Brea:Nonatomic
Overview
The Nonatomic Lib allows players to deploy Operators in the game. Operators correspond to Operator entities, and players can deploy them to perform various tasks.
This library provides a range of commonly used features for the entire Operator system:
- Operator Customization: Allows the customization of various types of Operators, each with unique attributes and behaviors.
- Operator Information Storage: In addition to customizable attributes, Operators have the capability to store mutable and persistent information.
- Entity and Information Communication: Operator entities and their information reference each other, with appropriate clearing and refreshing to ensure synchronization and proper status.
- Player Behavior Handling: Special player behaviors affect entity states to ensure proper functionality, including login, logout, teleportation, etc.
- Event Listening: The mod listens to game events, such as player login, logout, and the deployment and retrieval of Operators, to enhance flexibility.
Code Framework
Ideally, we can directly bind data to dimensions for unified management—this ensures that Operator data references are maintained when players are offline and avoids crashes due to excessive player data.
The data structure is roughly as follows, from broadest to most specific:
- World Data Storage. We do not provide a standard for this level,
but we offer
the
GroupProviderinterface (see at the bottom) for convenient handling of player and entity events. - Player Operator Data (
OpeHandler) Stores data on Operators owned by a player and a list of deployed Operators. Since a player might have multiple Operator data under different mod implementations, you need to configure the appropriateContainerIdto ensure the entity correctly captures the corresponding data upon loading. For data capturing, refer toFindOperatorEvent. If theGroupProvidermentioned in the first step is implemented and registered, related events can be automatically handled. - Operator (
Operator) Is the unit that can be directly captured and referenced by the Operator entity and is responsible for storing Operator information. This includes methods related to basic Operator behaviors such as deployment, withdrawal, legality checks, as well as basic information such as Operator type, status, last recorded position, etc. The referenced Operator entities will not be null as long as the entity exists and is loaded. - Operator Data (
OperatorInfo) Responsible for storing additional information about Operators. If needed, Operator entities can store similar types of information and request merging at appropriate times to implement temporary information functionality.
You can refer to the TestObjects class to see our
test code.
Calling the TestObjects#initTest method in the mod's main class will activate it—don't forget to remove it afterward.
You can also view the provided events in EventHooks.
Each event class contains javadoc content about its usage.
Additionally, you can refer to our TEST_LIST to see and verify the features that can be automatically implemented under correct configurations.
Contributing
We welcome contributions to the Nonatomic mod. You can submit Issues to report problems or Fork this project to submit your improvements.
Developer
- Mon-landis: Provides technical support and development.
Screenshots
Gallery
Versions
Files
Relations
Project Relations
More like this
Similar Mods
Suggestions use data such as tags, dependencies, dependents, descriptions, titles, and more to rank how much they overlap with this mod.
On ModDex
Community snapshot
By the numbers
Statistics
Want to reach Minecraft players?
We're looking for a server hosting partner to feature here and other parts of the site. Interested? Send us a message!
Get in touchGet it on
Available Platforms
On ModDex
Community snapshot
By the numbers
Statistics
Resources