flux reports: probably dragon fire and blaze ... #4860
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#4860
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?
flux reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
I think blaze fire should, but dragon fire shouldn't.
Cleaning up dragonfire after a major battle is not the funnerest thing to do, so yes, both should go out after a while.
There is already a node timer on them, they go out if there's no burning material nearby. Let's take this nodetimer and make it 10x longer, then go out if there's flammables close.
I had confused my thumb down with the dropping of the Blaze.
i implemented this:
2275264922
there's now a chance for it to extinguish if there's a flammable node nearby.
similarly for blaze fire (required creating a separate node for it)
f4ab870ec2
QA
Dragonfire goes out nicely after a while
Blaze somehow doesn't, most likely because in line 157 it still fire basic_flame instead of yl_nether_mobs:blaze_fire
QA: Both flames go out after a while :)
Aliza's not gonna be happy about this lol
I know, but it still needs to happen ....
this is live