Implement schemes

[Anaminus]

Umbrella issue for future schemes to be implemented.

• [ ] rbxasset
• [x] rbxassetid
• [ ] studio

[Anaminus]

rbxasset

Points to the content folder of current roblox studio installation.

• Input/Output
• Useful for prototyping assets in studio.
• Requires method to locate studio installation.

[Anaminus]

rbxassetid

Points to an asset on the Roblox website.

• Input/Output
• Requires authorization
  • Specify by command option or configure, or both?
• Input downloads the asset.
• Output uses /Data/Upload.ashx to update the asset.
  • How to specify metadata?
  • Updating metadata seems out of scope.
  • Creating assets in general also seems out of scope.
  • Should probably be complemented with a separate tool that interacts with the website (repurpose rbxweb?).
• Probably worth using a separate, dedicated package for up/downloading.
• Get
  • GET https://www.roblox.com/asset?id=<id>
• Create
  • POST https://www.roblox.com/ide/publish/uploadnewasset?assetTypeName=<type>&name=<name>&description=<description>&isPublic=True&genreTypeId=1&allowComments=True
• Update
  • POST https://www.roblox.com/Data/Upload.ashx?assetid=<id>
  • POST https://www.roblox.com/ide/publish/uploadexistingasset?assetID=<id>

[Anaminus]

studio

Interacts with a live studio session.

• Input/Output
• Serializes and up/downloads relevant objects.
  • Needs a format. Roblox's packet format would be ideal.
• How to connect to one of multiple studio sessions?
• Interacting via Team Create sounds cool but insane and scary.
• HTTP
  • Use plugin and HttpService for studio side.
  • Use a local web server for rbxmk side.
  • Requires a serialization lib in both Lua and Go. Or Lua and gopher-lua, maybe.

[Anaminus]

Issue has been invalidated by v0.3.0 refactor.