re-enable petz.throw? #2592
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#2592
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?
it's disabled here:
i'm not sure why it was disabled. did it used to crash? we're running a much newer version of petz. should we test re-enabling it?
seems like it was disabled here:
b3f24f31c2
Now if I only knew why I did that. I guesss it had to do with an error caused by the petz throw, but in a different position. If we re-enable we need to test all around petz other throw parts, where all of those functions play a role.
noting that this is more-orless a dupe of #2265
the commit says "bugfix grenade", i've just remembered that petz has a "jack-o-lantern grenade". i'm not sure what problems those cause, but possibly it was because they explode, and explosions are now "fixed".
i'll re-enable it locally and do some testing and see if anything interesting occurs.
MAybe it was an emergency hotfix because the grenade didn't respect protections?
after testing, i found one major issue, but that can be disabled w/out disabling the throw mechanic entirely.
the issue is that jack-o-lantern grenades don't respect PvP, and the throw mechanic doesn't record who threw the grenade, so there's no easy way to integrate that. however, it's trivial to disable jack-o-lantern grenade damage in petz's
user.conf
.i disabled the damage in
5ac142ac41
, and re-enabled petz throw ine1031d6222
. we can play w/ this more on the test server.this is live. enjoy playing fetch w/ you puppies and hopefully not punching them