You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I played around with some of the stuff you wrote here - compiled a map of string/ydcs.
But I have a goal/idea that would be interesting - a difficulty mod. Basically force npcs to use their most difficult deck without banned cards right from the start. This game is way too easy and this would be a step in the right direction.
I don't think we can edit the game logic for this, but we could edit the decklists 01 and 02 for each duelist to their 03 decklist.
Prob logic would be to map ygc to deck string and then create a config/json file to what declist ids to be replaced by what. Read the config file and then patch decklist in eboot.bin with proper change so it wont crash.
I could almost do this, but I dont know how to patch the ygc back into eboot bin/modify it so it points to the modified ygc file outside. In the workflow you provided where ygc files are unpacked.
The text was updated successfully, but these errors were encountered:
I played around with some of the stuff you wrote here - compiled a map of string/ydcs.
But I have a goal/idea that would be interesting - a difficulty mod. Basically force npcs to use their most difficult deck without banned cards right from the start. This game is way too easy and this would be a step in the right direction.
I don't think we can edit the game logic for this, but we could edit the decklists 01 and 02 for each duelist to their 03 decklist.
Prob logic would be to map ygc to deck string and then create a config/json file to what declist ids to be replaced by what. Read the config file and then patch decklist in eboot.bin with proper change so it wont crash.
I could almost do this, but I dont know how to patch the ygc back into eboot bin/modify it so it points to the modified ygc file outside. In the workflow you provided where ygc files are unpacked.
The text was updated successfully, but these errors were encountered: