{"id":52137,"date":"2023-04-04T21:17:19","date_gmt":"2023-04-04T21:17:19","guid":{"rendered":"https:\/\/barrycarlyon.co.uk\/wordpress\/?p=52137"},"modified":"2023-04-04T21:21:48","modified_gmt":"2023-04-04T21:21:48","slug":"the-twitch-extensions-developer-rig-is-dead","status":"publish","type":"post","link":"https:\/\/barrycarlyon.co.uk\/wordpress\/2023\/04\/04\/the-twitch-extensions-developer-rig-is-dead\/","title":{"rendered":"The Twitch Extensions Developer Rig is Dead"},"content":{"rendered":"\n

Or is it?<\/p>\n\n\n\n

Preamble<\/h2>\n\n\n\n

Twitch decided to deprecate the Extension Developer Rig, which is fine, just about everything that the rig could do is avialable via the API now. You can read about the Deprecation on the Developer Forums<\/a>.<\/p>\n\n\n\n

The final thing that was API enabled was bits product management, which for a while was rig only, but is now available in the API and more recently in the developer console, so if you don’t want to write or use a tool<\/a>, you can use the developer console<\/a> instead.<\/p>\n\n\n\n

You can read more about the Bits product management announcement over on the Twitch Developer Forums<\/a>.<\/p>\n\n\n\n

So What Now?<\/h2>\n\n\n\n

For those working with Twitch Extensions, you can either write you own tools to talk to various things via the API, such as the Config service<\/a> or Bits product management<\/a> or you can use a tool that someone else wrote such as my own Twitch Extension Tools<\/a>. But that leaves out the one thing that the Rig can do but nothing else can, which is view testing.<\/p>\n\n\n\n

View Testing<\/h2>\n\n\n\n

The optimal way, in my opinion, to do view testing is to get your Testing Base URI setup over SSL, either via using a real URL, or a reverse proxy tool such as NGROK.<\/p>\n\n\n\n

But there are times where you don’t want to do that or just want to quickly test a video or component slot extension without going live, which is where the Rig comes in, you can test those sort of extensions without going live, or even by putting the “wrong” channel behind you extension (listen to M<\/a>onstercat<\/a> whilst working on your extension for example….)<\/p>\n\n\n\n

The rig is still available for doing that sort of testing, but you may need to reimport\/reopen a project or refresh the projects manifest into the rig, or you have started a new Extension and need to test.<\/p>\n\n\n\n

That part of the rig is broken, you’ll hit the buttons and nothing will work as the API’s the Rig are trying to talk to just no longer work if they exist at all, to that end I devised a little tool to cover.<\/p>\n\n\n\n

The Manifester<\/h2>\n\n\n\n

Presenting the Twitch DeveloperRig Manifester<\/a> (not affiliated with Twitch naturally).<\/p>\n\n\n\n

\"\"<\/a>
A Screenshot of the Manifester. It’s ok the userID is mine I can leak my ID all I want mom!<\/figcaption><\/figure>\n\n\n\n

Which provides the following tools:<\/p>\n\n\n\n