To loop over all the key/value pairs in a table, use the pairs iterator:
> t = {foo = "bar", [123] = 456}
> for key,value in pairs(t) do print(key,value) end
foo bar
123 456
Honestly, I don't really know why its preffered, yeah maybe its more comfortable than VBA, but considering the fact that VBA is more than 10 years old being developed, I harldy see why.
Bizhawk uses a VBA-based core for GBA games, not something independently developed.
I have trouble getting excited about Metroid 2 fan remakes considering how many of them have gone unfinished, but if this one bucks the trend then hey, awesome.
Could it be said that a TAS of Final Fantasy 1 [NES] with hard resets is physically unrealistic, due to how RAM clears slowly? I mean, this isn't something you can fix by better emulation, the hard reset.
Compare it to a TAS of a GBA game that uses hard resets, with the BIOS (the Gameboy Advance bootup animation) ignored, and a slightly longer TAS of the same game with no hard resets. If the former TAS only wins due to not emulating the extra delays, shouldn't the latter TAS win?
(I'm probably not phrasing this right, but it needs to be thought about)
If you have Windows 7 Professional, Ultimate or Enterprise you can use 'Windows XP Mode' which is a kind of official Windows XP virtual machine. http://windows.microsoft.com/en-AU/windows7/install-and-use-windows-xp-mode-in-windows-7
Disclaimer: I haven't tried it with hourglass. (I actually -should- try it with hourglass... Would be interesting to see if I can do anything!)
I'd really like to make a 3-player TAS of this, but I definitely lack the proper resources to make it work at the moment.
What kind of resource would you need? If it emulates in a TASing emulator fine, you don't need three controllers or anything like that, you can use multi-track recording where you do input for P1, load state, do input for P2 while input for P1 is playing back, etc.
I am not talking about anything but the way you enter those two doors and press the elevator button. One way is obviously slower than the other. Maybe you should explain in your own language (or someone translate this to it).
If I press the button in the fastest time, I should lose it to stay undamaged!
But honestly, I was very lucky that this defect was neutralized by game, because that's my fault that I pressed the button late!
So it's like the super mario bros 21 frame rule? Where even if you do the rest of the level before that point faster, you have to wait so that you can avoid being damaged anyway (which would waste more time then it saved)?
Awesome news!
PJ got a 40:22 1CC on max difficulty, using Pimple and all speedrun strats (including fastest Big Blag and fastest Robo Manus).
Watch it here:
Link to video
You don't need to test on console because... You can learn what the input is for a trick in the english RTA route and do it on emulator, and if it ever doesn't match up you can report it as a bug :D
6: This could be a huge problem. If glitched action commands behave vastly differently between English console and English emulator, I won't be able to use the English version. In that case I'm going to take the Japanese version without a question.
Can a bug report be filed? Or are there no active devs?
