-
-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Llama are not controllable #1507
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I can replicate this on 1.20.6-2233 (the latest version as of writing this) |
This is also affecting new entities. For example, no config entry is generated for the breeze, added in 1.21, and if I add one manually and set |
That is unrelated (and doesn't make sense) since the options for the Breeze mob haven't been implemented yet (Although I thought I had...). Feel free to create a new issue in regards to missing ridable options for the breeze mob. If you could also check to see if any other mobs are missing that would be great. |
Seems like that riding is completely broken in 1.21.3 |
I'm having the same issue as @Onako2 where controlling mobs while riding is completely broken. I'm on build 2355 of 1.21.3. |
I didn't realize Onako meant all mobs were broken.. This isn't the issue for tracking that. Please create a new issue so I can track this better. |
Spark link
https://spark.lucko.me/ECUeK9Rs15
Expected behavior
As written in the purpur.yml config, the llama should be rideable and controllable, but when I tame it and put a carpet on it, and step on it, it is ridable but not controllable, it does not react to WASD commands
Observed/Actual behavior
At present, the tamed and equipped llama of a carpet is only ridable but not controllable
Steps/models to reproduce
Open purpur.yml and set llama controllable and ridable
Then, ride it
Purpur version
git-Purpur-2169 (MC: 1.20.4)*
Agreements
Other
No response
The text was updated successfully, but these errors were encountered: