Skip to content
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

[Idea] Make beacons last longer (to make them more usefull) #2061

Open
illwieckz opened this issue Aug 12, 2022 · 2 comments
Open

[Idea] Make beacons last longer (to make them more usefull) #2061

illwieckz opened this issue Aug 12, 2022 · 2 comments
Labels
T-Improvement Improvement for an existing feature

Comments

@illwieckz
Copy link
Member

Issue initially reported there: DaemonEngine/Daemon#642

Hi!

The beacons appears for only 3 or 5 seconds, that is too short.
The time to almost understand where is it, and it lost.

Also, a path on ground (with jump possible?) to the nearest beacon should be show for Aliens, and Humans with helmet.

Humans bots should also put beacons, when they saw Aliens buildings for example.

When the building disappear, the beacon should too.
For beacons for defend, attack... I think 30 seconds should be enough.
-- @superdupont-fr

Ideally we would have some lifetime management for beacons because even when "Defend" used to last 10s I often came for nothing because it was too late already

EDIT: the idea would be to make the beacon disappear if the attacker is killed in case of a Defend beacon, if the author of a "time sync" > beacon is killed, etc. (Note that it's hard and I dont intend to do it)
-- @necessarily-equal

@illwieckz illwieckz added the T-Improvement Improvement for an existing feature label Aug 12, 2022
@slipher
Copy link
Contributor

slipher commented Aug 12, 2022

We just went over beacon durations and increased some of them. UnvanquishedAssets/unvanquished_src.dpkdir#122

@ghost
Copy link

ghost commented Aug 12, 2022

Yes, all duration which were easy to adjust were done. Sadly, it does not means that all useful beacons had this problem improved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Improvement Improvement for an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants