Skip to content
This repository has been archived by the owner on Sep 3, 2022. It is now read-only.

Weird Relic/Minion Behavior #1373

Open
cabeca1143 opened this issue Mar 22, 2022 · 2 comments
Open

Weird Relic/Minion Behavior #1373

cabeca1143 opened this issue Mar 22, 2022 · 2 comments

Comments

@cabeca1143
Copy link
Contributor

cabeca1143 commented Mar 22, 2022

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:

  • All Relics will be rendered globally regardless of vision.
  • OdinShieldRelic and HA_AP_HealthRelic won't have their minion affected by the NoRender flag.
  • HA_AP_HealthRelic works normally besides the first issue.

Map10:

  • The NoRedender flag works normally for all relics.
  • OdinShieldRelic and TT_Relic wont have their particles redered at all if it was created out of vision, but if created while you had vision, will work normally
  • HA_AP_HealthRelic will be rendered globally regardless of vision.

Map12 (Disabled turrets for testing):
- As in map10, OdinShieldRelic and TT_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.

@cabeca1143 cabeca1143 changed the title Weird Relic Behavior Weird Relic/Minion Behavior Mar 22, 2022
@cabeca1143
Copy link
Contributor Author

Issue seems to have started in #1329

@cabeca1143
Copy link
Contributor Author

The issue seems to be caused by a Replication packet being sent alongside the visibility packet in NotifyEnterTeamVision in PacketNotifer.cs

lzardy pushed a commit that referenced this issue Apr 21, 2022
Added `isTargetable: false` argument to `CreateJungleMonster` call and eliminated duplicate code
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant