You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we need to implement the logic and idea correctly and completely, this feature (https://minecraft.fandom.com/wiki/Riding) would still be needed, instead of just targeting implementing the feature in the simplest and easiest way. This behaviour and direction have been used for a long time with Load and the static class structures as examples. (Taken from a Discord message in the boat post.)
Details
This issue is mainly related to the functionality, but not the actual entities to implement.
There should be a map (a BiMap is recommended.) mapping the entity riding relationships. The map should be stored in a separated file in save. When the save system is rewritten, the data of the passenger can be instead recorded within an entity recursively instead of using a separated mapping. The position of the passenger is led by the mount and the boat is controlled by the player when being ridden. An entity can only be ridden and/or riding not more than one entity not being ridden by the entity itself.
Player Riding
In general, if players want to ride a mobs that are intended to be rideable, a saddle must be installed. If they are required to be tamed, they must first be tamed before being able to control, even a saddle is installed, but a saddle is not required when taming.
Entity Implementation
Not all entities would support bonuses, but entities would have their own characteristics for their own usages, but sometimes it might just be interesting without actual uses.
The text was updated successfully, but these errors were encountered:
Original: MinicraftPlus/minicraft-plus-revived#561
Background
If we need to implement the logic and idea correctly and completely, this feature (https://minecraft.fandom.com/wiki/Riding) would still be needed, instead of just targeting implementing the feature in the simplest and easiest way. This behaviour and direction have been used for a long time with Load and the static class structures as examples. (Taken from a Discord message in the boat post.)
Details
This issue is mainly related to the functionality, but not the actual entities to implement.
There should be a map (a
BiMap
is recommended.) mapping the entity riding relationships. The map should be stored in a separated file in save. When the save system is rewritten, the data of the passenger can be instead recorded within an entity recursively instead of using a separated mapping. The position of the passenger is led by the mount and the boat is controlled by the player when being ridden. An entity can only be ridden and/or riding not more than one entity not being ridden by the entity itself.Player Riding
In general, if players want to ride a mobs that are intended to be rideable, a saddle must be installed. If they are required to be tamed, they must first be tamed before being able to control, even a saddle is installed, but a saddle is not required when taming.
Entity Implementation
Not all entities would support bonuses, but entities would have their own characteristics for their own usages, but sometimes it might just be interesting without actual uses.
The text was updated successfully, but these errors were encountered: