I'd like to announce that I am opening a Discord server for Transgender and Nonbinary TASers called the Trans/NB Assisted Superplayers! This is a place for trans and nonbinary tasers to interact and support each other. We also would like to host events and such as well! This is not a space restricted to TASVideos members by any means, so any trans/nb TASers are free to join! To access it simply fill out the application form. Social media updates can be found on our Bluesky: @tnbas.bsky.social. Plans are already underway to collaborate with Really Really Long A Thon and Frame Fatales for a marathon event taking place August 28th through September 1st 2026 where trans and nonbinary TASers are encouraged to submit! More information can be found in the discord. For those who might be worried, no I am not leaving TASVideos or anything, nor should this impact my duties in any way. I simply want to do more for TASing at large and give back to the trans and nonbinary individuals who contribute so much to our communities.

Well, it was a matter of time. As of a couple days ago, our submission form officially allows the submitter to report an alternate timing method or optimization metric, such as in-game time or score! You can now see titles like #1312: ikuyo's PC Sayonara Wild Hearts "maximum score" (2,116,350) in 48:23.136 or #4444: (a lot of author)'s N64 Super Mario 64 "120 stars" in 1:14:04.444 (Console Timing) Here's also an example of this information in the submission queue (image sourced from a development build of the site) While we have officially allowed TASers to use whatever metric they want as an optimization target, this decision was not reflected in the way we display submissions and publications on the site, most notably in publication titles and YouTube encode titles. This has been a historical source of confusion, leading to several communities assuming we don't support in-game timers at all, or even causing casual audiences to assume TASes are slower than their real time counterparts. You will find both a drop-down to select the metric or timing used in the movie, and a field to type how it should be displayed. This information will be used to fill the title data for the movie wherever needed. If you plan to use this feature, we recommend you explain to us how to calculate or measure the reported metric if it is not obviously apparent, such as when using real time speedrun metrics. This will make it easier for judges or anyone unfamiliar with the game's speedruns to know what to look for. By the way, if you have or know of a publication that you would like to use an alternate timing method, we have opened a thread for Publication timing/score update requests, as it can only be changed by people with editing permissions. Keep in mind that this could take us a while, as we are as usual working on a lot of things. Also, this feature is likely to get further revisions and changes in the future, as we find more cases that could use it. Thanks for your patience, and happy TASing!

TASVideos has been quite busy lately, as you may know. And thus, we may need some more hands and voices to help us handle our work. We are always looking for people willing to help us, but until today the way to approach us and volunteer was rather informal. And we are here to fix it: this is the new official TASVideos Volunteer Application form! If you want to do wiki editing, reviewing, encoding, or any other form of volunteer work for the site, fill this form and we will get to you in due time. Thank you a lot! The site and our community appreciate your contributions. Apply here! https://forms.gle/Ly8fXyVtRpwUBn1t7. If you would like further details on how to help the site, please read https://tasvideos.org/Helping

We have finally overhauled our requirements page for accepting new TAS frameworks. The page was previously written with primarily emulators in mind, but the page is now written to be friendly to single game tools such as CelesteTAS and GZ, the Ocarina of Time Practice ROM as well as large scope frameworks that are not emulators by definition such as libTAS. As TASers adapt new and creative ways of TASing games, we must keep up and accept these sorts of tools as well. If you are interested in us accepting any sort of TASing framework, please reach out to an administrator or an administrator assistant. Also worth noting that these requirements are by no means final. If you have concerns that a framework you're using does not pass the requirements listed, we would be happy to discuss and negotiate. There is also discussion in Thread #22894: Potential support for single game/series/engine tasing tools.