It's easier for me to illustrate what I mean. Imagine a contest, in which several teams participate to create a certain product, and the winner is to be decided by a poll between these teams. Team A has 10 members, team B has two. They create the products they're supposed to, and vote on them. All members of team A vote for their product. All members of team B vote for theirs. What does this poll show in regards to the products themselves? Nothing. It's obviously exaggerated to illustrate the weak spot without wasting a lot of paper, so I believe you get the idea.
And yes, democracy is perverted by design, but it's a thing easiest to agree upon between all members of pretty much any given community. I've always been towards a small circle of people who know their shit™ to make decisions, rather than having a large circle of people, most of which are absolutely unrelated to the subject at hand, do it. :)
That's actually a good idea.
Sure I have, my point was more about the fact that for authors, or generally any persons directly affiliated with a certain voting option, them voting for this option is effectively predefined (and thus known beforehand), which means any poll can theoretically be won just by having enough people directly affiliated with the option, perverting the majority rule and defeating the purpose of a poll in the first place. However, as AKA pointed out, this can be solved by a larger electorate. Indeed, voting for oneself is no big deal at all when the overall electorate is orders higher than amount of people affiliated with each particular option, but obviously, this is not the case here, as 2 out of 37 votes make 5.41%, which is pretty significant.
Of course, what's done is done, and I don't want to dispute nor discredit the voting results, but I think that for all future polls, the authors should be disqualified from voting for their own runs (I do believe this is fair) — at least until the voting audience grows, like, tenfold.
No, what I'm saying is, the author will always want to vote for their own run, due to the obvious bias involved. Which is why it's strictly prohibited in every possible voting system where the result is important for whatever reason. Not to say that it's just classless.
That would work, but the important thing is that there are gazillion routes in SMR, and an unoptimized run would take as much as ~4 hours realtime (to watch, not to do).
Well, I'm more or less fine with that naming scheme, but I'd still prefer having movie# instead of date, just to be able to locate the appropriate publication page far more conveniently. Why do I not think date is that important in this case? Because if I need an exact date, I can check the movie page (the only action being typing in the movie#), and I can still sort by date in a window manager, because the files have this attribute already "built-in". Not having a movie#, however, would make me do excess actions like searching or browsing by game name before locating the actual movie page.
Just my two cents.
Something like "game name - category - publication/submission number - player" would probably be better than having time in the filename (some movies are longer for whatever reasons like category change), and movie version number is about as irrelevant to someone who doesn't track the movie's history as the publication number… except the publication number has a page associated with it, which is a huge bonus.
I fully support the incentive, btw, the current naming conventions are indeed very counterintuitive (not to say bad). Same goes for screenshots, which could be SO much simpler going just by "publication number - screenshot version", since you don't need anything else at all.
My original point (which is to use the search to find the topic about the game in question) stands just as well, the fact that I confused two hacks doesn't mean I couldn't have searched for the relevant topics — in fact I did; I just didn't read them through beforehand to find out which is which, because it wasn't my intention to begin with — hence I got caught red-handed, and I have no problems with that, nor with not coming off great in your eyes. Hope that suits you.
My bad, it was for Super Mario Impossible/Metamorphosis/Forever, not Kaizo.
That one was definitely more prone to starting new topics, but that was more due to people not knowing the actual name of the hack, which is not the case here. All of them got eventually merged into one thread.
Not using search when it obviously works is bad.
Of course not. >_>
Seriously, why don't you use a search button? This is the fourth or fifth Kaizo topic that has been created since the one I linked to.
My opinion on this is a bit complex. For one, this run doesn't use all the opportunities for entertainment, and fails to aim for speed, either. On the other hand, the published run is no better (since it's of course severely outdated, and was made back when tools were quite poor and/or players didn't know how to use them to their full potential).
But. What I'm suggesting is, to do whatever you like with this run (it's subpar, imo), but make a new one in the near future:
1) on the arcade version when we get FBA accepted (see below),
2) and on higher loop (see below).
Version differences are quite noticeable. Arcade version has:
1) less lag (SNES version lags everywhere) yet better image quality;
2) much better sound (unlike this cow barf on SNES version) with more voice samples ("destroy the core!");
3) higher difficulty (yes, even harder);
4) more and better stages (this will increase the overall length by some ~10 minutes, but the stages themselves are so worth it);
5) more and better bosses;
6) likely something else I forgot.
As for higher loops, they have more (and somewhat faster) bullets, killed enemies release suicide bullets, all that kind of stuff that makes the game even harder (and makes TASing it more worthwhile). For example, this footage by BGR-44 demonstrates parts of loop 3 gameplay, and there are likely to be more loops meaning more bullets.
As such, my vote for this movie is meh. I'll be waiting for an arcade version.
Well, most of the improvement came from skipping a missile expansion and one-rounding Charge Beamst, the rest looked about as slick as in the 100% run, actually even better. :)
Rather, you're deliberately missing my half-serious remark basically stating that, while "Transylvania" is a word that does make sense, "Castlevania" is one that doesn't, not where the name comes from (it should be obvious to anyone knowing a bit of history behind the series' general plot).
Anyway, if you feel like analyzing this further from that particular perspective, here's some food for thought: trans is Latin for "across, beyond", silva (or sylva) is Latin for "woods, forest". Trans + sylva + nia basically means a land across/beyond a forest, a forest land. Makes sense, considering its geographic whereabouts? Indeed.
Add "castle" so that it chops a syllable off of "sylva", and you get… nonsense. You, user Sabikage, just made a post on this forum — loosely following this naming scheme, it can be called Sabikapost! At best, if you stretch it so that "-stle" serves as a phonetic replacement for "syl", you get a forest castle. Sounds quite lame, and not always true. And even "Transylvania castle" is too vague a description considering there were multiple castles there back then.
And I would like to stress once again that my original post wasn't a serious criticism of any of the game's aspects, and was more of a sarcastic remark aimed at pirate_sephiroth's nitpicking.