(Add ViGrey's NES RAM initialiser) |
(Link to installed extension list) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | |||
[[Category:Projects_and_infrastructure]] | |||
{{about|software used by (or made for) the console verification subcommunity|emulators used to make TASes|{{TASVideos|/EmulatorResources}}}} | {{about|software used by (or made for) the console verification subcommunity|emulators used to make TASes|{{TASVideos|/EmulatorResources}}}} | ||
| Line 4: | Line 6: | ||
For the most common use case of having commissioned a replay device from someone and getting it set up, the best would be {{TASVideos|/ConsoleVerification/Guide|this page on the TASVideos wiki}}, though it only hosts some of the code itself. | For the most common use case of having commissioned a replay device from someone and getting it set up, the best would be {{TASVideos|/ConsoleVerification/Guide|this page on the TASVideos wiki}}, though it only hosts some of the code itself. | ||
Also listed here is infrastructure used by Team TASBot, software that powers TASBot('s eyes), and design documents for TASBot and some replay devices. | Also listed here is [[:Category:Projects_and_infrastructure|infrastructure used by Team TASBot]], software that powers TASBot('s eyes), and design documents for TASBot and some replay devices. | ||
=== GitLab === | === GitLab === | ||
| Line 38: | Line 40: | ||
=== other === | === other === | ||
This wiki! [[Special:Version]] lists what's installed. | |||
https://vigrey.com/git/nes-ram-to-fceux/file/README.txt.html | https://vigrey.com/git/nes-ram-to-fceux/file/README.txt.html | ||
Latest revision as of 21:12, 23 November 2024
There is unfortunately no centralised source for verification/replay software, which is perhaps unsurprising given the diversity of replay devices and the lack of standardisation in the retro gaming space. For the most common use case of having commissioned a replay device from someone and getting it set up, the best would be this page on the TASVideos wiki, though it only hosts some of the code itself.
Also listed here is infrastructure used by Team TASBot, software that powers TASBot('s eyes), and design documents for TASBot and some replay devices.
GitLab
There is a TASBot org on GitLab. Its subprojects include:
- Source code for runs.tas.bot and for the previous iteration of tas.bot.
- Some of the designs and software for TASBot-X.
- A Nix package set of testroms and homebrew games.
(There is also a ToolAssist org, that is, under the name of the non-profit. )
Yoshi set up a bot account and cron jobs for the TASBot and TASEmulators GitLab orgs which you are welcome to use.
Additionally, Yoshi made the first steps on a Nix Flake for everything mentioned on this page—at time of writing it still only has 1 package.
GitHub
There is an org for TASBot, L3C on GitHub, but it's only being used for planning event appearances. TASBot IP/design stuff is all on GitLab.
There is an older TASToys org, which is mostly software for dwango's Twitch stream.
dwango and MediaMagnet are maintaining a set of dump scripts and dumps. (These are being rehomed on the previously mentioned TASVideos page.)
Owna is maintaining designs and software for the TAStm32.
Bigbass is developing designs and software for a new RP2040-based device called VeriTAS.
micro500 was maintaining designs and software for the TASLink, but it's now archived (also see Owna's fork).
Trello
Fream's TASBot branding and design work is in this Trello board. This includes some assets specifically for dwango's Twitch stream and some for wider use.
other
This wiki! Special:Version lists what's installed.
https://vigrey.com/git/nes-ram-to-fceux/file/README.txt.html