ProximityPrompts further away are not working

Help and Feedback Scripting Support
, , ,
1

Hey Developers,

I have a weird problem. When I press “Play Here” (starts the game where you are in edit mode), only the proximityprompts near my spawn is working and proximityprompts about atleast 150 studs away from my spawn aren’t working. They show up normally but the interaction isn’t working (.Triggered event).

I am not sure why is this happening. The one possible problem that may cause this would be the map size. Map is pretty massive and has a lot of details. Before it worked normally but after I made 1 more room, this problem appeared.
If the problem is the map size then why is that causing this problem? Plus, I am not going to remove rooms from the map because it literally took so long to make plus it’s meant to be massive. I don’t understand why Roblox keeps bad servers and don’t want to get better servers.

If something else is causing the problem, I would like to know it asap.

So let me explain everything quickly if someone didn’t understand:
ProximityPrompts aren’t working. Only the ones near your spawn are working but other ProximityPrompts aren’t working. They show up normally but the .Triggered event isn’t working.

Quick Answers:

Is it because objects are blocking the ProximityPrompt?

  • Nope, there are no object blocking the ProximityPrompt. Those works normally if you spawn near those.

I didn’t understand the problem exactly…

  • Let me explain. We have ProximityPrompts A and B. If I spawn near A or B, the other one is over 200 studs away from me. If I spawn near A, A works but B doesn’t work. If I instead spawn near B, B works but A doesn’t work.

Is the StreamingEnabled on?

  • Yes, the reason is because we have a massive map so your game might crash if you have low end pc and StreamingEnabled is disabled. It may cause this ProximityPrompt problem but I have never changed it before and ProximityPrompts worked normally earlier.

If you have ideas, tell me please. I literally cannot do anything now because I want to test some things but this is stopping me from doing it. I have like 3 year Roblox Studio experience. I am almost good at everything and that’s why this is confusing, I can’t fix this weird bug.

2 Likes
2

Is the script detecting when you interact with the proximity prompt a local script or a server script?
How are you accessing the proximity prompt in the script?

3

I use server scripts on every ProximityPrompt and usually these scripts are inside the ProximityPrompt. I usually do script like this:

local prox = script.Parent
prox.Triggered:Connect(function()
   print("Triggered")
   -- other things
end)

and the result is…
nothing comes out.

ProximityPrompts near spawn are only working and other don’t work. If I move my spawn, proximityPrompts near my new spawn are now working and others don’t.

4

If you add other print statements within the scripts, so they output before and after the triggered part, are all the scripts running correctly? (just to narrow down the issue)

5

I tried to add print statements before and after Triggered function and they were in the output normally but the proximityprompt didn’t work.

local prox = script.Parent
print("Check1")
prox.Triggered:Connect(function()
   print("Triggered")
   -- other things
end)
print("Check2")

I can try to add while loop that continously prints out smth to show if the script is still working.

6

I made the whileloop check and it turns out that the script works but the Triggered function doesn’t work.

while true do
	wait(1)
	print("PROXSCRIPT WORKS")
end
7

I’ve tested proximity prompts being quite far away (1000 studs away) in my own place, but I can’t seem to replicate the same issue.

Can you please test if the proximity prompts work as expected if you play the game (e.g. from the website), rather than accessing it through Studio?

1 Like
8

I tried in Roblox Player and it’s in Roblox Player too. It doesn’t matter if you use Studio or Player, it’s still same.

The thing is that I don’t know what causes it really, how to fix it and why it happens.

9

Do you have streamingEnabled enabled in the workspace? If so, are the proximityPrompts being loaded correctly?

10

My bad I reread your post and you do have enabled. However, I tested in studio and that shouldn’t be the problem. I’d suggest you make sure “RequiresLineOfSight” is enabled, as well as “ClickablePrompt” (if you want the prompt to be triggered by holding the left button on it). If that doesn’t fix it I am sorry.

11

The problem isn’t that because they should work normally and they do if they are near your spawn.

12

How about RequiresLineOfSight? That might change when you are far away, maybe some invisible parts or something?

13

They mentioned about 3 times that the issue is not related to the prompt visual, RequiresLineOfSight is a visual feature. Additionally, it cannot be due to StreamingEnabled, as it only affect the client, yet these are server scripts.

14

What is the RunContext of you scripts?
Have you tried to use wait time before running the script to make sure instances are loaded?

15

I use server script like this:
{A2F1905E-35A1-4740-8928-889F3F2FA34B}

I directly just use

local prox = script.Parent

and don’t put like

wait(10)
local prox = script.Parent.Parent:WaitForChild("ProximityPrompt")

Now I tried that on one script and it did… nothing.

The weird thing is that everything was normal earlier but now this came like out of nowhere. I first though this was some kind of bug in studio because at the same time all of us had the problem about saving game project. After this project saving thing got fixed, this however did not get fixed and I tried to check if anyone else had this problem too but I figured out that I am the only one facing this problem. Now I have tried to solve this like may times but still having this same problem. Imagine having a problem like this and you don’t know what causes it, how to fix it and is it even possible to fix it.

16

I would like to get a solution as soon as possible. I literally cannot do anything right now because of this annoying problem.
[EDIT]
Likes does not help me. I need answers, not likes.