The category is mislabeled. This isn't "glitched", it's beating the game's random mode.
I agree. The branch should be changed to "random mode" or something else that more accurately describes the TAS. "Glitched" is not only inaccurate, but it makes it look like an April Fool's submission, and I assume you really want this published.
I have a couple questions.
- Why do you have to phone 13 numbers at the beginning? Is it necessary to gain even one secret Denjuu?
Sorry, I'm not familiar with this game.
The phone, and therefore the glitch, is trigger at intervals of 5 minutes in-game time, so I decided to recruit all the secret denjuu to reduce the amount of time I walk around in circles doing nothing.
FractalFusion wrote:
You seem to imply that, without a secret Denjuu, the fight against Bashou is 2 minutes of text and in blue. How do you know it takes 2 minutes?
Without a secret denjuu, I would be stuck with a level 5 starter with only 1 offensive attack. The 2 minutes was an estimate based on the fact that the previous run, which didn't use secret denjuu, took 1 minute+ with the snake enemy, which is at a lower level.
Since not only is the damage towards Bashou is around the same, but it also has alot higher health, it was predicted that it would take ~2x longer.
Wow, thanks!
I'm stuck on a particular part in the run. I've manipulated a boss battle to be faster than my previous WIP, but encounters horrid luck later that kills the improvement. However, my slower WIP has better luck later on, and thus becomes faster (alot) latter.
Any ideas what should I do?
rog was joking? He sounded legit.
Anyway, there should be a rule preventing people from submitting runs like this in the future, regardless if it was a joke or not.
Ringrush should be banned for the irreparable damage he has done to this site's honor.
Well, at least he cancelled it. It could've been published before RingRush cancelled the run; then it would be a mess. I'd say, let RingRush go this time, but make "cheating" like this a bannable offence from now on.
The improvements are all from stage 3. I could have saved 5 frames instead of 4 if not for those meddling bots and their pesky lag frame.
I can't get over this. I'll try to see if that 1 frame could be saved.
Edit: I did it! But it caused the rest of the run to desync, and I got horrid luck. This may take some time.
Edit 2: WIP of the first 2 stages. I also changed the first boss fight slightly, for better or for worse. Feedback would be nice. :)
Really? =0
......
Does the purple sqaures count for 100% too? I'm getting conflicting answers when I asked someone who got 100%.
Answers:
Silfalas wrote:
No. Purple boxes let you get the reward of a mission if it has one but it won't "complete" it. If you used it on the remaining two blocks the counter would still be 118/120. You will have to do it on your own to complete the checklist.
CelloJerbear wrote:
This is not strictly true. You will in fact have a gold checklist page, but the ones that you used the purple boxes on will still have the purple spot. All the green/red ones will be gold
The thing I'm trying to clarify here is what actually counts as 'Reaching the Credits?' if you can unlock the credits and go to the options menu and watch it. is that reaching the credits? or must they be triggered by the game?
You CAN'T do that! The game would NOT allow you to! I told you already. >.>
jlun2 wrote:
I tried, doesn't work
If you don't believe me, why not try it yourself? You can only view the credits after completing 100 checks!
If i remember correctly, couldn't you get the free unlock squares and use it on the bottom right corner? that would unlock the credits. i'm not a TASer so I'm not sure if you have to make them trigger for the run to count or if you need to unlock the credits.
I tried, doesn't work. Besides, the purple squares only unlocks the award, but doesn't count as "done". So the purple squares are quite useless.
- 35 rerecords common if you're going to fake make it higher God!
This movie that has high ratings have only 58 rerecords. Unpublished it now? LOL
Antoids wrote:
TAS site rules are that we time the game until final input. Bending this rule at all completely invalidates timing on just about every single video (most games end at least 2 frames after final input, usually more).
Thereareruns which end input way before its supposed to. :P
What's RT?Here's a page that documents some glitches in SMW.
Here's a post about yoshi eating nothing, which can change mario's status.
Here's a post about triggering the credits early using the above glitch.
Hope that helps.
Luckily, there's little to no luck involved in Free Run! Every stage starts off exactly the same; there's no way things like where the green boosters appear on Grass could be manipulated.
Also, according to Link to video video, Sand is the fastest, but it requires going through the sand pit every lap, which I'm sure won't last 100 laps. So the 100 laps would be done on Grass, which should take ~3 seconds for every lap except for the first.
dem questions--
input file:
The battle RNG can be abused online; for this reason I won't upload it because I do not want to openly share the information on how the battle RNG operates. I've demonstrated this to my friends at Smogon and we've decided to keep battle RNG under wraps due to BW being the active game.
So...if a TASer somehow figured it out alone, and submitted the TAS, online play would be wrecked? 0_o
While doing some test runs in "Free Run", it seems that pressing "A" for 1 VI on certain VI's gives a very small boost in speed. In all other VI's, it just slows you down. Time to restart the run, I guess. :P
In the latest revision of dolphin, the memory card doesn't clear out after playing back a movie. This means I have to manually delete the save file everytime. rog, can you please request for a fix? Thanks!
While making this TAS, I've been annoyed by frequent freezes of the emulator in dungeon manipulation and continuous desync between luabot and real result in battle. They made the rerecords to 5 million and make me waste several months...
This problem has been reported by otherpeople too.
Anyway, I'm going to watch this run later to see the 07:46.48 improvement.
