Having trouble with highlights

Help and Feedback Scripting Support
,
#1

this script creates a part and 2 highlights they are both parented to workspace.

local part = Instance.new("Part", workspace)
part.Anchored = true

local highlight = Instance.new("Highlight", workspace)
local anotherHighlight = Instance.new("Highlight", workspace)
anotherHighlight.Enabled = false
highlight.Adornee = part

for some strange reason this doesn’t work in studio but on roblox player it does.

1 Like
#2

this might just be a bug and not a scripting relates thing

#3

I don’t think parts can have two highlight adornments at all. It’s the same as with two welds and one part. If 2 welds connected to 1 part only 1 weld will be used.

#4

the other highlight is not enabled

#5

A fun thing that Roblox doesn’t consider is whether any of them are disabled or not. Only one will be used. If you want to change highlights just destroy one

#6

very strange, this had worked for me in the past.

#7

It never worked. Maybe it had to do with the order you created and adorned with highlights.

#9

join this game from roblox and play this game from studio and tell me if you see a difference

#10

I tested this and found that Roblox disregards whether or not the highlight is enabled. The highlight that is considered is ALWAYS the one that was most recently created.

Here is a script that tests this:

-- Init --
local part = Instance.new("Part", workspace)
part.Anchored = true

-- Testing --
local currentHighlightCount = 0

workspace.ChildAdded:Connect(function(child)
	if child:IsA("Highlight") then
		currentHighlightCount += 1
		child.Name = `HighlightInstance#{currentHighlightCount}`
	end
end)

for index = 1, 15 do
	local randomHighlight = Instance.new("Highlight", workspace)
	randomHighlight.Enabled = index % 2 == 0 -- Every other highlight generated will be enabled
	randomHighlight.Adornee = part
end

This generates 15 highlights, and every-other one is enabled. Below is a GIF showing what I mean by “the most recent” one being the dominant. They are numbered in order of being loaded.


In your case, the order in which the highlights are loaded into workspace can be different based on server frame times. Make sure you intentionally use a minimal number of highlights to avoid this issue!

Hope this helps! If so, feel free to mark this as a solution :grin::+1:

cc: @towerscripter1386

1 Like
#11

I think this is a bug in roblox for several reasons.

  1. It worked in the past.
  2. There’s no reason it shouldn’t work because the Adornee property is what matters
    and if its nil then it defaults to the highlight’s parent.
    It’s simple to demonstrate, just change my example and set the parent of the highlight to an empty folder.
local part = Instance.new("Part", workspace)
part.Anchored = true

local folder = Instance.new("Folder", workspace)

local highlight = Instance.new("Highlight", workspace)
local anotherHighlight = Instance.new("Highlight", folder)
anotherHighlight.Enabled = false
highlight.Adornee = part
  1. If you join this game from roblox(website) you will see the highlight is visible but if you play this game in studio you wont seee the highlight.
    highlight are borken - Roblox

Sadly I don’t have permissions to post in the Studio Bugs tag.

#12

This is not true, it’s likely that you happened to have it work correctly by accident. I tested this before highlights were released and it has always been buggy. This isn’t a bug in Roblox, but rather really unintuitive design on the engineering side.

I explained why this happens in my reply:

Or, in other words, the engine server-loading frame times can be different from Studio.

1 Like
#13

I’m using a local script to load them, so server frames are irrelevant. anyway the solution I found doesn’t fix the bug but it works for me.
I just put each highlight in a different folder.
Screenshot 2023-05-13 213210-t

#14

Then in that case, it’s client frames.

1 Like