Petz #6129
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#6129
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
From Server Zeitsprung.
this is not the place to report petz bugs that don't specifically affect the your-land server. please report this upstream: https://github.com/runsy/petz/issues
probably because of https://forum.minetest.net/viewtopic.php?p=431721#p431721 and the following post
runs has certainly started at least working on the mod somewhat again, though i fear either i or your-land will have to adopt the mod more formally. but that hasn't happened yet.
Right and after i have talked with AliasAlreadyTaken.
Sorry.
i didn't know you had such a bureaucracy.
Bye.
apologies, i didn't mean to offend. i admire your work, cucina_vegana in particular. we just don't have time to fix all of our own issues (over 2000 are open), let alone those of others. i don't understand the petz code well enough to know what sort of entity it expects to have a "height" parameter or why. only runs knows why that code is the way it is. i could fix the crash with a nil check, but that'd be a PR to upstream, and i know you can do the same yourself.
and i really don't want to encourage the whole minetest community to come here and report all of their problems in the hope that i'll fix them. this is just the your-land bugtracker.
Then let's see whether runs keeps going and if not, let's adopt it formally.
One issue with adopting, is that petz repo has only b3d models. I'm not sure how to edit them keeping the animations, since blender plugin does not support animation import yet... And Runs can be using blender to just export to b3d. If he does, then hopefully he will post original blender files too...
That's where we have a slightly secret weapon ... I believe the original blender files are here: https://github.com/runsy/petz_raw
And on top of that, there's someone who can read them and work with them and already pushed a couple of fixes upstream.
All ok, flux, nothing has happened.
I understand, when you say, you have more than enough own issues to fix.
Runsy has always fixed the issue and this were never a problem with this, but as i read, he don't want to work again on petz,
so i was asking AliasAlreadyTaken.
As long runsy will take care about the issues, i will post him. After them, i don't know, as long petz is running fine, i will have it on my servers, but then, chi sera ;-).
Greetings, Clyde.
This is fixed upstream