Yes, we need more power, us scripters, really greedy.
Anyway, you've given us little control over the CoreGui, I mean sure we can remove specific aspects and bring them back, but what does that mean? Little control.
In a LocalScript the main thing we can do
game:GetService("StarterGui"):SetCoreGuiEnabled("PlayerList", false) --There's also the Health, Backpack, Chat, and All, but that's it!
We cannot add or modify things like that. Only can we add stuff to CoreGui is when we're in studio, only to make it active, after which it doesn't show in online!
Wow, you've given us so much huh? But what if we wanted to change our the chat or leaderboard looked. Okay, let's go through the trouble of disabling and creating stuff from scratch... Alright so first we make a gui... then we do that...
BUT WAIT!
There's a better way!
I propose a new way for CoreGui to work. The idea is that all the above guis can be put into game:GetService("CoreGui") and that CoreGui (I think it already is) would be local to each client.
SetCoreGuiEnabled and GetCoreGuiEnabled would be added into CoreGui and not StarterGui in this new update (but would stay deprecated in StarterGui as to not break anything)
Then the client (LocalScripts) would be able to add/take away from CoreGui, or modify the guis inside CoreGui.
This would give scripters A LOT more power over what CoreGui stuff happens in their game, and will make a custom leaderboard or a custom chat which still takes input with the chat bar, so much easier.
Support if you agree, no support if you do not.
Lemme start us off support:no_support
1:0 |