You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new studio output window features that print({ value = 1 }) is visualised, instead of being outputted as table: hex ID. However, run-in-roblox does not detect this at all, acting as if nothing was printed.
This also applies to print(Instance.new("TextLabel"))
The text was updated successfully, but these errors were encountered:
Ah, that's rough. Does this happen with the in-game dev console as well?
If you look at the code that run-in-roblox uses to catch logs, you can see that we use LogService. I don't know if there's another way to capture logs that would pick this up. It sounds like a Roblox bug! :(
The in-game dev console (F9) just prints the old table: hex ID. It's specific behaviour of print in studio. This function exists. Maybe that returns the original output? Although I wouldn't really count on it, but it's worth a shot.
The new studio output window features that
print({ value = 1 })
is visualised, instead of being outputted astable: hex ID
. However, run-in-roblox does not detect this at all, acting as if nothing was printed.This also applies to
print(Instance.new("TextLabel"))
The text was updated successfully, but these errors were encountered: