Inaccuracy of MP: If for any reason that Willow acquires a large amount of MP (80 for example) within a small number of movie frames, the game has to sit there and count every single digit (31, 32, 33, 34, etc.) until it finally gets where it needs to be. If a large amount of MP is in queue which I am sure that's exactly how their system works, then it does take a certain amount of time to count them all up. Now, if the game is still counting a large amount of MP and not being aware of Willow using any magic spell during that point, then it is strict that this is a nicely known glitch. When the game finally gets done counting MP back where it needs to be, then it regains its accuracy and will keep track of magic spells that was used again. If for any reason that Willow leaves the screen while MP is still counting up, that means the game has to halt counting MP for a moment and focus on taking Willow to the next screen - then it gets back into counting MP.
Abusing "inaccuracy of MP glitch": This was effectively used during a level-grind toward Nockmaar. This is done by making sure all red ghosts are gathered in one pile as quick as possible and as close to one side of the screen that it can get to without touching Willow. From that point, the goal was to kill them all with the Devil Eye sword BUT making sure Willow does NOT touch MP balls during the course of killing them all. Once all red ghosts are killed and there are several MP balls piled up, it's easy for Willow to get several or all of them in one shot, put the MP in queue, and immediately use the nearest side of the screen to manipulate red ghosts' appearance nearby. This glitch technique allows Willow to use his Thunder spell about 5 to 7 times, instead of 4, before having to score more MP from red ghosts.
--Simple Willow script by TheAxeMan lastx = 0 lasty = 0 relx = 0 rely = 0 function showWillowCoords() relx = memory.readbyte(0x00cb) rely = memory.readbyte(0x00ca) gui.text(relx-20,rely,relx..","..rely) xmove = math.abs(relx-lastx) ymove = math.abs(rely-lasty) gui.text(relx-20,rely-10,xmove..","..ymove) end; gui.register(showWillowCoords) while (true) do lastx = relx lasty = rely FCEU.frameadvance() end;
function safeText(x,y,text)
if x > 0 and x < 255 and y > 0 and y < 240 then
gui.text(x,y,text)
end;
end;
Besides, why be at 700 ex. on level 3 when you're 10 ex. closer to the next level anyway?!
http://dehacked.2y.net/microstorage.php/info/820131848/NES.willow.P0RTAL.0ƒ.RAIN.[draft.4].fcmhttp://dehacked.2y.net/microstorage.php/info/783631037/NES.willow.P0RTAL.0ƒ.RAIN.[draft.4].fcmLevel Select To begin, enter the password "oBH jq2 xgI 5ve iNw g5f" When the game begins, pres SELECT to display the level number as two white blocks. To change it, hold B and press UP or DOWN to change the first number. Hold A and press UP or DOWN to change the second number. Press SELECT to warp to the desired location. Location Coordinates Gates of Nockmaar 0, 18 Tavern of the Travelers A, 9 Tir Asleen F, 19 Dew 13, F Newlyn 1A, E Po's house 13, 3 Twins Tower 8, 3 Thunder Cabin C, 10 Abang's room 18, 1B Bavmorda's guard 0, 13 Bavmorda 11, 1B
--Simple Willow script by TheAxeMan
lastx = 0
lasty = 0
relx = 0
rely = 0
function showWillowCoords()
relx = memory.readbyte(0x00cb)
rely = memory.readbyte(0x00ca)
gui.text(relx-20,rely,relx..","..rely)
xmove = math.abs(relx-lastx)
ymove = math.abs(rely-lasty)
gui.text(relx-20,rely-10,xmove..","..ymove)
end;
function safeText(x,y,text)
if x > 0 and x <255> 0 and y < 240 then
gui.text(x,y,text)
end;
end;
This is to ensure I follow my new positioning pattern smoothly. It may look like I am seeking to loop this pattern and it may look annoying. But without this pattern, I can't abuse the inaccuracy of MP glitch destructively.