After his failed takeover of Mario's castle in the previous game, Wario decides to go after a statue stolen by Captain Syrup. Armed with a new glitch, he finishes over two minutes faster than his previous attempt.
  • Heavily abuses glitches
  • Heavy luck manipulation
  • Uses fake death to save real time
  • Ending choice: fastest end-of-input
  • Contains speed-sanity tradeoffs

Emulator notes and timing differences

This run was started all the way back on Bizhawk 1.4.1 and should sync on any version up through 1.9.1 with unequal frame lengths. (This turned out not to be true due to issues with the sync settings, so this submission has a fixed bk2. It will sync now. ...hopefully.) However, at the time this run was finished, the most recent version was 1.8.4, which did not have the new TAStudio. So the actual TASing never went past 1.5.3. Use of TAStudio is also why the rerecord count is zero.
The previous run used an old version of VBA-rr, which uses a framerate of 60 instead of Bizhawk's ~59.7. There appears to be a lot of extra lag in this run, but most of this is VBA's fault. The display is disabled during room transitions and other parts of the game, and VBA counts this as 1 frame regardless of length.

Sprite lag and the sprite limit

Wario Land 1 will hold data for up to seven objects at once. However, the last two sprite slots are reserved for important items such as coins and what's in item boxes. Everything else is limited to the first five sprite slots. If all of those are full when the game tries to load another sprite, it won't load. Five is actually a pretty hard number to hit, and even when it's possible it typically requires a big coin to be taken out.
The game will not always process each object on each frame, and will not always start with the same one each time. To keep the game from lagging, any that haven't done anything near the end of the frame will not do anything on that frame. The sprite that would have moved next on the first frame will then be the first one to move on the next frame. This can be either a good thing or a bad thing depending on the situation. The amount of sprite lag is mostly unchangeable while jet dashing, but it can be controlled more while jumping (usually by pressing up on certain frames). The index of the sprite that will move first can also be changed by waiting a few frames before entering a door, provided there is enough time left on the eight frame rule.

The coin game

The RNG used for the coin game after each boss fight is based on cycles, making it very sensitive to tiny changes. The list of things that can change how it turns out is very long, and includes things like when Wario stops a jet dash (and for how long), which direction he faces, when the jet dash was started, which direction(s) he collects a coin from, which coin he collects when there's more than one on screen, what the index of the first sprite is, if... well, there's a lot.
The coins that appear can take the last two sprite slots, but letting that many coins on screen is a bad idea. For one thing, when all seven slots are filled the coin counter stops. It doesn't matter whether or not all 30 coins have already appeared; if there's nowhere to put a new coin, the game won't even check that. Even filling up six is too much because any big coin Wario takes out will take the seventh. Also, during a boss fight and coin game, the sprite lag feature is disabled, so letting that many sprites on screen will cause game lag.
Pressing select during gameplay actually sort of does something here. It's part of a hidden debug mode (seperate from the 16 selects when paused one) and changes the hat Wario is wearing. It's not active in this run, and in fact the activation method (press select 16 times on the "Course No. xx" screen) only does anything if it's already active. However, the check if it's active takes enough cycles to sometimes change the result on that frame. Sometimes it can even affect what happens several frames later.
The coin replacement technique to take out more than one at a time works like this: When trying to take out a big coin, the game checks every sprite slot in order until it either finds an empty one, one containing an already thrown coin, or goes through all of them. If it finds the empty slot first Wario will take out the coin. This means to do this multiple times Wario has to grab the small coins in reverse sprite order. Unfortunately each coin will take the lowest numbered slot availible, so in most cases he can only grab them in forward order.
Finally, throwing away a big coin on the ground will start a counter for how long before Wario can move again. This uses the same address as the counter for the end of level fadeout, and it isn't zeroed before that starts. This gives Wario an extra three frames to manipulate the coins while making the same frame rule.

Fake death

When Wario gets close to an instant death tile while jet dashing/diving and cancels it, the game will set him to the dying state and start the death sequence... and then immediately change it to the midair state. If a jet dash is started on the next frame, Wario will no longer be touching the tile and can continue the level. This will not work on the death zone at the bottom of the level or with an instant death object such as a pouncer.
When fake death is active, all sprites are frozen in the state they initially load in. They can be unfrozen by pausing and unpausing. The glitch also sets the level fadeout counter to 128, saving that many frames each time. This is the only thing fake death is used for in this run, as the autoscroll rooms in course 33 are completely skipped.

