This repository has been archived by the owner on Sep 3, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 427
Weird Relic/Minion Behavior #1373
Comments
Issue seems to have started in #1329 |
The issue seems to be caused by a Replication packet being sent alongside the visibility packet in |
lzardy
pushed a commit
that referenced
this issue
Apr 21, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There's an odd issue with relics and i haven't been able to track it down, seems to be somehow related to maps, i've tried moving things around, changing models, buffs, names, i couldn't pinpoint anything besides the different map.
The following is the documentation of this issue:
Map8:
OdinShieldRelic
andHA_AP_HealthRelic
won't have their minion affected by the NoRender flag.HA_AP_HealthRelic
works normally besides the first issue.Map10:
OdinShieldRelic
andTT_Relic
wont have their particles redered at all if it was created out of vision, but if created while you had vision, will work normallyHA_AP_HealthRelic
will be rendered globally regardless of vision.Map12 (Disabled turrets for testing):
- As in map10,
OdinShieldRelic
andTT_Relic
requires vision when it is spawned in order to be rendered at all.-
HA_AP_HealthRelic
will be rendered globally regardless of vision.- If no relics have ever been in your vision, and you have vision of 2 relics spawning at the same time, the NoRender flag won't be applied until it get's out of vision, this issue is present for all relics.
- In the scenario mentioned just above, with
HA_AP_HealthRelic
, the Targetability flag wont be applied either, so you can attack it and even land skillshots.TT_Relic
can be hovered and selected, but not targeted. Both issues goes away when it gets out of vision.The text was updated successfully, but these errors were encountered: