refactor LibPlayer and LibEntity #109
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
LibEntityLibEntitytoLibMachineBuild, since it handles machine entity creation, not abstract entity stuffLibPlayer, particularlygetSpawnedPlayerEntity, which can be used in all systems to get the player entity and ensure it's spawned without many lines of overheadLibMachineBuild.createwithinLibPlayer.spawnto create machine-like aspects of playerLibUtils.addressToEntityKey(_msgSender());toLibPlayer.getSpawnedPlayerEntity();, which makesaddressToEntityKeymostly obsolete, as it's only used inLibPlayernowThis PR was more of an accidental distraction, hopefully it's still useful