-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Partial fix for the innocent_witches branch #123
base: innocent_witches
Are you sure you want to change the base?
Partial fix for the innocent_witches branch #123
Conversation
…mon obfuscation tactics.
…ow we use those to recognize them as well
…de so now use the presence of a linenumber attribute on it to detect if it was unconditional
Innocent witches
… prevent rpyc modification shenanigans.
heya, figured I'd reply to this after like 3 years 😓 I think the years of changes have made this pull request a bit hard to read, and the branch has diverged quite a bit as well. I'm also not sure how many fixes here have mirrored ones in the repo already right now. I think we'll have to separate the merged in commits from the ones that actually handle the game specific things to make sense of this and move that branch forward, so I don't really see a chance of this pull landing in this format. That said, I'll keep it open for whoever needs this right now. |
Improves #122
I managed to solve the
FakeUnpicklingError: <class 'store.LanguageCases'> was instantiated with unexpected arguments (u'Hermione',), {}
error I got when unrpycing Innocent Witches 0.6.5f.I did kinda like the ELSE_COND fix, but my fix can probably be simplified.
Next step is solving the
Unknown AST node: <class 'store.ATL.RawUse'>
for RawIf, RawUse, RawChoice, RawRepeat, RawAnimation, RawBlock and (surprisingly) renpy.ast.PostUserStatement.That last one may come from renpy updates and as such, may deserve an update in master.