Why doesn’t runservice appear in studio’s object browser…?
Edit: Oops you just said that in your reply post. Without it being in the original post I can understand einsteink’s post
1 Like
Why should it be there? You only have to remember “RunService” ?
There’s a ton of services not shown there. Way more than we do show. The ones with properties, or intended to be used as storage, are shown. Why would RunService be an exception?
1 Like
Maybe a simpler solution for this would be if it was still not displayed, but still appeared on the intellisense as a child of game?
EDIT: Ignore this. 
Those services should be displayed in the Object Browser as well. The Object Browser is a like an instant wiki that you don’t have to browse to or wait for pages to load – you know the name of what you’re using and then you’re presented with all of the things you can do with it. Just because they’re services instead of creatable objects doesn’t mean the Object Browser is magically not useful for them. Service events and methods can be just as easily forgotten as events, methods, and properties of creatable objects.
print(game.Run -- Already shows RunService
1 Like
Funny enough, there are some studio settings that could do this:
Of course they appear to do nothing that I notice…
All instances that have any use should be shown. RunService contains the Step methods and it would be extremely useful if we did not have to open the wiki to remember the exact name. This is the same for other instances too such as GuiService.
Anything that we have a real use for should be shown.
If you really use RunService that much, you should be able to remember its name.
You can always add bookmarks on your browser for the services you use.
Yes, and he does. The Object Browser is not for finding service names – it’s for looking up event/property/method names for objects you already know the name of. RunService fits this bill just as much as any creatable object.
The Object Browser is not for objects you use on a regular basis – if you use objects regularly you will have already committed their member events/etc to memory. It’s a quick lookup for things you don’t remember – in other words, uncommon objects/services that you wouldn’t have bookmarked.
Edit: Woops total misread.
The object browser should show RunService. There’s no reason not to. Why would we show some services and not others?
1 Like
Just add a searchmachine to your chrome omnibar:
If you call it “rowiki”, you can enter “rowiki RunService” to go to its page.
I should not need to open Chrome when the information is already available but not displayed.
1 Like
Looking it up in the Object Browser is quicker – that’s why it exists, and that’s what it’s for. Using the wiki, you need to switch programs and then load a webpage (or two if the search doesn’t redirect you to the exact page). The Object Browser provides all of this to you instantly without any webpage loading. The wiki is for explanation and examples of objects – the Object Browser just tells you which member events/etc an object has. The uses for the two are completely different.
Isn’t the Object Browser the built-in browser linked to the wiki?
No – it’s populated with information provided by ReflectionMetadata.xml. It doesn’t download anything and uses in-house data from that XML.
1 Like
Well there’s a built-in wiki browser, no?
As I mentioned previously, the wiki and the Object Browser serve two very separate needs. On top of that, the Context Help (built-in wiki widget) takes time to load the page just as your browser does. The wiki is not a replacement for the Object Browser.
Yes, but it is entirely separate.