Screen wrap

When Wario jet dashes into a wall and is knocked backwards the camera will not move to follow him until the player regains control. This allows Wario to get closer to the edge of the screen than normally possible.
By not touching the ground for more than one frame and moving at the same speed as the camera (jet dashing or only moving every other frame), it will not be able to catch up to Wario. If the recoil is repeated enough times, Wario can go off the left side. At this point the camera will try to catch up by moving to the right. If Wario then moves far enough to the right that the camera reaches the part where it normally locks, it will be able to go past that point into the next room.
This game, like many, determines where each exit leads to using the camera position instead of Wario's. Using the screen wrap glitch therefore allows Wario to use a different exit, which can skip large parts of the game. This glitch is responsible for most of the improvements in this run.
Under most circumstances Wario will have to bash into five walls to go offscreen. If there's an enemy he can bounce off of it can be done with four, but otherwise the edge of the screen is just out of reach. The right side of the screen is much farther away and the screen doesn't like to scroll to the left, so going in that direction has no use in this run.
The goal while moving offscreen is usually to reach a specific spot in the level while moving the camera as quickly as possible. Slow jumps to the right and alternately walking left and right are the best ways to do this.

Frames saved

CourseFrames SavedExtra LagTotal
Title Screen-0+42+42
Course 02-48+68+20
Course 03-168+67-101
Course 04-80+66-14
Course 05-96+125+29
Course 20-176+67-109
Course 22-104+67-37
Course 25-168+85-83
Course 26-16+73+57
Course 27-48+72+24
Course 28/29-256+83-173
Course 30-792+114-678
Course 32-40+76+36
Course 33-2160+68-2092
Course 34-360+79-281
Course 35-1512+58-1454
Course 36-144+87-57
Course 37-24+67+43
Course 38-1904+104-1800
Course 39-336+91-245
Course 40-1031+43-988
Total-9463+1602-7861
  • Ending point for each lag count is on the map screen before the course is selected. Currently this only measures the difference in lag counts between emulators. The lag VBA doesn't count has not yet been counted, because I don't know how to do that.

Stage-by-stage comments

Course 2

  • The fading platforms in the first section need to be manipulated so a spearman lands on one for more bouncing. These will normally change every 32 frames, but just like sprite lag they'll stay put if there's too much going on.
  • There are two possible coin routes that take exactly the same amount of time. Getting the second coin from a spearman instead of a block is faster initially, but it's all lost later because it restricts what the fading platforms can do later. And this time there's not enough happening to lag the platforms. Grabbing either of the coins from the enemies at the end of the room takes too long.

Course 3

  • The sprite limit makes its first appearance in the second room. Hitting the first spearman from below is only slightly faster waiting for it to reach the edge, but it gets it far enough to the right that it won't disappear before Wario reaches the skull door spawn point. The big coin won't despawn until it stops bouncing around, and the big heart exists before the invisible block is hit.

Course 4

  • The breakable blocks can only spawn coins every fourth frame with a 50% chance. The low ceiling allows the blocks to be destroyed on a few different frames without losing any time, making the manipulation a non-issue. Getting zero coins still isn't an option because the fastest route over the lava requires grabbing a few.

Course 5

  • There aren't enough sprites availible to get rid of the pouncer in the second room. Five is actually a pretty hard number to hit.
  • The boss will start rising to the air after spending 120 frames spinning on the ground, plus however long it takes to come to a complete stop afterward.
  • There isn't a single well-behaved coin game in this run. In this one there are walls on either side of the room instead of just the screen lock other boss rooms have. Wario has to be carefully placed during the final jet dive, because if he hits the wall it will cost time that would be used to throw away the coins. Speaking of which, the walls also prevent Wario from throwing the coins offscreen... and this is the only floor high enough for Wario to get away with that without wasting time jumping. The coin replacement problem is solved by manipulating the front coins to bounce high, letting Wario grab a back coin out from under them.

Course 20

  • With fake death active, the spearmen are frozen before they're set to do any damage to Wario. This allows him to just pass straight through all of them. The star is frozen inside the block and can't be interacted with, but with the spearmen in the ladder section frozen it doesn't have to be.

Course 22

  • Setting up the bounce out of the lava is tricky because of where the duck has to be placed. It has a very large hitbox and needs to be as close to the lava as it can get without dying to be bounced off of. Then if it's too far away, Wario won't reach it before he's too low for the bounce... but if he's too close, he'll land on the edge of the platform instead of falling into the lava. And there's no time to extend the jump with a jet dash, because if that duck hits the lava Wario's goose is cooked. In the end there was no middle ground; using 3-frame pauses to take advantage of the 2-frame movement rule was the only way to get enough distance.
  • The pause and unpause at the end is to demonstrate that it unfreezes everything, and also to get the last duck offscreen before entering the door. Reducing the number of sprites that are onscreen will also reduce the lag time the display is disabled. It's only a fraction of a frame and only affects the frame count in one spot (course 36), but for consistency it was done everywhere there was time to do it. (Which wasn't that many places actually.)

Course 25

  • The large number of coins in Wario's path and the falling bridges make it easy to reach the sprite limit in the second half of the stage. It's used three times to get rid of some inconveniently placed enemies.
  • ...However, it also causes a problem. When the fake death glitch is used, Wario will drop coins if he is carrying any. The falling coins and jet hat on top of the number of sprites on-screen will be enough to cause the game to lag. To counteract this a coin route must be chosen that leaves Wario with no coins when he hits the lava.
  • There isn't a single well-behaved coin game in this run. In this one, throwing a coin on the ground will cancel out fake death's faster fadeout, so they have to be thrown from a jump, which temporarily pauses the coin game timer. Also, the boss takes up three sprite slots. Attempting to use coin replacement with the number of coins the route forces will fill up all the remaining slots, which also stops the timer. And there's ALMOST enough time to get rid of them all without coin replacement without jumping more than necessary.

Course 26

  • Sixteen frames from optimizing movement and nothing else. This level's not much more than flying straight through, and the rooms are too short for any significant time gains.

Course 27

  • Improvement comes entirely from getting enough coins to avoid having to take the detour right before the exit door. At least one coin is needed from the blocks at the beginning of the course to get enough. The second one can be gotten from the conveyor belt in the second room without any time loss. Oddly, both coins always appeared no matter how many times the previous input changed.

Course 28

  • Skipped, as it's no longer the faster course to play.
  • The map screens are slightly slower overall due to the course switch. However it has a larger frame rule (16) so no time is lost. This temporary time loss is not included in the table above.

Course 29

  • Up until this point every level has either been one big room and one small one for the exit or a few smaller rooms all laid out one after the other. In this one the main rooms still are, but one of them the exit is on the left side of the room. This allows the first use of the screen wrap glitch.
  • There's usually a waiting period while the camera scrolls horizontally to the next screen boundary. Having this happen while the camera is scrolling vertically (control is lost during this) reduces the waiting period.
  • If Wario stands any further to the left than he already is, the camera will consider him "centered enough" before reaching the screen boundary and stop scrolling. If this happens it won't lock on the next room when Wario moves left.
  • When a large enemy like a duck is stunned it creates a set of stars above its head. Just like thrown big coins there can usually be only one of these at a time, but coin replacement can be used so Wario doesn't have to wait for the first one to disappear.

Course 30

  • After coming out of the treasure room Wario is on the wrong side of the 2-frame rule to crawl to the left, and will instead be knocked away from the treasure door on the ground to the right. Another 3-frame pause fixes this.
  • Duck jumping into Bobo for the first hit prevents him from moving backward, and Wario can land the first hit slightly sooner. This is enough to beat a 32 frame rule for when the first bird can appear. Some initial sprite slot manipulation also saves a couple frames on the second hit from unmanipulated.
  • The pit at the left side of the boss room is not actually the bottom of the level. All boss rooms use the screen at the top left, well above the instant death line. That pit is instead an instead death tile, and can be used for the fake death glitch.
  • There isn't a single well-behaved coin game in this run. Not even this one; activating fake death after the boss fight prevents the game from starting, and the pause to unfreeze everything takes enough time to lose a frame rule.
  • RNG manipulation for the course 36 coin game starts back here. It's not the only place where the initial state can be controlled, but it's the easiest way to preserve the later levels.

