Advertisement
trihex

srb_updates (2015/08/04)

Sep 2nd, 2015
2,365
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 12.38 KB | None | 0 0
  1. ▤▤▤ FOREWORD:
  2.  
  3. Apologies to my use of vocabulary in SRB presentation. I understandably upset many with use of "asshole" and "autistic" to sarcastically refer to specific forms of elitism I feel are present.
  4.  
  5. I severely underestimated my reach/position in speedrunning. I mean this with utmost humbleness, I honestly didn't expect 1k viewers or anything near it (much less 2.7k at peak) since many guessed the reveal was going to be me picking up a new game (lol).
  6.  
  7. Going forward, I'll refrain from using such language when discussing formalities involving SRB & actually be a better face for the community.
  8.  
  9. When revealing what I disliked about speedrunning, I am not making SRB to "attack" those things -- more to reveal my motivation for being excited to do this. This is an extremely collaborative thing alongisde some other like-minded speedrunners who share ideals in the concept, not necessarily my viewpoints exactly.
  10.  
  11. I'd also like to emphasize I don't have any ambition to "monopolize speedrun content". Sure, expansion would be cool if my Yoshi tuts are good and working, but this is why I want to do my thing first. Set the tempo, become familiar in the production process first, and be able to help in all steps of production. The attempt of branding it as "SRB" rather than "trihex's Yoshi tuts" is skipping the step of rebranding all my work if it does pick up traffic with more eager collaborative participants in the future, nothing more.
  12.  
  13. ▤▤▤ SRB changes to announce:
  14. • Controller Cam will become Input Display
  15. • Scripts for upcoming levels to be revealed soon (next week or so)
  16. • SRB production process revealed entirely (check accompanying tweet)
  17.  
  18. ▤▤▤ SRB content spec for each game:
  19. Each game category covered would receive 3 large chunks of content in coverage. It gets a bit lengthy, but each content chuck is marked with a bullet point (•); if that entitles a list, each item accompanied with a dash (-); and if each item within that is accomplishing multiple things, they're marked with em dashes (——).
  20.  
  21.  
  22. • [game] Speedrun Tech playlist
  23. - Every speedrun-exclusive technique covered in an independent brief video (30sec to 5min depending on complexity of tech) on its own playlist for fast digestion for those not interested in thorough explanation alongside a full run, or for those not interested in searching thru chapters of videos for a specific tech elaboration.
  24.  
  25. EXAMPLES, using Yoshi's Island (with approximate running times):
  26. - Perfect Flutter (2min)
  27. - Red Coin Dupe (4min)
  28. - Double Dupe (2min)
  29. - Camera Manipulation (3min)
  30. - Bonus Skipping (5min)
  31. - Egg Shuffling (1min)
  32.  
  33.  
  34. • [game] [category] Speedrun SRB Playlist
  35. - A full speedrun of the category in the game, segmented into satisfying, independent 10min-length videos. All containing post-run commentary with an approved, collaborative script; tech timeline w/ tech icons; display input; and re-created relevant HUD to help visualize anything that can be shown accompanying goals or things getting done in the speedrun.
  36.  
  37. EXAMPLES, of relevant HUDs that could be used in SRB:
  38. - Realtime Star/Flower/Coin HUD in Yoshi 100%
  39. - Badge/Item/Partner HUD w/ English if using J-copy in Paper Mario: TTYD
  40. - Showing the spec complete upgrade path for HP/FP/BP when leveling up in TTYD (HP 1st, then FP, then BP a ton of times, then FP again later, etc.)
  41. - Showing score milestones throughout levels in StarFox 64 that ensure a self-check system (safety numbers) of taking the appropriate path during a speedrun
  42. - Showing spec menu navigation route in entirety in English alongside game-feed of diving into tons of menus in optimized shop navigating in RPG's like Japanese SMRPG or Pokemon speedruns
  43.  
  44. • "Welcome to [game][category] speedrunning" video (no video length cap)
  45. COVERS:
  46. - Encourage the viewer to legitimately play the game start-to-finish at least once (ensure they enjoy it) before starting tuts
  47. - What you can expect to learn watching SRB's videos specifically (in effort to empower the viewer/encourage participation)
  48. - Developer-intended gameplay mechanics in high-skill manner (all non-speedrun-exclusive tech, i.e. the basics)
  49. - Spec for the speedrun category (what region version used & why; any rules/obligations of this category & exceptions, if any)
  50.  
  51. OPTIONAL IN "Welcome to [game][category] speedrunning" VIDEO:
  52. - Goals of full [category] runs once tuts completed (better than an invisible, unspoken conversation of the new runner comparing to WR regardless):
  53. —— Newcomer Goal* (a time realistic within 1st run attempt after practicing all things covered in tut)
  54. —— Starter Goal (a time realistic within 6 months of playing regularly; based on race data and other newer runners in the community)
  55. —— State then-current WR time, emphasizing how many of the techniques (both vanilla and speed tech) are employed and used skillfully in a list format alongside (to help build confidence in visualizing what a new runner's speedrun isn't incorporating to justify being nowhere near WR at the beginning)
  56.  
  57. *Newcomer Goal = temporary name. Open to a better, possibly less condescending-implied title for this goal.
  58.  
  59. ▤▤▤ SRB spec:
  60. • each video be 10min or less (for digestible, modern YT meta); playlist utilized extensively
  61. • use video editing as helpful informational tools to what's happening on-screen and make all information easy to understand
  62. • show a complete run, interrupted with when-relevant information, with post-recorded commentary the entire time
  63.  
  64. ▤▤▤ SRB questions/answers:
  65.  
  66. Q: Will SRB be open to others contributing/helping?
  67. A: Yes. Ideally, things go well for Yoshi and some point after AGDQ 2016 we can move forward with doing doing other games (braintrust members are already working on theirs'). I chose to not elaborate because I felt worrying too far in advance is celebrating early. Understandably, I have much criticism at the ambition of what I'm aiming for.
  68.  
  69. In short, yes, eventually any one interested can submit to do SRB treatment for any game later in 2016.
  70.  
  71.  
  72. Q: Are you open to criticism/change to be better and more constructive?
  73. A: Yes, I read everything tossed at me. And will reply to all I can. You reach me via:
  74.  
  75. - tweeting me w/ any idea/concern/criticism (twitter DM me if it's lengthy)
  76. - asking on ask.fm (annonymously, if want) w/ hashtag SRB (#SRB)
  77.  
  78. I don't prefer Twitch PM because it's slow and awful to manage.
  79.  
  80.  
  81. Q: Will there be a portal for SRB content in the future?
  82. A: Yes, I plan on using my own YouTube channel for the source of content, and if it succeeds, I will make a SRB youtube and twitter channel as a main portal for expansion content (and also re-uplaod my stuff there). I will use all available resources (10k youtube subs, 21k twitter) to minimize failing due to no-reach compared to starting new portals immediately.
  83.  
  84. If things meet Phase 2 w/ Expansion in 2016, I'd exercise the brand and create a website portal and specific twitter for SRB updates.
  85.  
  86.  
  87. Q: This would be great to attach to existing portals (speedrun.com)! Are you gonna do that?
  88. A: I have connections w/ speedrun.com, but I'd like to prove that this is a solid idea before bothering them or anyone else.
  89.  
  90.  
  91. Q: Who will do all the tutorials for other games after Yoshi is done, hypothetically?
  92. A: As much automation as possible will hopefully be achieved in the future. For now, I would help eager runners with editing duty after they have completed scripts & recording. Eventually recruiting assistant video editors if I can somehow pay them.
  93.  
  94. Honestly, I haven't given thought to the logistics of this phase (since it's so far in the future), but I assume there will be helpful hands if I do my part well beforehand.
  95.  
  96.  
  97. Q: Are you going to cover how to route/how to practice?
  98. A: No. Those would require separate video series to cover to the extent they'd need to be done well. Both are aspects tied to all games, not a specific series. This -could- be a thing in the future, but I'd need much more collaboration and support then I have now.
  99.  
  100. SRB is taking the existing resources and applying/displaying them in entertainingly informative videos as a starting point for those interested in speedrunning.
  101.  
  102.  
  103. Q: But your logo references Discovery/Glitch Hunting & Routing. Why mention those things if this tutorial series isn't covering either one explicitly?
  104. A: That's my fault as an oversight in presenting everything originally. I liked the idea in relation to splits and speedrunning, but technically, yes, those aspects won't be present nor instructed here.
  105.  
  106.  
  107. Q: If you're gonna take a year to finish Yoshi 100% tutorials, how will you address if the runs become obsolete or route changes midway?
  108. A: I commit to demonstrating everything known at start of production. I wouldn't change what to show to reflect sudden updates in-production.
  109.  
  110. Understandably, the speed of production is what everyone is upset by with this circumstance. I can't promise a faster time without neglecting streaming (my income) to a damaging degree, so there's compromise in that regard.
  111.  
  112.  
  113. Q: How will you address changes to route displayed after tuts are finished?
  114. A: I expect some things to be outdated by completion or as soon as released. I'm okay with that as the dated videos will serve as a documentation capsule of "August 2015 Yoshi routing". I can add videos later specifically covering how the routes changed for "Q4 2016" if applicable. (I'd later change the outdated videos to "Q3 2015" strats)
  115.  
  116. I envision being able to see Logistics for how to manage/label that aren't ironed out yet, but I'm aware of this situation.
  117.  
  118. ▤▤▤ Accusations/Criticisms:
  119.  
  120. 1) By not allowing others to contribute immediately, you're "part of the problem" by being elists and displaying favoritism in whom is in braintrust/backroom
  121. ▤ If I opened SRB to anyone I feel the quality and control would deteriorate as not everyone sees the level of quality I envision for the project. If I opened it immediately, I'd have to formalize a submission process and reject many due to not enough polish in their scripts. To not be needlessly negative, I feel it's better to show my product/idea before opening up. I absolutely want to open SRB to all, once everyone is on-board with me having won them over with trust in my execution.
  122.  
  123. For now, I'll endure the criticism until I've done my part.
  124.  
  125.  
  126. 2) SRB = overdramatic hype for Yoshi tutorials
  127. ▤ I wanted to show the full context of why I was so excited to do this project. It went beyond just thinking it's a solid idea (speedrun tutorials), and more about conditions present in the community that can be addressed -- tuts being the 1st of many I'd like to do.
  128.  
  129. The lengthy presentation was needed to cover all of that. I under-estimated how much attention that would gather and questionably under-prepared for such a mass reception (I'd definitely have edited it shorter, if so). But for anyone's convenience, I uploaded different edits for those not interested in the full context:
  130.  
  131. • (78min) full presentation -- https://www.youtube.com/playlist?list=PLf05t022RiHGbY9QxpACPqPEO753pyIQ_
  132. • (35min) concept reveal & rough cut demo only -- https://www.youtube.com/playlist?list=PLf05t022RiHGyiKE_BV849TgNYBYrfhYQ
  133. • (10min) concept reveal only -- https://www.youtube.com/watch?v=VUQn1U70ERc
  134.  
  135.  
  136. 3) SRB's presentation overcomplicated the speedrun process
  137. ▤ I covered the speedrun process as I see it mostly as relevant to the logo design itself. I don't plan to explore the process in the series, more to utilize/display the known resources in quick/digestible form for anyone.
  138.  
  139.  
  140. 4) Commentated runs are what grab attention of those not interested; not tutorials which target those already interested
  141. ▤ The structure of SRB ideally is that it's a run, but rather than GDQ during-commentary, it'd have higher quality post-commentary enhanced with complimenting what's happening on-screen rather than pre-buffering an event to-happen -- but even better with tons of video editing involved to make everything even easier to follow, information-wise.
  142.  
  143. Though I understand the appeal of watching a WR run by comparison, but I still feel speedrunning has grown to the point of that situation alone not being enough to kill this concept out of existence for competition in traffic.
  144.  
  145. ▤▤▤ Things to reveal later (next week-ish)
  146. - Yoshi tutorial process (what order to show route options, back-up strats, etc.)
  147. - Sample scripts completed so far (1-1, Welcome to Yoshi, 1-2, etc.)
  148. - Updated WIPs on Graphic Presentation
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement