Skip to content
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

[Feature request] Choose padding byte while using rgblink's overlay feature #1394

Closed
marcrobledo opened this issue May 12, 2024 · 0 comments · Fixed by #1395
Closed

[Feature request] Choose padding byte while using rgblink's overlay feature #1394

marcrobledo opened this issue May 12, 2024 · 0 comments · Fixed by #1395
Labels
enhancement Typically new features; lesser priority than bugs rgblink This affects RGBLINK
Milestone

Comments

@marcrobledo
Copy link

According to documentation:

-p pad_value, --pad pad_value: When inserting padding between sections, pad with this value. Has no effect if -O is specified. The default is 0.

It is not possible to set the padding value if usign the --O/-overlay feature.

It makes sense since the overlay file is already assembled and has data on it. However, I miss this feature when expanding the ROM.
I'm working on a ROM hack that needs to switch to a new bank, read a byte (which will be the OAM attribute) in the current [hl] then return to the original bank. It would be great if I could choose the initial value to be $00 of those new banks instead of doing my own workarounds.

@Rangi42 Rangi42 added enhancement Typically new features; lesser priority than bugs rgblink This affects RGBLINK labels May 13, 2024
@Rangi42 Rangi42 added this to the v0.8.0 milestone May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Typically new features; lesser priority than bugs rgblink This affects RGBLINK
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants