Ever wanted to share live progress of your game’s development to your audience or keep track of what’s going on within your game?
With just two commands you can start live-logging your progress into Discord automatically! Let your players know what updates and changes are being made to your game live.
You can install the plugin from here.
Once you have it installed, type in your Command Bar
_G.RoLink.Help() to get started. It’ll give you instructions on how to set up your Webhook. Once you have a linked Webhook, you can just enable it and it’ll start functioning.
The following are the events that the Plugin will replicate and the conditions for them to occur.
Script Create: Fires when a LuaSourceContainer instance is created.
Script Delete: Fires when a LuaSourceContainer instance is deleted.
Script Name Change: Fires when a LuaSourceContainer instance name is modified.
Script Source Update: Fires when a LuaSourceContainer hasn’t been editted for the Update Rate period (configurable) or if there were more than 500 actions related to that script (typing, deleting, etc.)
The Plugin does NOT cache your scripts at all, it just keeps track of the amount of times you’ve changed the source, not the source itself.
Q: I’ve made a change but it hasn’t logged it.
A: Logging isn’t instantaneous, especially if you’re expecting a source update log. All logs, except source updates, can take up to 10 seconds to be shown in the webhook.
Q: Does the Plugin rate limit webhook requests?
A: Yes, there’s a built in rate limit, the Plugin will not make any more than 60 requests per minute.
Q: Can multiple people use this plugin in the same Team Create session?
A: Yes, the Plugin works with a Queue for requests and will not send any duplicate requests.
Q: Can multiple people use a different webhook inside of the same Team Create session?
A: Currently not, but I’ll be working on a fix for that.
Q: Can I download the source to check it out?
A: Yes, of course! I’m planning on opening a Github repository so we can improve the code further, currently I’d say it’s a bit messy.
Q: Are you planning to create a visual menu for this Plugin instead of command line?
A: Yes, I’ll be making a visual menu as well for the plugin, but due to its simplicity I’ll stick with the command line for now.
This plugin is in Beta, expect bugs and please report them in comments. I’ll read them and make any changes necessary.