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
The change in the above commit is likely what broke it. I may try to fix it myself but it's been ages since I scripted and Royal Oppression is a relatively ancient and weird card. If it's something simple I can probably get it done. [Edit: Nope, the script is too complicated because of the either player SS3, I cannot fix this myself without a lot of pain. I also don't know what the above commit was intending to fix so I don't know if reverting is a good option or not.]
The text was updated successfully, but these errors were encountered:
Add: Koishipro reports the error as on line 15, the aux.NegateSummonCondition line.
Was the aux function changed? The old functioning script does not use this aux function so it may be incorrect to use since Royal Opp's activation condition is fairly strange.
Royal Oppression is nonfunctional on production with error message "Parameter 2 should be 'Function'."
0b7ea09
The change in the above commit is likely what broke it. I may try to fix it myself but it's been ages since I scripted and Royal Oppression is a relatively ancient and weird card. If it's something simple I can probably get it done. [Edit: Nope, the script is too complicated because of the either player SS3, I cannot fix this myself without a lot of pain. I also don't know what the above commit was intending to fix so I don't know if reverting is a good option or not.]
The text was updated successfully, but these errors were encountered: