Talk:Gauntlet II

RE: level 100 being the winning design from a competition.

I would like to see a source for this claim. I just played Gauntlet II (the PS3 port - which is supposedly direct from the arcade version) to level 102.

I can assure you that if Level 100 was the winning design from a competition, there mustn't have been many entries. It was a very boring level - quite plain, without a dragon, many monsters, or anything interesting. It was certainly no prizewinner. I've looked on the net, and the only reference I can see to this supposed competition are other websites that appear to be quoting the wikipedia entry.

Further, I can't see logistically how such a competition would work. This was the days before the internet - the only feasible way to collect the entries would have been on graph paper, with the walls/monster generators etc marked out by hand. That just doesn't seem likely. Especially considering that level 100 isn't the final level.

122.108.241.152 (talk) 09:46, 12 June 2011 (UTC)iiago

Seperate bugs section

The Ports section sort of bleeds into talking about bugs, and it isn't clear if they're bugs that exist only in the ports! Can someone with more knowledge on the subject split the sections? Srkingdavy (talk) 02:22, 29 September 2011 (UTC)

The whole section reads like a blog post. — Preceding unsigned comment added by 70.94.90.143 (talk) 00:02, 25 April 2012 (UTC)

Someone had commented out the entire bug section, but it has no sources anyway, portions of it have been challenged, and it does sound kind of bloggish so I've moved it here into talk for the time being. I think that makes a lot more sense than leaving it as a giant in-article block of non-displayed text. If anyone wants to re-add portions of it at a later time then please feel free, but remember that it needs sourcing. -Thibbs (talk) 11:59, 28 September 2012 (UTC)

Gauntlet II bug section

Gauntlet II had several bugs, and some quarter guzzling features that were taken from the "Final" rom version of the first Gauntlet. The "Fight power" multiplier was bugged for the half-level players from the "Original" Gauntlet; all players picking the red, blue or yellow characters would have their fight power at either level 1 or level 2, regardless if they were supposed to have an extra "half" level (Warrior and Elf). So the Warrior would have fight level 2, which is the same as Valkyrie's, and the Elf would only have fight level 1. The only fix for this was to play the Green character, which would give Warrior and Elf two to three times fight power, and one to two times normal fight power respectively (the correct value for those characters), but would also give Valkyrie and Wizard an extra half level. So Valkyrie would have two to three times fight power (same as Warrior), and Wizard would have one to two times normal power (same as Elf). All other attributes worked as they should. This bug was never fixed. The quarter draining feature was taken from Gauntlet 1 Final Revision, and refined a bit to be less harsh on the player (less food removed initially). Basically, the game became more difficult at every multiple of 16,384 points (2 to the power of 14; more on this binary math later). The monsters generated slightly faster at each point step, and the game would remove a small amount of the placed food. The higher your score became (on 16,384 point steps), the more difficult the game would become, with difficulty divided by the number of coins inserted. Eventually, at around 200,000 points, there would be so little food placed on the levels, that it would become impossible to gain health by clearing the levels, even if you were stacked with power ups. This would force the player to eventually die, or insert more coins to keep playing (which would reduce the difficulty). There was a bug with the 16,384 point difficulty counter, which had to do with the binary system of number storage. In an 8 or 16 bit system, values of 0-127 are often used as "signed" values, while 128-255 may be used as "unsigned" (or vice versa), with the highest value in an 8 bit memory location being "255". Gauntlet was a 16 bit game, however even on 32 bit computers, 255 is often the highest value for some variables (just look at the Internet Protocol or IP address). Anyway, at the game score value of 16,384 x 128 (approximately 2.1 million, exact value 2,097,152), the food removal counter would "overflow" (since the number counter at 128 switched from signed to unsigned (or vice versa), calculating how much food would be removed from the levels. This caused the game to put the maximum amount of food into the levels, although the monster difficulty remained at maximum. At 16,384 points x 256 (approximately 4.2 million points), the "256" was too high of a value to be stored in a memory cell only holding values of 1-255, so this caused a complete reset to "1", making the game difficulty act as if you had started a completely new game and your score were back to "0". The frequency of the Thief and Mugger appearances were not related to score, so were unaffected by this. Enterprising players could use this exploit to their advantage by building up their one credit health as high as possible (at least 7,000 health was needed for success), and playing up to 150,000 to 200,000 points, inserting one credit into the other three players, then having them join on a map with lots of 30 point ghosts and treasures. Then, by raising the main player's point multiplier to x8 by grabbing treasure, and stalling so the walls turned into exits, and having the other three players leave, the player could shoot 240+ point ghosts until their score became over 2.1 million. If this was successful, they would have bypassed the "food starvation" stage, and they would kill the other three players, and play as long as possible, and hopefully have enough health to survive the "next" starvation stage without using more credits, which would happen at around 4.3 million points. (about 19,000 health and the Death "potion" points set to 8,000 per killed Death, were needed to survive another 2 million points of food level starvation). Some other bugs (a few which could crash the entire machine) involved getting the thief or mugger's linked list lost, by standing right next to their spawn point (the spot where you entered the level), so they attack you while they are right on the spawn. Then when you move out of the way, they move in a straight line, up to a wall, instead of exiting the level as they are supposed to do. You could sometimes go to the other side of the wall, and the monster would teleport on top of you, causing very bizarre things to happen.