Trying to realize the best way for magnitude interaction, help me

[Korrow (Peter)]

I currently have this simple script, but I am trying to understand if it always works like this, how/which parts get prioritized to get selected in the magnitude range?
I also use CollectionService to get all these parts.

local cs = game:GetService("CollectionService")
local uis = game:GetService("UserInputService")

uis.InputBegan:Connect(function(input, gameProcessed)
	if input.KeyCode == Enum.KeyCode.E and not gameProcessed then
		for _,Interactable in pairs(cs:GetTagged("Interactable")) do
			local Magnitude = (Interactable.Position - game.Players.LocalPlayer.Character.HumanoidRootPart.Position).magnitude
			
			if Magnitude <= 10 then
				print(Interactable.Name)
			end
		end
	end	
end)

game:GetService("RunService").RenderStepped:Connect(function()
	script.Parent.InteractionPrompt.Visible = false
	
	for _,Interactable in pairs(cs:GetTagged("Interactable")) do
		local Magnitude = (Interactable.Position - game.Players.LocalPlayer.Character.HumanoidRootPart.Position).magnitude

		if Magnitude <= 10 then
			local coords2D = game.Workspace.CurrentCamera:WorldToScreenPoint(Interactable.Position)
			script.Parent.InteractionPrompt.Position = UDim2.new(0, coords2D.X, 0, coords2D.Y)
			script.Parent.InteractionPrompt.Visible = true
		end
	end
end)

Is this a good method cause I don’t know anything else lol.

[starmaq]

My article might interest you!

Best way to handle collectables

It’s very common for a game to have a sort of collectable objects system. Usually people go for the simplest strategies, such as the infamous loop through all objects in the game and make magnitude checks. Some spice things up and end up using a Region3, but still, updating a Region3, and getting all of the objects inside of it is still a really heavy process to do every frame. Today I will show you a great strategy for doing this! The idea is rather basic, imagine that your game is made up of…

Making a chunk system and only checking for objects tagged with "Interactable" in the surrounding chunks less often than the usual 60 times a second (if running on 60 fps) is better than all "Interactable"s 60 times a second.

[Korrow (Peter)]

This is a promising idea, I can’t believe I didn’t find your post when researching, it’s under-rated.

[Korrow (Peter)]

But there is still a prioritization issue even w/ your method that I see
I believe there should be an easy fix, is it possible you can think of one?

Edit: I believe like you wrote, clearing the table should’ve fixed it but by even click E once 2 of them disappeared
Edit2: nvm it wasn’t to clear the last part you were near lol