I’ve been noticing this happen in studio lately where proximity prompts will randomly appear at infinite distance. Now it’s happening in live gameplay. Not sure if this is a bug, but I dont know why it is happening. There are no proximity prompts in my game with activation distance greater than 100 and this is confirmed through command line console. I even tested in studio on client and setting all prompts to maxactivation 10 on client using classname:ProximityPrompt → still seeing the prompt.
The bug can be seen in this game: ∞ Nights in Tower Defense - Roblox
I think this would be an error with your game itself, not an engine issue.
Try creating a proximity prompt separate from the one you currently have to troubleshoot and see if maybe it’s a setting you have on the one showing infinitely. I myself haven’t run into this issue tho.
as you can see in this sccreenshot I have the proximityprompt properties open and it clearly shows maxactivationdistance of 10 but I can still see it despite the fact that im very far away–so far away in fact that the part it is attached to is streamed out of the world. I also checked on the server–the prompt has maxactivationdistance of 10 there too.
Try turning on “RequiresLineOfSight” property
this shouldn’t affect maxactivationdistance
That’s weird, I’ve only ever had an issue similar to this when using custom proximity prompts.
Try creating a prompt in another workspace and see if this error were to occur. But if I were you, I’d just go ahead and create my own proximity prompt like system, that doesn’t involve the use of Roblox’s proximity prompts.
nevermind, I found the issue. streaming was messing it up. Not sure why, but when you parent a proximity prompt to a model, and the model’s primarypart is streamed out, the proximity prompt remains in a sort of glitched state, ignoring the maxactivationdistance. Never noticed this before… I’ve been using this system for a while with streaming on–not sure if this is a new thing.
Can be seen in this file:
proximityprompttest.rbxl (63.4 KB)
Note: setting the model streaming mode to atomic resolved the issue. Seems to be a bug with the streaming out of proximity prompts parented to models. Hope roblox fixes this issue or clarifies if this is intended functionality.