The remote i try to fire that isn’t reconised
The declaration:
It indeed does exist in ReplicatedStorage:
System Information:
Windows 11 Pro 24h2
Beta Features:
New luau solver
Assistant Preview
The issue mostly happen when trying to script code in local scripts
First of all, why use :WaitForChild() on the object that wont be moved durning runtime, you can just declare a clean path like ReplicatedStorage.RemoteEvents.ShowPickCar
That way, your intellisense will work perfectly.
Alternative solution.
You could put : RemoteEvent type declaration after the variable name, so the Luau Solver will know for what type of object you are looking for.
Third solution:
use :: RemoteEvent type casting after :WaitForChild() method, it will work the same as Image above
1 Like
The old luau solver didn’t need a declaration to know it was availlable its why i’m reporting this issue
1 Like
Strange, it never worked that way for me.
It always silenced the Intellisense with :WaitForChild() as long as I can remember
1 Like
Also look at this following:
1 Like
Works fine for me
1 Like
use --!strict at the top of the script
1 Like
¯ \ _ (ツ) _ / ¯
1 Like
What error supposed to be here?
the do and end after the function, there is no for or while.
can you close the script and open it again?
Its shouldnt error…
the following syntax was always intented:
-- global scope
do
-- Inner scope
local function test()
print("inside the scope!")
end
end
test() -- Will error, because out of the scopeFine i guess this count as an error then
nvm, it happens only with the Beta feature enabled.
I could see now
but it fixes with just a simple edit
So its still intented use.
Roblox thinks that LocalPlayer “might” retrurn nil (it just doesnt account the side on which script is running)
so its still up to be an issue if dont use the or variable
Even this is gettings incorrect warning.
No its not the issue at all.
Its still intended feature, as Luau expects you to use :WaitForChild() for non nil instances
this one errors, because the variable gerrorm might be nil, and you cant concat the strings with nil
its says on the pcall documentation, that the first results is always returns boolean while the second and next ones, its either error or the function returns.
So its still not a bug