Hey, it's absolutely fair to be annoyed when people take your work without crediting you. So why all the victim-blaming here? C'mon guys.
Unfortunately I don't have any good advice for you. It's very hard to stop people from engaging in plagiarism or copyright violation on the Internet (and yes, I'm aware of the irony of saying that here). I suggest you contact the creators of that video, say "Hey, you used my stuff without my permission, I want some credit." It's entirely possible you can resolve this peacefully, and you're more likely to get good results by being polite than by immediately opening fire. You can always step things up if they don't respond well to politeness, but you can't step things down, so to speak.
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
A few years ago I tried to make an arcade SF2:TWW playaround run, using glitches like handcuffs and all the other things Guile can do, invisible Dhalsim, player vs player fights, etc., although I never got far with it. A good playaround/glitchfest would probably be able to obsolete both SNES runs.
I have a question related to this, and preferred game version in general.
How is the preferred version/port of a game decided? Is there a list?
For example NES Double Dragon is also on this list, but there are surely plenty of other ports of that game, so should I do NES double dragon or the Genesis Version (which also has a published run) or something else?
In the specific case of Double Dragon, there's actually wildly different games with the same name. The Genesis version, if I recall correctly, has a lot in common with the Commodore 64 version of all things, and both have levels that aren't in the NES version (and vice versa).
There's no general rule though. Usually you go for the most complete version (in the case where some versions have more content than others) and/or the "best" version (in the case where some versions have worse graphics/sound/framerate/etc.).
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
Are there any ingame-time runs that are not (at least) one of a) for a game with a speedrunning community that relies on the ingame clock, or b) for a game with very long time-based score tallies?
My inclination would also be to go on a case-by-case basis, but on the other hand my impression was that the rules for the Vault were rather strict and simple (viz. fastest realtime any% or 100% runs only). I wouldn't want someone to spend a lot of effort on a "Vault-only" ingame-time-oriented run only for it to get rejected...not that I have any evidence that someone is considering making such a run.
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
There was a lot of interest in Brookman's previous submission; this seems to be mostly a refinement of that one, and I suspect people aren't really interested in watching a 35-minute-long movie again for comparatively minor differences.
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
Sure, you could provide a verification movie that unlocks the 12th world and then do a single run with all 12. That's also a perfectly valid approach, and frankly better than the two-run approach I suggested; d'oh!
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
Yeah, this is a tricky problem. My inclination would be to have two separate runs: one which does the 11 normal worlds, then one which does just the 12th world, but includes a verification movie that does the necessary grinding. Nobody would actually watch the verification movie (because it'd be boring as hell); it's just there to prove that access to the 12th world wasn't cheated.
On the other hand, if you think your plan can be made entertaining (a.k.a. Moon tier), then go for it; as long as you entertain the audience it doesn't much matter what you do otherwise.
Either way, good luck with the TAS!
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
I vote yes and don't understand how you win against Pikachu.
To be honest i don't know why i don't die first if i suck Pikachu in the air and fall with him in the ground.
If i do this way with Pikachu in Saffron City in a Vs. match i am dying first it's really weird. I am sorry that i can't give you better information's about that fact.
In Melee I used to get kills this way all the time, as a way to troll my friends. I assumed it was just a matter of Pikachu's hitbox being lower than Kirby's, so Pikachu gets zoned-out first.
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
I know that TAS can converts random variables to fix variables.
To be clear, TASes don't change random variables into fixed ones. However, they are (sometimes) able to get the random number generator to produce favorable numbers. Depending on exactly how Binding of Isaac works, it could potentially take a long time to generate a good level or set of levels. Or perhaps it'd be trivial; it's hard to know without someone taking the game apart to see how it works.
But yeah, as far as I'm aware nobody's able to make submittable TASes for Flash games.
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
Is Gauntlet 1 actually completable? I know Gauntlet II just loops forever; way back in the day I left my NES running for days and had a warrior with 99 carrying capacity, run speed something like three times faster than the elf, tons of extra shot power/armor, etc. from all the dragon boosts. Still sucked at using magic though. :D
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
Basically the verification movie is just there to make certain that your starting point was achieved without using any cheat codes or utilities (like a Game Genie). It doesn't have to be optimal at all. I think the New Game+ TAS of Chrono Trigger had a verification move that was over 24 hours long because it used a script to grind all of the characters up to level 99.
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
The author is very clearly aiming for a speed TAS (i.e. this is not an attempt to obsolete the much slower-paced current publication).
Speaking as someone who isn't really into N64 Smash Bros., it does seem quite fast, but I didn't find it all that interesting. At least it avoids the common problem many speed-oriented fighting game TASes have of there being one optimal combo that gets used in every single fight in exactly the same way. Instead everyone just gets ring-out'd as quickly as possible, but tactics for that at least vary somewhat.
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
This makes me wonder how well consoles would sync between themselves.
I was thinking about something sort of similar: with a system like this you could theoretically play networked multiplayer games on the original SNES. Each player's input would be read by the device, streamed over the network, and sent to the other player's console via a custom controller.
My guess is they'd desync after maybe a few minutes (even ignoring any latency issues due to the network), but it's a cute idea.
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
Maybe I'm missing something here, but are there no mushrooms or fireflowers in the rest of the game? Was it truly necessary to run through the final level twice to grab a flower?
1-1 and 6-2 both have powerups that are revealed but ignored.
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
Does exposure (author of submission 4667) deserve co-author status on this movie? It seems a little cruel to have someone submit a movie, then go "Hey, nice submission, I see what you did there but I can do it better, no publication for you."
Fresh input, so nope.
Presence or absence of other users' input is not the only thing to consider for co-authors. Not that I'm really aware of the differences between these runs and the previous publication, but I get the distinct impression that you would not have known how to make this improvement without exposure's submission.
Put frankly, this strikes me as a rather rude submission. I'm open to being convinced otherwise, but as it stands I'd have to vote for it not being published (in any category), simply on the grounds that we should be polite to potential new TASers instead of (effectively) stealing their work.
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
Does exposure (author of submission 4667) deserve co-author status on this movie? It seems a little cruel to have someone submit a movie, then go "Hey, nice submission, I see what you did there but I can do it better, no publication for you."
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
Dude, be polite. Nobody is required to do anything to help you out here. If the encoders are busy, then they're busy; you can always watch the TAS in an emulator.
Dude, be polite. Nobody is required to do anything to help you out here. If the encoders are busy, then they're busy; you can always watch the TAS in an emulator.
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
Anyways, is it me or like almost ALL good RPGs on the SNES have totally game-breaking glitches? I mean, Lufia II, Secret of Mana, Chrono Trigger, and with a glitched Secret of Evermore run I'll be done ^o^
What you're seeing here is more like "All games on the SNES have totally game-breaking glitches, but we mostly only know about the ones for games that people have played a lot of." Writing software for these old, heavily-constrained systems is hard (the SNES had 128kB of RAM; the NES only 2kB!), and there's no extra money to be made by making your software ironclad anyway. As long as players make it through their first playthrough of the game without running into any difficulties, that's good enough.
Pyrel - an open-source rewrite of the Angband roguelike game in Python.
