Enum.KeyCode.Slash does not exist or function

[LordMerc (Merc)]

Reproduction Steps

Experiencing a recent bug ( i do not know when this patch was released ) that my chat system no longer responds to ContextActionService binding the Slash Enum.

function Listeners()
	print('ok go')
	local function startChat(actionName, inputState, inputObject)
		print(inputState, inputObject)
		if inputState == Enum.UserInputState.Begin then
			print('test?')
			task.wait()
			ChatBar:CaptureFocus()
		end
	end
	ContextActionService:BindAction("Start Chat", startChat, false, Enum.KeyCode.Slash)
end

The code above does not function, however the below does

function Listeners()
	print('ok go')
	local function startChat(actionName, inputState, inputObject)
		print(inputState, inputObject)
		if inputState == Enum.UserInputState.Begin then
			print('test?')
			task.wait()
			ChatBar:CaptureFocus()
		end
	end
	ContextActionService:BindAction("Start Chat", startChat, false, Enum.KeyCode.Semicolon)
end

The slash also does not appear on the intellisense

Expected Behavior

I expect it to function as normal, when slash is hit it registers.

Actual Behavior

Does not register nor print, and does not show the slash on the intellisense example.

Workaround

I do not, have to use another KeyCode I do not want to use.

Issue Area: Studio
Issue Type: Other
Impact: Very High
Frequency: Very Rarely
Date First Experienced: 2022-12-14 00:12:00 (-05:00)
Date Last Experienced: 2022-12-15 00:12:00 (-05:00)

[julianhak06]

Yeah man. I’ve seen this issue before too and it’s really troubling, especially for custom chat systems that rely on the keybinds users know and love. I hope ROBLOX addresses this soon.

[LordMerc (Merc)]

Issue is still persisting and there has been no help. It appears ContextActionService itself is broken.

[julianhak06]

Thanks, man. That’s pretty sad to hear. I hope this fixes soon as it is troublesome, man.

[thirdtakeonit]

Thanks for the report! We’ll follow up when we have an update for you.

[LordMerc (Merc)]

Much appreciated, thank you! This has been an annoying bug!