Course 32

  • The minecarts will start moving sooner if Wario touches the top of them instead of coming in from the bottom and being warped up. And of course, it's important not to stop and jump off until he's reached the end of the cart.

Course 33

  • With badly placed enemies the first time the screen wrap is done and no enemies the second time, Wario needs to dash into five walls. However he doesn't need all of the fifth one; getting stopped early by the low ceiling will still be enough.
  • Out of all the screen wraps in the run this one takes the longest due to the blocks in the middle of the path, the bad placement of the walls to bounce off of, and having to do it twice. However it's still much faster than going through two autoscroll rooms.

Course 34

  • Hyper climbing is so fast that Wario can catch up to a thrown enemy and bounce off of it while it's still moving up, allowing a jump directly to the door in the first room.
  • Normally if Wario stands this close to the edge of the screen, it will stop scrolling before it reaches the next screen boundary and won't lock when moving to the left. However, free scroll rooms will always try to have the camera centered on Wario. The extra distance it moves is enough.
  • No, that last ladder can't be hyper climbed any more than it already is.

Course 35

  • By this point the screen wrap glitch is self explanatory.

Course 36

  • Autofiring right while jumping keeps the screen from getting too far ahead of Wario. The spike balls around the midpoint of the course then load late enough that he can fly right under them without stopping.
  • The thunderclouds will follow Wario forever and will never de-spawn. This makes the final spike ball section very laggy and Wario has to go higher than he normally would. Unfortunately there's no way to get rid of them. Even with both thunderclouds, five is still a pretty hard number to hit. Also, whether there's a lightning strike uses the same RNG as the coin game. Between all the clouds and the course 30 coin game the initial state for this coin game can be completely controlled.
  • As noted in the previous submission, when Wario is paralyzed and touching the ghost, nothing he throws can hurt it. This also works in reverse -- when something else such as a big coin is touching the ghost, it cannot paralyze Wario. This lets him save time getting the first hit by getting closer than what would normally be possible.
  • There isn't a single well behaved coin game in this run. In this one the problem is the low floor. A jump from the floor will just barely take Wario high enough to grab them the frame they appear, but they have a 50% chance of moving out of his reach on that frame. Instead of dealing with that a midair bounce off the small ghost gives enough height to reach them easily.
  • The small ghost is actually still "alive" offscreen. Its "death" occurs while Wario is throwing away the coins, freeing up a slot so only one coin is needed for coin replacement. The other coin is just there because that's how the coin game turned out, and it's in a bad slot to be used for the glitch anyway.

Course 37

  • It looks like Wario is one short of the sprite limit, as the spike ball disappears as soon as the mole is stunned. However if the mole is hit by jumping into it and letting go of A on the correct frame, the spike ball will invisibly reappear the frame after it disappears.

Course 38

  • There are a lot of potential shortcuts early in the level... that don't work. The early rooms don't have a layout that would allow a screen wrap.
  • The sprite limit is used twice to get rid of the two spearmen in the tunnels, which will otherwise be difficult to deal with. The first time there are already enough sprites on screen that nothing has to be done. The second requires manipulating enough coins to take out a big one, and then adding one more. The last coin must appear on the same frame the spearman would because Wario is going to collect it on the next frame.
  • This course is normally completed by hitting a large [!]-block... but the screen that contains it is an exit screen. This is the only one of the [!] courses that also has a regular exit. Now there isn't actually a door on the exit screen, but with the screen wrap glitch this isn't a problem. By finishing this way, the castle destruction cutscene doesn't happen.
  • The combination of the fake death and screen wrap glitches makes it impossible to throw away a big coin once it's been taken out. There's nothing to do but the slow method of taking it out next to the door and walking to it.

Course 39

  • If Wario is close to the center of the screen before starting the first screen wrap he can still make it, but will lose a lot of time jumping so he can reach the next wall without landing. It's better to go all the way to the left and use the extra space to speed that part up.
  • The second screen wrap can be done with four recoils, but the layout is so bad that it's actually slower to do this.

