Conversation Between cooley and score_under
1 to 15 of 38
  1. cooley
    September 23rd, 2009 1:26 PM
    cooley
    Oh, wow. Thanks! You saved me a bunch of time, I'll try to test it out. After I finish homework.
  2. score_under
    September 20th, 2009 8:42 AM
    score_under
    You might like my new update ;) Dynamic support sort-of works in Gold (but I haven't tested it very extensively, to be honest) use :labels for 2-byte and @blocks for 3-byte.
    An example I used to test the compiling:
    #dyn findfromgold
    #org @test
    loadfont
    2writetext :test
    yesorno
    2ptjump :asd
    :test
    = Testing\nLol\e
    :asd
    #3ptr @zzzz
    #org @zzzz
    3writetext @asdf
    3jump @yyyy
    #org @yyyy
    end

    #org @asdf
    = Message 2\e
  3. cooley
    September 9th, 2009 5:43 PM
    cooley
    Well.. There's Crystal Map, if you didn't already know. But other than that, I don't think there is any other one. I think yomamama is trying to make one, so ask him for updates to it :)
  4. score_under
    September 9th, 2009 1:17 PM
    score_under
    That's pretty much what #dynamic does... XD
    I could try to make something where you use labels for 2-byte calls and jumps, etc, which means you use labels for intra-section calls (2byte) and @-offsets for inter-section calls (3byte)... but no promises ;)

    Oh, and do you know of any Crystal mapping program?
  5. cooley
    September 7th, 2009 12:46 PM
    cooley
    I will try to create something that helps make scripts in PKSV. It is kind of like dynamic, except there's no "@" symbol.

    #org 0x1225A0
    faceplayer
    loadfont
    2writetext 0xZZZZ
    closetext
    loadmovesprites
    end

    #org 0xZZZZ
    = This is some random text\e

    So once you've typed your script in it, you hit okay and, it should be able to replace ZZZZ with an offset that is availble, like in this case 0x1225A9.

    To me, this will be damn hard to do, but I'll try to. I just wanted to know if you think it's a good idea, or if you want, you can do it. Since you enjoy coding(hopefully) and have much more experience than I do.
  6. cooley
    July 14th, 2009 11:12 AM
    cooley
    Oh, okay. Yeah, you should add a editor (of the tables you mentioned) to PKSV, especially the sethealingplace one ;)

    I'm sure once beginners advance, they're going to want to know how to do things, and the more things you have available to them, the more people will start to use it :D
  7. score_under
    July 14th, 2009 6:10 AM
    score_under
    I'm attempting working on one with a friend - he's doing most things, but I'm doing things like reprogramming PKSV (and making it user-friendlier in places too) and researching tables (I've found, for FR and LG, the pointers to the move tutor tables (setvar 0x8005 [table index], special 0x18D) and the sethealingplace map tables. Now I wonder if I can implement any of these into PKSV...)
  8. cooley
    July 13th, 2009 1:22 PM
    cooley
    Wow, thanks a bunch!
    ----
    Have you ever considered making a hack?
  9. score_under
    July 13th, 2009 9:56 AM
    score_under
    Yeah, I gave up when I couldn't find any data about the map offsets or their many formats and intricacies...
    Anyway, thanks for reminding me, here's my comments on the subject (literally)
    //207500 (20F500) is jap. codec (font w/ is 128, char w/ 16, font h/ 16)
    //1EAF02 (1EEF00) is eng. (small) codec (font w/ 8, char w/ 8, font h/ 16)
    //1F3100 (1FB100) is eng. (norm) codec (font w/ 16, char w/ 16, font h/ 16)
  10. cooley
    July 12th, 2009 6:21 PM
    cooley
    Oh, well it's okay. wait so does that mean you're not making an HLE?
  11. score_under
    July 12th, 2009 12:06 PM
    score_under
    I think I did a while back... but I've probably forgotten it again, haha.
  12. cooley
    July 9th, 2009 5:34 PM
    cooley
    Did you ever find the FireRed font offset?
  13. cooley
    June 26th, 2009 6:34 AM
    cooley
    Yes, I understand..Never knew about that XSE "bug". But good luck with the new features ^_^
  14. score_under
    June 25th, 2009 11:18 AM
    score_under
    Sort-of, but do you know the difference between XSE-style and PKSV-style #define? XSE's #define is a find/replace operation on the whole script, while PKSV's #define adds it to a list of defined values and waits until it encounters a token exactly like it. That way, if you do this:
    #define food 0x3
    messagebox @needfood
    In PKSV, this would work normally (as if you didn't #define it, because you never used it) while in XSE this would rename "@needfood" to "@need0x3" ;)
    Anyway, I'm going to get to work on labels, text, and pointer scanner.
  15. cooley
    June 25th, 2009 7:31 AM
    cooley
    Ahh I see... So the linkedlist is kind of like a "#define"?

    btw, I'm using the newest PKSV..IT ROCKS!!! :D