PurpleOrange
still don't know what I'm doing
- 367
- Posts
- 11
- Years
- Littleroot Town (UK)
- Seen Mar 14, 2025
There's no error, the button is greyed out and i can't do Anything.
It says [Sister 1.rbc]
have you opened your ROM in xse?
There's no error, the button is greyed out and i can't do Anything.
It says [Sister 1.rbc]
wait, i have to do that? well thanks!
Ok, I've compiled it and copied and pasted it, but the character won't say anything.
#dynamic 0x800000
#org @start
msgbox @1
boxset 0x2
end
#org @1
= Munch Munch\n(Leave me alone,/n I'm eating!)
no, lots of errors. lol, I'm really bad at this :p
This is weird.
When I compile this:
#dynamic 0x800000
#org 0x13580
msgbox @Sister1 0x2
end
#org @Sister1
= Munch Munch /n(I'm trying to eat!)
get this: 8001AB
But when I copy it into advance map: 8001AB80
When I open the script I get this;
'---------------
#org 0x1AB80
nop
copyvar 0x80 0x1840
nop1
giveegg 0x2001
gotostd 0x40
#dynamic 0x13580
#org @start
msgbox @Sister1 0x2
end
#org @Sister1
= Munch Munch /n(I'm trying to eat!)
get this: 8001AB
But when I copy it into advance map: 8001AB80
You forgot to put 0xFE at the end of the movement string.What exactly is it that I'm doing wrong?
Spoiler:
#dynamic 0x805110
#org @main
lockall
(lots of movement)
msgbox @1 0x6
cry 0x97 0x0
applymovement MOVE_PLAYER @excl
waitmovement 0
special 0x113
applymovement 0x7F @cmove1
waitmovement 0
special 0x114
msgbox @2 0x6
releaseall
setvar 0x4036 0x1
end
#org @1
= [.]\n[.]\l[.]
#org @2
= camera test
#org @cmove1
#raw 0x11
#raw 0x11
#raw 0x11
#raw 0x10
#raw 0x10
#raw 0x10
#raw 0xFE
Well that's a new one:
Spoiler:![]()
![]()
never mind, I fixed it.
The red is when I talked to her, but I just needed a @start in my script :p
comparefarbytetobyte allows you to compare any offset in the rom and see if it is the value that you want, for example at 0x80861CD in a hex editor for my game, the byte is 0xB5.
I can compare but the thing is I don't know how to write, if possible.
I read that writebytetooffset is used for general internal memory and internal display memory, and I also tested it and it won't work.
So what I'm asking, is there a command that allows the hacker to change a byte at an offset such as 0x80861CD to a different value, even if it is temporary?
The 0x08000000 - 0x09000000 area is the ROM, which means it's read-only; it can't be edited at runtime. I'm not sure what you're trying to do, but maybe try buffering it into the RAM and use it from there instead?