User:Mantidactyle: Difference between revisions

From Data Crystal
Jump to navigation Jump to search
Line 4: Line 4:
* [[Pokémon TCG]] : Currently working on the AI of some CPU opponents being unable to use Pokémon Breeder for some weird reason when playing a modified deck.
* [[Pokémon TCG]] : Currently working on the AI of some CPU opponents being unable to use Pokémon Breeder for some weird reason when playing a modified deck.
* [[Skies of Arcadia]] : Currently working on an editor for enemies, spells and special attacks.
* [[Skies of Arcadia]] : Currently working on an editor for enemies, spells and special attacks.
* [[Yu-Gi-Oh! Dark Duel Stories]] : Currently working on the stupid AI discarding Tremendous Fire instead of activating it. What could possibly go wrong ? Someone obviously didn't debug there. The subroutine used to discard a Tribute monster while the hand is full is being called with a hand consisting of one spell card because the conditional statement is utterly fucked up. '''Update 2 :''' Guess what ? The AI choose to discard Swords of Revealing Light instead of activating it if there's no monsters on board ! '''Update 3 :''' *sigh* This game will drive me nuts : let's say the CPU has a Harpie's Feather Duster in hand, and you have a trap in play. You play a monster. The CPU activates Harpie's Feather Duster on his turn. Everything is all right, right ? '''NO !''' If you don't play a monster and leave your field empty, the CPU will attack without activating Harpie's Feather Duster because the check for an opponent trap card is made AFTER the check for "does my opponent have a monster ?" when deciding whether or not to attack ! '''Update 4 :''' Found the remnants of a debug mode. [http://oldgamehacking.com/?p=576 There is more than the sound test and chara viewer which were found earlier.] '''Update 5 :''' I found a major glitch, filling the player's deck with some data. Might be useable in a TAS. [http://www.pixenli.com/images/1404/1404218465065322500.png aaaaaaaaRRRRRRRR] [http://www.pixenli.com/images/1404/1404219451087594900.png aaaaaaaaRRRRRRRR] [http://www.pixenli.com/images/1404/1404219502045734500.png aaaaaaaaRRRRRRRR](Attacking with this monster causes the game to freeze, as it doesn't have a proper ATK, even if 500 is shown)  
* [[Yu-Gi-Oh! Dark Duel Stories]] : Currently working on the stupid AI discarding Tremendous Fire instead of activating it. What could possibly go wrong ? Someone obviously didn't debug there. The subroutine used to discard a Tribute monster while the hand is full is being called with a hand consisting of one spell card because the conditional statement is utterly fucked up. '''Update 2 :''' Guess what ? The AI choose to discard Swords of Revealing Light instead of activating it if there's no monsters on board ! '''Update 3 :''' *sigh* This game will drive me nuts : let's say the CPU has a Harpie's Feather Duster in hand, and you have a trap in play. You play a monster. The CPU activates Harpie's Feather Duster on his turn. Everything is all right, right ? '''NO !''' If you don't play a monster and leave your field empty, the CPU will attack without activating Harpie's Feather Duster because the check for an opponent trap card is made AFTER the check for "does my opponent have a monster ?" when deciding whether or not to attack ! '''Update 4 :''' Found the remnants of a debug mode. [http://oldgamehacking.com/?p=576 There is more than the sound test and chara viewer which were found earlier.] '''Update 5 :''' I found a major glitch, filling the player's deck with some data. Might be useable in a TAS. [http://www.pixenli.com/images/1404/1404218465065322500.png aaaaaaaaRRRRRRRR] [http://www.pixenli.com/images/1404/1404219451087594900.png aaaaaaaaRRRRRRRR] [http://www.pixenli.com/images/1404/1404219502045734500.png aaaaaaaaRRRRRRRR] (Attacking with this monster causes the game to freeze, as it doesn't have a proper ATK, even if 500 is shown)  
* [[Yu-Gi-Oh! World Championship 2006]] : Currently working on the banlist password system.
* [[Yu-Gi-Oh! World Championship 2006]] : Currently working on the banlist password system.

Revision as of 12:58, 1 July 2014

To Do List

  • Pokémon Stadium : Currently working on the AI script
  • Pokémon Stadium 2 : Working around an infinite loop at startup when toying with Base Stats. Update : doesn't happen on a real n64. idk what's wrong with project64.
  • Pokémon TCG : Currently working on the AI of some CPU opponents being unable to use Pokémon Breeder for some weird reason when playing a modified deck.
  • Skies of Arcadia : Currently working on an editor for enemies, spells and special attacks.
  • Yu-Gi-Oh! Dark Duel Stories : Currently working on the stupid AI discarding Tremendous Fire instead of activating it. What could possibly go wrong ? Someone obviously didn't debug there. The subroutine used to discard a Tribute monster while the hand is full is being called with a hand consisting of one spell card because the conditional statement is utterly fucked up. Update 2 : Guess what ? The AI choose to discard Swords of Revealing Light instead of activating it if there's no monsters on board ! Update 3 : *sigh* This game will drive me nuts : let's say the CPU has a Harpie's Feather Duster in hand, and you have a trap in play. You play a monster. The CPU activates Harpie's Feather Duster on his turn. Everything is all right, right ? NO ! If you don't play a monster and leave your field empty, the CPU will attack without activating Harpie's Feather Duster because the check for an opponent trap card is made AFTER the check for "does my opponent have a monster ?" when deciding whether or not to attack ! Update 4 : Found the remnants of a debug mode. There is more than the sound test and chara viewer which were found earlier. Update 5 : I found a major glitch, filling the player's deck with some data. Might be useable in a TAS. aaaaaaaaRRRRRRRR aaaaaaaaRRRRRRRR aaaaaaaaRRRRRRRR (Attacking with this monster causes the game to freeze, as it doesn't have a proper ATK, even if 500 is shown)
  • Yu-Gi-Oh! World Championship 2006 : Currently working on the banlist password system.