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

[BUG]: Being in a different team than expected makes the particles get indexed out of bounds #122

Open
StShAzzy opened this issue Jun 15, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@StShAzzy
Copy link

StShAzzy commented Jun 15, 2024

check the player's team if it's unassigned or spectator, and if it is, just force to use either red or blue variant

or if you're that mean, you could just not allow players to roll if they aren't on either red or blue team, which would suck as it's not the proper fix

@StShAzzy
Copy link
Author

switch (TF2_GetClientTeam(client))

this one for instance when you're in spectator but alive and players (has a playermodel and everything else, but it's just in another team)
causes the particles to get indexed out of bounds, grabbing any junk nearby, some times it's harmless because the particles despawn, other times, spawns particles that don't despawn, which means the client will crash if too many spawn, as it runs out of edicts for rendering particles

@Phil25
Copy link
Owner

Phil25 commented Aug 22, 2024

I don't recall spectator abuse being an issue, so not sure why these problems are coming out now. I'm wondering if anything changed in the latest upgrades, maybe the 64 bit one, where players in spectators are considered alive.

In any case, RTD hasn't been designed with this in mind, so that's definitely needing of a fix.

@Phil25 Phil25 added the bug Something isn't working label Aug 22, 2024
@StShAzzy
Copy link
Author

no, you can just forcefully set players to different teams using plugins

@StShAzzy
Copy link
Author

without using the SourceMod function that also kills you, by changing m_iTeamNum to 0 or 1

@StShAzzy
Copy link
Author

if any question arise in your head regarding this, please contact me, i'll be happy to make sure it gets fixed properly

@StShAzzy
Copy link
Author

I don't recall spectator abuse being an issue, so not sure why these problems are coming out now. I'm wondering if anything changed in the latest upgrades, maybe the 64 bit one, where players in spectators are considered alive.

i was just too lazy to actually come and report it as soon as i found it out and could replicate it

CrazyShootin added a commit to CrazyShootin/RTD-Fork that referenced this issue Nov 8, 2024
Easy patch in regards to the spectator exploit with one being able to go into spectator and still being able to have an RTD perk active and/or roll while in spectator, ruining players experience of RTD. 
So with this fix implemented hopefully it will stay gone!

in regards to issue Phil25#122 and Phil25#125
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants