LogService
is client-sided, and required modules show up in the server output, so no.
This was considered.
Our evaluation was that the method doesn’t add any additional attack surface that wasn’t there already.
-
You can already spam the output with a bunch of newlines and other junk to effectively hide something.
-
The malicious code can wait until it detects inactivity from the user to do its malicious work when the user isn’t looking so the output shouldn’t be the last line of defence regardless.
RE: PlaybackRegions
There will be an announcement. This feature broke multiple times in the past when we tried to enable it so we’re just giving some time to make sure it didn’t break something again before putting up the announcement.
But will there be any way to view sound waves so we can put the region on the right place??? This looks unfinished to me as the only way to set “Begin” and “End” is changing values only and that doesn’t guarantee if the sound is perfectly looped.
also wasn’t it supposed to be a beta features or was it accidental releases??
LoopRegion is not intended to be a full solution for more powerful audio sequencing.
It’s just intended to make working with audio easier by allowing minor adjustments to things where you would have had to re-import the asset before. It also allows you to more easily work with existing licensed audio in the catalog which you can’t re-import at all.
Mean this that you van reload the plugins and not have remove the GUI from plugin where you work on from core GUI will update lokaal plugin
It is explained here, in an earlier post, why some improvements have odd titles.
Read this. My previous post was unfortunately moderated.
I am so happy this is finally a feature, I used to have to manually reload the plugin after changing something and was very annoying to the workflow.
Ah that’s my bad. I’ve never experienced this issue using a non apple mouse on my mac, so I didn’t know that was a thing.
Amazing work! I work extensively with Rojo plugins in Rojo places and it’s so nice to do something like
$ rojo build plugin.project.json --output ~/Documents/Roblox/Plugins/plugin.rbxm --watch
and see it update in Studio. Goodbye my friend, no more clicking you 100 times per day.
I see absolutely no use in this functionally. You can right click the output and clear it. Using programming to do this has effectively no purpose. The only thing that I can genuinely see is malicious use.
I believe the intended use is to allow for plugins to have more access to output features. Maybe you want to make your own custom plugin that clears the output and prints some debug info.
It doesn’t have any use for most users but some advanced users wish to use this in semi-automated tooling workflows for testing / rapid-prototyping purposes.
Imagine for instance you’re trying to debug a specific scenario in your game and you want to clear the output right before that scenario occurs so it’s easy to see exactly the output lines you’re interested in. Having a command available to do something like that can come in handy surprisingly often.
It is an API with a non-zero amount of risk for sure… that’s why it hadn’t been added yet.
When I want to run a script in the command line that will print something, I have to add a wait so I have time to clear the output. Remember, the script I ran is printed in the output before it runs, which can fill up a lot of space and could make it look cluttered. With LogService:ClearOutput()
, I don’t need to add a wait and I don’t need to clear it myself. Automation.
I know it may sound stupid, but what exactly is PlaybackRegion?
I couldn’t find anything about it in Docs, is it a region sound plays in?
Thanks, and I apologize again if it sounds a bit goofy.
Why I don’t have this updates I have today worked on my plugin and can’t reload it
Do you see the “Reload plugins on file changed” setting in the Studio settings or not and what value does it have?
I didn’t even realize this was in the release notes, but this has indeed been a bother for a long time now.