The code does not check if CFrame is nil.
Expected behavior
There should be no errors from PlayerModule.
3 Likes
Thanks for the report! We’ll follow up when we have an update for you.
1 Like
Hello!
What is the type of the Camera that you’re using (or are you just using the default)? Do you have any steps to reproduce this issue, or is it just showing up in your dashboard?
1 Like
This is the default Roblox camera script, I’m not forking the script. This is an error within module probably because sometimes it parses nil or cframe is nan. I’ve only seen this on my dashboard.
I assume that means you also use the default PlayerScripts and not a fork, correct?
1 Like
@ProtoValence If this error doesn’t correlate to the Poppercam code whatsoever, keep in mind that it could be from players who are exploiting by replacing the script with their own for whatever reason
If exploiting is the reason then they should ban the exploiters they’re already detecting, I suggested this before. What they could do is list the user ids under client error reports to at least allow us to ban them from the game.
1 Like
In this case it does correspond to the code in PlayerScripts directly, so this being an exploit is unlikely. I could make a change that just checks for the CFrame and call it a day, but I’m looking a bit deeper because it might be indicative of a different problem.
1 Like
I’ve been looking for a repro, but unfortunately haven’t been able to do so yet. Could you take a screenshot of your PlayerScripts folder and PlayerScripts Settings? Thanks!
Also do you modify the current camera or update any of your camera’s settings in any of your scripts? If so, what specifically do you do?
Also, has it appeared again since the last time it came up, or has it since vanished from your dashboard?
It still appeared on the dashboard a couple of days ago.
The only properties I change are camera type, subject and cframe for things like shops and cutscenes.
I will add more after I’m able to do so.
Another log, might be related to camera script
