Proximity Prompt Release

[Ejioplex (Ejio)]

Just finished making my own system when this got announced. I still prefer making my own proximity prompt system but this new system will be convenient.

[Timelens]

Then you can use an ImageLabel.

[tacheometrist]

How would I only show part of the circle by scripting without uploading tons of images then?

[Timelens]

Off the top of my head mate? Not a clue right now, but I imagine you could just upload a segment of the arc/circle and make a script to duplicate it and rotate each duplicated instance according accordingly.

[iGottic]

cc: @Timelens

@Robloxian_Thinking

How would I only show part of the circle by scripting without uploading tons of images then?

UIGradient solves that. This has also been done on the DevForum before.

Regardless, it might have been better to leave the replies for relevant issues, not for scripting or UI support.

[crypto_mancer]

@SillyMeTimbers

tldr - I used a custom UI and can’t use my mouse to activate it (For mobile support) any suggestions?

When you create your custom UI, you can listen for InputBegan and InputEnd on your button, and call these from within:
prompt:InputHoldBegin()
and
prompt:InputHoldEnd()

You can see an example of that in the customization code sample here:

ProximityPrompt | Documentation - Roblox Creator Hub

[ImSimplyAnna]

This is cool! Really nice to finally have a dedicated tool for this, akin to the ClickDetector instance.

One thing I’d say that could be improved is that when a part has multiple ProximityPrompt instances, that it displays one UI with both of the buttons shown. This would be useful for cases like doors where you have the option to either open it or lock it, or the option to break down a door vs. lockpicking it. Right now, the ProximityPrompt just creates two GUIs that overlap:

EDIT: I realize this is possible with the UIOffset property, but it would be nice if Roblox handled that automatically out of the box.

[DybalaplaysYT (questforLa_Flame)]

No, because countless games are using ClickDetectors

[lexidogfur (lexidog)]

Proximity Prompt Studio Beta

Great questions! It updates at your current framerate. The task scheduler is not used currently. By default, it uses the PrimaryPart of the local player’s Character, which by default is the HumanoidRootPart. If no character exists, it uses the camera’s focus position You can use the camera’s focus position if player.Character is nil. You can also set the player’s character to a non-humanoid model, in which case the PrimaryPart’s position will be used for proximity prompts.

[Spare_Access (Lord_Wither)]

I would like to point out that, countless games relied on legacy lighting, outlines and legacy terrain, yet roblox removed them, in such a way that the games were still playable, I believe a similar thing will happen to Clickdetectors, roblox will slowly start deprecating them like it did to the above mentioned features, before announcing a final deadline for it’s removal, I believe that they will convert existing Clickdetectors in games to proximity prompts, similar to how they converted legacy terrain to smooth terrain, this way, they will ensure old games do not break

[AbstractAlex]

@ImSimplyAnna

One thing I’d say that could be improved is that when a part has multiple ProximityPrompt instances, that it displays one UI with both of the buttons shown. This would be useful for cases like doors where you have the option to either open it or lock it, or the option to break down a door vs. lockpicking it. Right now, the ProximityPrompt just creates two GUIs that overlap

100% support for this.

We use proximity interactions in all of our games, however they also require showing multiple/variable options at once. This requires writing a large custom wrapper on top of ProximityPrompts to handle building these lists and setting their keybinds in real time.

Here is a demo I wrote but it required a significant amount of custom code.

Here is how we use interactions in Robloxian High School:

I think if this feature supported multiple-options there would be hardly any reasons to use a custom implementation anymore!

[SillyMeTimbers (Silly)]

Absolute lifesaver, thank you!

[SillyMeTimbers (Silly)]

That is technically possible with the current system. Although you will have to mess with the UI Offset quite a bit for each one.

[PPenter1 (PetyaDev)]

Thanks, Roblox! It helped a lot!

[PPenter1 (PetyaDev)]

Yes, you can do that with a script in my opinion. Scroll up, there are a few examples😄

[otcrunchy]

This has removed alot of work for something so simple and helped performance. Great addition

[Daw588]

This is great, the only thing that I want to be added to this is automatic handling for multiple prompts in one position, so like if you have 2 prompts in one part, it will show 2 nicely aligned prompts, and thats all .

[SillyMeTimbers (Silly)]

I’m sure that would be helpful but eventually someone will write a script to do that automatically.

[Rookstun]

This is great! I’ve always a ClickDetector for KeyInputs. I’m a bit concerned what will happen when two entities with ProximityPrompts are close to eachother though. I’d rather priority be based on the where the player is facing instead of just distance.

[smuffgahmin (smuff)]

This is a really awesome feature, it’s great to see compatibility for games and platforms becoming much better.