“Internal: This object has been marked as internal. It currently serves no significant use to developers.”
Now that’s a load of baloney, everyone use this for debugging reasons.
Either that change is meant for the new developers who aren’t getting too advanced, it’s there as a “it technically is” kind of deal, or it’s a hint.
I hope it’s a hint.
Technically, it is internal, since ROBLOX exposed a better method of getting output with LogService.MessageOut.
3 Likes
Ah right!
That is a nice function but it lacks something very important:
It does not give you the script causing the error (if an error is shown).
Its not a bug, its intentional.
A majority of the ScriptContext functionality is internal, so I marked it as such.
If you can’t identify the source of an error you’re doing something wrong lol.
Though keeping in mind the point that you brought up, I decided to remove the internal tag.
http://wiki.roblox.com/index.php?title=API:Class/ScriptContext
1 Like
The stacktrace does…
and if you need the actual Script object, you can get it using the stacktrace’s “Workspace.Idk”
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.