AliasAlreadyTaken reports: testserver Apparently we have tracer ammo ... #6079
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#6079
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?
AliasAlreadyTaken reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Keep it, make it
special staff item maybe, but it's useful :)Alias suggested a command that will toggle this - could be more useful for different types of ammo.
AliasAlreadyTaken reports: Apparently we have tracer ammo ...to AliasAlreadyTaken reports: testserver Apparently we have tracer ammo ...I kinda forgot... x_bows did have similar white trace, I think y_bows should also have this.
Having trace helps immensely with aiming - so at least the shooter should see it, but:
When shooting flying targets or even just slow stone monsters when there's lag (1s+ dtime) this helps so much, that it's a must have. Because otherwise you can't see the arrow traveling due to lag. And judging distance without stereo vision is near impossible.
Not sure if other people besides shooter should also see the trace, but maybe could be helpful too?
UPD: I see that the arrow itself also leaves trace, but it does not appear properly (or at all) when there's lag. And red trace appears always. In fact, during lag white trace can appear in completely different place (I suppose it's using
moveresult
still)("arrow trace particles do not appear when there's lag" should be it's own issue maybe?)
Perhaops these tracers can be kept on a "testing arrow" that does zero damage
.... and has no craftign recipe, then yes.
it's a setting:
ballistics:show_estimated_path
. i've currently set it to be "on" by default, while we're working on debugging things. eventually it'll be off by default.y_bows does have this as well, though perhaps it's not emitting as many particles as it should. emitting some every server step seemed to be too many.
probably i should make it a property of specific projectile entities instead of a global setting, though.
I didn't notice them at all because I tested with lag enabled, and during lag they all bunch up and appear in a completely different place (like
moveresult
arrows did). Seems like they should use tracing results if we want to see them on main...There's your-land/administration#132 (comment) by LMD, apparently he already tried to do stuff with missiles in MT, but quote "its not so easy"
i've solved at least some of those problems and discovered a host of new ones :) i do think we'll end up w/ something that'll solve a lot of our long-standing issues w/ x_bows though.
yeah, now that we've got the path-casting, it should be pretty easy to ensure that more particles show up when there's lag.
i've removed the trace
73c0695497
QA
The tracer ammo vanished
this is live