Importing and Exporting Packages are the way to share projects that have been made with other members of the community, since 0.1.8 this has been updated to make it far easier with the addition of the ability to export commands too.
In the Top Left of Streamer.bot you will see an
Pressing that will bring up this dialogue box.
From here you can select one or more
Commands you would like to package for export.
After selecting the actions and commands for your package, give it a name and then choose one of the buttons below
Export to to Clipboard will copy a string of UUEncoded text to the clipboard and show a confirmation dialogue.
Export to File Will perform the same operation but automatically bring up a Save dialogue and create a file ready for transport
Exported actions will retain any custom JSON or C# code and will retain the sub-actions, group names and custom
Queues an action was associated with. When actions are re-imported, Streamerbot will attempt to rebuild connections with OBS objects that match but these sub-actions may require opening up to confirm they are pointing to te intended sources
Actions and Commands can be
Imported from other installations of Streamer.bot (providing they have been created on an equal or earlier version), allowing you to share your creations to different PCs or even to entirely different streamers.
To Import an action, open the
Import dialogue by pressing Import in the Top Left of Streamer.bot.
You can Import 2 ways either paste in the UUEncoded string for the package you want or drag and drop a file with that contains your import code into the top box.
If for some reason you are running streamer.bot with elevated permissions or in
Administratormode, you will be unable to use the drag-drop functionality, unless the Explorer window you are dragging from is also running in Administrator mode.
To work around this you can temporarily load the application in regular mode while importing actions
Streamer.bot will attempt to recreate as best it can the action exactly as exported, though if it includes paths to files you will need to adjust these to match your folder structure before they will work.
The lower half of the window will then populate with a preview of all the actions found in that package.
You can select any of the actions you want to bring in, if any have an identical name to an action already in your library it will rename the incoming action(s)
If you see no actions or commands populate when you copy and paste the code ensure that they are no trailing spaces or a new line at the end of the string.
The above example creates 2 Actions and 2 commands, you can use the checkmark to choose which Actions or Commands you wish to Import.