-
Notifications
You must be signed in to change notification settings - Fork 58
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
Build issue #10
Comments
Sounds like the rst sections are stepping on each other. Take a look at the top of home.asm |
Can I ask why you are reapplying these changes to a clean pokered repo? This repo was last synced with pokered on April 13th |
I figured it out. I needed to comment out a few lines of the link file. And to answer your question, I'm trying to reapply it so as to try and better understand how it all works. |
This really isn't an issue with pokered-gbc itself, but with applying the GBC stuff on top of regular RBY. Can this be closed? |
Ah, apologies. Yes. Sorry about that. I wasn't sure how best to post such a
question. I appreciate your feedback!
…On Wed, Dec 4, 2019 at 3:51 AM Daniel Harding ***@***.***> wrote:
Closed #10 <#10>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#10?email_source=notifications&email_token=ABN63HLUEU7BX7JRQGZYCFLQW3BE3A5CNFSM4ILEHFMKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVH4ARIA#event-2851604640>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABN63HP6R4DFDH2RYG3CCMLQW3BE3ANCNFSM4ILEHFMA>
.
|
No worries. I don't mind you using the issues for questions about this project |
Can I PM you if I have modding questions unrelated to the project? I've got a mod I'm trying to do and I've hit a snag |
Before I get into this... let me say, I'm trying to port the changes into a fresh pokered disasm. I seem to have almost everything accounted for but I'm getting an odd error:
error: Trying to go to a previous address (0x0010 to 0x0008)
Have you ever seen this when putting this together?
The text was updated successfully, but these errors were encountered: