Reaction score

Profile posts Postings Media Albums About

  • Most important thing first, you can keep playing Metroid (it's a girl!) until whenever.
    it's just a purple thing that stands there. Awesome, I know. You can make the image as large as u want to fit the spikes, basically it just stands their until you shoot it, then it goes all prickly and defensive. your choice what kind of spikes to use.

    And as a weird side note, could you give the behemoth ram horns?
    And as for the gig, I need to find a file uploader that can upload a midgetbyte first. :(
    1&2) Sweetzies*
    1+2) - If you can balance a gigabyte of cave story related stuff on your head, kudos to you. I don't think I could. :(
    22?) - It's not tutu hard, I just stink at dresses.

    *basically, here's what I wish for you to draw, but angrywithspikes.

    thanks a mayan, I can giveth you that gig of stuff if you want, but you need some serious sorting powers if you ever want to find anything.
    - lacy
    2 Qs;
    first, you're awesome at pixel art, right?
    second, could you do an ikkle bit of dat for me?
    nonsensical third question: if I sent you a gig and a bit of asm notes, mods, plots, etcetera, would you do something interesting with it?

    also, your mod HARD.
    I beat the first part that is all green, and then their was a second part I got halvzies thru and died. :(
    I never really got why that cavern was their tho...

    A rain of blood.

    "Each day, we will spill their blood till it rains down from the skies."

    I Think I might have killed the world.
    But anyway, I'm better off alone.

    A rain of blood.

    I Think I might have killed the world.
    But anyway, I'm better off alone

    I'm better off alone...

    "Each day, we will spill their blood till it rains down from the skies."
    Noxid said:
    The C7 is the MOV command
    Oh, duh, now I feel silly.
    I don't know why I decided to ignore the commands in hex. {I blame lack of sleep}
    Noxid said:
    and the next BYTE seems to be the type of MOV command we're dealing with, then either the next BYTE or DWORD is for how far off the register to go, and the last DWORD is the actual value being MOV'ed
    This is so much more confusing using something like Translhextion....
    But I see what you mean with Olly.
    Not really sure about that...
    Assuming 40F9D5 simply becomes x0F9D5 for Translhextion, the numbers that came up look nothing like that.
    Not sure if that's how the offsets change between the two, though. Just a guess, but the numbers seem to be in a pattern, like they should be for frame rects.
    Each offset {
    Well, I tried almost a dozen} always started me at a C7 , too, so it doesn't seem like I'm randomly jumping around.
    Noxid said:
    Rects are somewhat difficult to visualise, but think of them as defining four infinitely extending lines; the line display_L draws a vertical line (for the left side) and everything to the left of that line is disregarded. display_U draws a horizontal line, and everything above is disregarded. Continue this logic with the other two and what you're left with is a rectangular area.
    That's just about exactly how I imagined them...
    Noxid said:
    As for what you've mentioned, after a bit of searching I found it in one of rune's old tutorials. The proper order is, in fact, LURD, and I'm not sure why he put them in LRUD order (possibly to group them by x/y, I dunno). Everywhere else in the compendium where it lists the actual offsets of these rects they're properly ordered as far as I can see.
    Just my luck to see only that set, eh.
    {Really, I was being lazy/rushing and just used Find until I came across it}
    Noxid said:
    Finally, when you're dealing with rects and such in the .exe, remember that all the numbers are hex; hence, 16 = 10, 32 = 20 and so forth.
    Oh, I know. I just listed them in that way because it's how Rune had all of the title screen rects listed.

    Anyways, thanks for clearing that up for me.
    OK, this probably isn't a biggy, but it had me pulling hairs for awhile...
    I was trying to figure out how Frame Rects work, and I saw something listed in your Assembly Compendium.
    Specifically, it says the four numbers should be in this format:
    Display_L: left side of the display rect
    Display_R: right side of the display rect (NOT width)
    Display_U: top side of the display rect
    Display_D: bottom side of the display rect (NOT height)
    Well, I spent an hour or two trying to figure out why the game would keep displaying nothing, when I noticed that the other frame rects in the code didn't follow that rule. So I tried something else.
    To display the left standing animation of Quote, it should be 000 016 000 016, right? {Left Right Top Bottom}
    That got me blank, so I tried 000 000 016 016. {Left Top Right Bottom} It displayed perfectly.
    I even tried 0000 0064 0016 0080 to display an animation that I added to an enlarged version of the MyChar.PBM, and it worked. {According to the Compendium, it should've been 0000 0016 0064 0080}

    I'm thinking the list wasn't suppose to be taken in that order, but I didn't see anything else in the little article that told how the EXE accepted them.
    Unless, do the Rects go in an order akin to the game's directions? {I just now literally noticed that}
    I mean, in the TSC.txt the directions are listed as:
    0000 Left
    0001 Up
    0002 Right
    0003 Down

    I'm rather confused at the moment....
    You should join me in creating festive facepics, then. :D {On the corresponding holidays, of course}
    I've done one for Halloween, Christmas, and {Inter}National Speak Like a Pirate Day, so far.
    I'm not sure if I'll do a Valentines one or not, though...
  • Loading…
  • Loading…
  • Loading…
  • Loading…