Error spam with homing RTD

[Wheretf2]

Bug description

Hello,

We're having some issues with error logs being spammed with a reoccurring error from the homing roll

L 06/15/2024 - 20:07:49: SourceMod error session started
L 06/15/2024 - 20:07:49: Info (map "trade_minecraft_neon_v197") (file "/home/burokai/tf2/tf/addons/sourcemod.idle/logs/errors_20240615.log")
L 06/15/2024 - 20:07:49: [SM] Exception reported: Property "m_vInitialVelocity" not found (entity 150/spotlight_end)
L 06/15/2024 - 20:07:49: [SM] Blaming: rtd.smx
L 06/15/2024 - 20:07:49: [SM] Call stack trace:
L 06/15/2024 - 20:07:49: [SM]   [0] GetEntPropVector
L 06/15/2024 - 20:07:49: [SM]   [1] Line 1520, rtd\stocks.sp::Homing_TurnToTarget
L 06/15/2024 - 20:07:49: [SM]   [2] Line 1513, rtd\stocks.sp::Homing_TurnToClient
L 06/15/2024 - 20:07:49: [SM]   [3] Line 1506, rtd\stocks.sp::Homing_FindTarget
L 06/15/2024 - 20:07:49: [SM]   [4] Line 1429, rtd\stocks.sp::Homing_Think
L 06/15/2024 - 20:07:49: [SM]   [5] Line 1416, rtd\stocks.sp::Homing_OnGameFrame
L 06/15/2024 - 20:07:49: [SM]   [6] Line 798, C:\Users\Nitro 5\Desktop\SM Compiler\1.11\!Compiler\rtd.sp::OnGameFrame

This error has generated a 600MB error log from being triggered so rapidly
I haven't been able to reproduce this error, although I have many logs of in occurring
Running 2.5.5
Not using any custom cfg
I also sent you a friend request on discord so we can communicate if needed

Report checks

Please describe the bug in the section above, then post it and tick the correct boxes below.

Required

• The bug does not have an open issue.
• I have described the bug.
• I mentioned whether the bug is sporadic or systematic.

Optional

• Steps to reproduce the bug are known and have been described.
• I have access to server error logs and have provided them, if any.
• I am able to check the RTD version (sm_cvar sm_rtd2_version) and have specified it.
• I have access to RTD default configuration file (rtd2_perks.default.cfg) and can confirm it's the one bundled with plugin release archive.
• I have access to RTD custom configuration file (rtd2_perks.custom.cfg or other) and have attached it to this issue.
• The issue is related to a particular perk, which has been specified by a label.