blr & bne

Can anyone explain the b, blr, bne+ and bne ASM instructions? I'm having a problem clearly understanding them.

b means "Branch always". It is used to jump to some offset and continue executing from there using a branch label to mark the position (or you calculate the offset).

blr means "Branch to link register". It returns to the previous caller (it´s the address from the link register).

bne+ means "Branch if not equal". As soon as the previous condition is "not equal", branch will be taken and execution continues where the branch label set (as you can imagine there are more different branches to use)

bne- basically does the same thing. The + and - may mean that the one is signed and the other unsigned. Random guess. I never cared about that difference, it must be little and I always used bne- on my codes. I´ve seen people using bne+ which was interchangeable when I checked.

---

Good list:
b ("Branch always")
beq- ("Branch if equal")
bne- ("Branch if not equal")
bgt- ("Branch if greater than")
blt- ("Branch if less than")
bge- ("Branch if greater or equal")
ble- ("Branch if less or equal")
blr ("Branch to link register")
nop ("Branch never")

There´s more, but I don´t think you´ll need many more.

Mhh this is interesting, I have heard the word ASM; but I would like to know more about it, have you made any tutorials?

Sincerely

Thank You Bully. You saved the day again.

@Xylon - ASM is a programming language used in the game. By editing the way certain functions work or inserting your own, you can do far more than simply changing a value for health or something of that nature. In my experience it actually seems to be the best way to make good codes that are glitch free.

I know what it is, but I would like to learn it to understand it a littlebit more.

Sincerely

Do you understand what a "breakpoint" is and how to use them? Maybe I will make a tutorial for making a simple ASM code.

This would be GREAT. I have heard about Breakpoint but I do not know it in detail...In case of that I would like to learn this...

Sincerely

Welohabi wrote:In my experience it actually seems to be the best way to make good codes that are glitch free.

You got it
Using ASM mostly makes up perfect and glitch-free codes. Well, if you fully know what you´re doing obviously. Many cool things can NOT be done without breakpoints...

---

Addition:
the + and - from branches are "branch predictions". Minus means it´s less likely to branch and plus that it´s more likely. The compiler is mostly good enough for figure itself. There´s therefore no need to care about it... (source: megazig from WiiRd)