Course 40

  • The recoil from hitting something like the door or the guard (along with other things) works slightly differently. It will send Wario to the left as long as he stays in the air, but the camera will start following him if it reaches the edge.
  • A second hit is set up after end of input by placing a cloud for Wario to land on and hit the genie from above. This saves 103 frames at the cost of 59 for the final hit to land. By a nice coincidence, the method to get the final hit as soon as possible also puts Wario in the exact spot he would walk to during the ending sequence.

Known improvement

The same trick with the big coin that lets Wario touch the big ghost without being paralyzed also lets him touch the course 5 boss without being hurt. This lets Wario get the second hit on the frame it stops spinning, which is when it becomes vulnerable again. The boss won't have time to rise into the air and will immediately stand up, allowing in immediate third hit. This strat would save 40 frames over the current boss fight.
However, implementing this strat would make the course 5 coin game significantly harder. The big coin cannot hit the ground and start its final slow bounce until Wario is close enough to get the second hit, or else it will not interact with the boss and Wario will take damage. This places the limit on how fast the coin can disappear at well after every coin has spawned. The empty slot it leaves behind has such a low index that using coin replacement enough times will be impossible. This also means the disappearence can't be used to spawn a later coin in an earlier slot, making it much harder to replace the coins in the correct order. And an extra coin has to be replaced because Wario has to get rid of four coins at the end. AND the other two coin games would have to be redone as well. AND this strat was only found after the TAS had been completed.
So I decided to leave it as. I'll eventually give this another shot when I revisit this game for 100%, but it's been well over a year since I started and I need a break.

feos: ME UNBRANCH, ME JUDGE!
feos: Accepting to obsolete [1688] GB Wario Land: Super Mario Land 3 by Greenalink in 21:49.15 (with inheriting the star).


TASVideoAgent
They/Them
Moderator
Joined: 8/3/2004
Posts: 15644
Location: 127.0.0.1
This topic is for the purpose of discussing #4510: McHazard's GB Wario Land: Super Mario Land 3 in 19:43.51
Skilled player (1744)
Joined: 9/17/2009
Posts: 4986
Location: ̶C̶a̶n̶a̶d̶a̶ "Kanatah"
So....since this is a reresynced version, and you accidentally found a game breaking bug, would you also optimize it and ask a mod to replace the previous submission?
Active player (274)
Joined: 2/1/2014
Posts: 928
Temp Encode Link to video
AntyMew
It/Its
Encoder, Player (35)
Joined: 10/22/2014
Posts: 425
jlun2 wrote:
So....since this is a reresynced version, and you accidentally found a game breaking bug, would you also optimize it and ask a mod to replace the previous submission?
Surprisingly, the desync is pretty damn optimized as far as I can tell. Without knowing more about why the level selection glitch happens, it can't be improved. Wario enters the stage 3 exit door on the perfect frame, and even inputs down+b+start while paused (the input which causes the wrong warp) frame perfectly. Any other optimization I tried caused the glitch to fail.
Just a Mew! 〜 It/She ΘΔ 〜
Joined: 3/9/2009
Posts: 530
Anty-Lemon wrote:
jlun2 wrote:
So....since this is a reresynced version, and you accidentally found a game breaking bug, would you also optimize it and ask a mod to replace the previous submission?
Surprisingly, the desync is pretty damn optimized as far as I can tell. Without knowing more about why the level selection glitch happens, it can't be improved. Wario enters the stage 3 exit door on the perfect frame, and even inputs down+b+start while paused (the input which causes the wrong warp) frame perfectly. Any other optimization I tried caused the glitch to fail.
He knew it desynced already, so must have already seen the glitch. Also, unless I'm missing something major in the mechanics, there's no reason/need to be holding left and then pressing up to enter a door while on the jet in the 'for real' version, so the input there is clearly done with the glitch in mind. Pretty sure he's just having a giggle. /partypooping
Experienced player (589)
Joined: 2/5/2011
Posts: 1417
Location: France
Tangent wrote:
Anty-Lemon wrote:
jlun2 wrote:
So....since this is a reresynced version, and you accidentally found a game breaking bug, would you also optimize it and ask a mod to replace the previous submission?
Surprisingly, the desync is pretty damn optimized as far as I can tell. Without knowing more about why the level selection glitch happens, it can't be improved. Wario enters the stage 3 exit door on the perfect frame, and even inputs down+b+start while paused (the input which causes the wrong warp) frame perfectly. Any other optimization I tried caused the glitch to fail.
He knew it desynced already, so must have already seen the glitch. Also, unless I'm missing something major in the mechanics, there's no reason/need to be holding left and then pressing up to enter a door while on the jet in the 'for real' version, so the input there is clearly done with the glitch in mind. Pretty sure he's just having a giggle. /partypooping
dem luck den O_o
Current: Rayman 3 maybe? idk xD Paused: N64 Rayman 2 (with Funnyhair) GBA SMA 4 : E Reader (With TehSeven) TASVideos is like a quicksand, you get in, but you cannot quit the sand
Zarmakuizz
He/Him
Joined: 10/12/2013
Posts: 279
Location: France
I love the optimizations on this run, and I'm sad because the desync is way more exciting. Yes vote anyway, if there is a way to keep this run in a separate branch.
Site Admin, Skilled player (1256)
Joined: 4/17/2010
Posts: 11495
Location: Lake Char­gogg­a­gogg­man­chaugg­a­gogg­chau­bun­a­gung­a­maugg
So which one of these 2 is the actual submission?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Spikestuff
They/Them
Editor, Publisher, Expert player (2665)
Joined: 10/12/2011
Posts: 6451
Location: The land down under.
feos wrote:
So which one of these 2 is the actual submission?
Silly feos, both of them are. One breaks the game but is very questionable and the other breaks the game and is less questionable.
WebNations/Sabih wrote:
+fsvgm777 never censoring anything.
Disables Comments and Ratings for the YouTube account. Something better for yourself and also others.
Site Admin, Skilled player (1256)
Joined: 4/17/2010
Posts: 11495
Location: Lake Char­gogg­a­gogg­man­chaugg­a­gogg­chau­bun­a­gung­a­maugg
feos looks at the branch names. feos looks at identical times. feos looks at Spike calling feos silly.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Samsara
She/They
Senior Judge, Site Admin, Expert player (2242)
Joined: 11/13/2006
Posts: 2823
Location: Northern California
I think this is the "intended" submission with the "actual" time. The other run is legit as well, it just needs to be updated with truncated input.
TASvideos Admin and acting Senior Judge 💙 Currently unable to dedicate a lot of time to the site, taking care of family. Now infrequently posting on Bluesky
warmCabin wrote:
You shouldn't need a degree in computer science to get into this hobby.
Editor, Expert player (2373)
Joined: 5/15/2007
Posts: 3940
Location: Germany
Really nice run. I enjoyed it. Can screen wrap be done to reach the right side of the screen?
AntyMew
It/Its
Encoder, Player (35)
Joined: 10/22/2014
Posts: 425
MUGG wrote:
Really nice run. I enjoyed it. Can screen wrap be done to reach the right side of the screen?
Yes, but:
TASVideoAgent wrote:
The right side of the screen is much farther away and the screen doesn't like to scroll to the left, so going in that direction has no use in this run.
Just a Mew! 〜 It/She ΘΔ 〜
Spikestuff
They/Them
Editor, Publisher, Expert player (2665)
Joined: 10/12/2011
Posts: 6451
Location: The land down under.
feos wrote:
feos looks at the branch names. feos looks at identical times. feos looks at Spike calling feos silly.
Silly feos
WebNations/Sabih wrote:
+fsvgm777 never censoring anything.
Disables Comments and Ratings for the YouTube account. Something better for yourself and also others.
Site Admin, Skilled player (1256)
Joined: 4/17/2010
Posts: 11495
Location: Lake Char­gogg­a­gogg­man­chaugg­a­gogg­chau­bun­a­gung­a­maugg
UR MOM IS SILLY, DOUCHE
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Noxxa
They/Them
Moderator, Expert player (4130)
Joined: 8/14/2009
Posts: 4090
Location: The Netherlands
feos wrote:
UR MOM IS SILLY, DOUCHE
[15:54:19] <Spikestuff> I poked feos [15:54:25] <Spikestuff> and proved him silly [15:54:31] <Spikestuff> I win the internet for the entire month (that said, let's stop this dialogue before it goes even further out of hand)
http://www.youtube.com/Noxxa <dwangoAC> This is a TAS (...). Not suitable for all audiences. May cause undesirable side-effects. May contain emulator abuse. Emulator may be abusive. This product contains glitches known to the state of California to cause egg defects. <Masterjun> I'm just a guy arranging bits in a sequence which could potentially amuse other people looking at these bits <adelikat> In Oregon Trail, I sacrificed my own family to save time. In Star trek, I killed helpless comrades in escape pods to save time. Here, I kill my allies to save time. I think I need help.
Spikestuff
They/Them
Editor, Publisher, Expert player (2665)
Joined: 10/12/2011
Posts: 6451
Location: The land down under.
TASVideoAgent wrote:
Use of TAStudio is also why the rerecord count is zero.
Re-record count: 1 Caaaaaaaaaaaaaaaaaaaaaaaan we get this fixed?
WebNations/Sabih wrote:
+fsvgm777 never censoring anything.
Disables Comments and Ratings for the YouTube account. Something better for yourself and also others.
Site Admin, Skilled player (1256)
Joined: 4/17/2010
Posts: 11495
Location: Lake Char­gogg­a­gogg­man­chaugg­a­gogg­chau­bun­a­gung­a­maugg
It's what his movie has, so why not 1?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Spikestuff
They/Them
Editor, Publisher, Expert player (2665)
Joined: 10/12/2011
Posts: 6451
Location: The land down under.
feos wrote:
It's what his movie has, so why not 1?
Because it was for the input fix and the RR went up 1 for some reason.
WebNations/Sabih wrote:
+fsvgm777 never censoring anything.
Disables Comments and Ratings for the YouTube account. Something better for yourself and also others.
Noxxa
They/Them
Moderator, Expert player (4130)
Joined: 8/14/2009
Posts: 4090
Location: The Netherlands
feos wrote:
It's what his movie has, so why not 1?
0 is identified in the database as "Unknown rerecord count". 1 isn't, which skews the movie statistics (and some people would quite favor the movie statistics to be accurate). And as Spikestuff said, the rerecord count used to be 0, so 1 is inaccurate as well.
http://www.youtube.com/Noxxa <dwangoAC> This is a TAS (...). Not suitable for all audiences. May cause undesirable side-effects. May contain emulator abuse. Emulator may be abusive. This product contains glitches known to the state of California to cause egg defects. <Masterjun> I'm just a guy arranging bits in a sequence which could potentially amuse other people looking at these bits <adelikat> In Oregon Trail, I sacrificed my own family to save time. In Star trek, I killed helpless comrades in escape pods to save time. Here, I kill my allies to save time. I think I need help.
Player (62)
Joined: 9/2/2008
Posts: 289
Location: United Kingdom
RIP my player status. But in all seriousness I am really impressed with the new tech used in the non-game end glitch run and for extra lols, my runs never used any of the memory reader/viewer features. I was actually laughing when seeing these new skips like the guard skip in course 40 and a full autoscroll skip in one of the train courses. I may get back into TASing when a TAS supported 3DS emulator exists which I know will be quite some time.
greenalink.blogspot.com
Post subject: Movie published
TASVideoAgent
They/Them
Moderator
Joined: 8/3/2004
Posts: 15644
Location: 127.0.0.1
This movie has been published. The posts before this message apply to the submission, and posts after this message apply to the published movie. ---- [2746] GB Wario Land: Super Mario Land 3 by McHazard in 19:43.51
Fortranm
He/Him
Editor, Experienced player (880)
Joined: 10/19/2013
Posts: 1122
Maybe this publication shouldn't have those 4 "forgoes" tags if the game end glitch movie is now considered invalid?
Emulator Coder, Judge, Experienced player (733)
Joined: 2/26/2020
Posts: 791
Location: California
Fortranm wrote:
Maybe this publication shouldn't have those 4 "forgoes" tags if the game end glitch movie is now considered invalid?
A game end glitch is probably not impossible to have anyways. Eventually someone will probably make a game end glitch movie which doesn't end up relying on the emulator inaccuracy the published movie used.