Change Actor Graphics on Equip patch request

● ARCHIVED · READ-ONLY
Started by kingkoopa300 7 posts View original ↗
  1. kingkoopa300
    #1 Source
    Hello, i'm again lost I've tried every Equipment Graphic script out there. This one is Simple and would work best with my battle scripts. There's one problem it's not compatible with my !$ sprites. I would use common event script to change graphics on equipment but i plan on have lot's of playable characters and equipment so 999 is the limit in common events and it will not be enough (I think). It would be nice if there was a way to get Large "!$filename.png" to work with this script.​
     ​
    This is the script i'm talking about​
     ​
    its' awesome even uses $file's but not !$.​
     ​
    Victor Visual Equip is very good to, but it layers on sprites not change them which is not what i need. I could see using this script in my Action RPG project but my heart is set on Turn-Based for now.​
     ​
    I know i could water-down my ideas use $ format instead but i already got 60 layers in Photoshop finished using !$ format​
    i love the sprites I've created and i don't wanna start from scratch again. And Please forgive me Pro Scriptwriters i know i'm a newbie and this is my first game ever so i got no clue about Ruby yet.​
     ​
  2. Shaz
    #2 Source
    I've moved this thread to RGSSx Script Support. Please be sure to post your threads in the correct forum next time. Thank you.


    Do you NEED the ! in the filename? Do you know what it's for?


    ! at the start of a file name indicates that the sprite is not to be offset by 4 pixels when drawing (without it, the sprite is moved up 4 pixels from the standard grid). It's usually only used for non-moving things that you want to align perfectly with the grid - like doors. It has nothing to do with how large your spritesheet is or how many characters it contains.


    However, try changing this line:

    Code:
    GRAPHIC_EQUIP = /<ge[:]?\s*(\d+)\s*[,]?\s*([$]*\w+)?\s*[,]?\s*(\d+)\s*>/i
    to this:
    Code:
    GRAPHIC_EQUIP = /<ge[:]?\s*(\d+)\s*[,]?\s*([!$]*\w+)?\s*[,]?\s*(\d+)\s*>/i
  3. kingkoopa300
    #3 Source
    Sorry doesn't work... I wish i could figure it out
  4. kingkoopa300
    #4 Source
    Well this script here fit's my needs might fill up my common events but beggars can be choosers ;) Thanks anyways Shaz

    Hime's Equip Event
  5. Engr. Adiktuzmiko
    #5 Source
    I know i could water-down my ideas use $ format instead but i already got 60 layers in Photoshop finished using !$ format
    I agree with Shaz here, there shouldn't really be a difference between using $ and $! as the ! part is just for adjusting the 4 pixel offset.

    Do you NEED the ! in the filename? Do you know what it's for?


    ! at the start of a file name indicates that the sprite is not to be offset by 4 pixels when drawing (without it, the sprite is moved up 4 pixels from the standard grid). It's usually only used for non-moving things that you want to align perfectly with the grid - like doors. It has nothing to do with how large your spritesheet is or how many characters it contains.
  6. kingkoopa300
    #6 Source
    !

    Engr. Adiktuzmiko said:
    I agree with Shaz here, there shouldn't really be a difference between using $ and $! as the ! part is just for adjusting the 4 pixel offset.
     
    Still doesn't work with my custom sprites, my characters are 238x428 pixels. i think that's why this won't work. Good to know about the difference between !$ and $ thanks Shaz and Engr.  $files work fine just the one's i've created don't work, weird :(  i'll stick with Hime's Equip event for now... i'll try to IM Jeneeus Guruman maybe he can shed some light on what i am doing wrong, but right now i don't feel like searching for away to chat with him. Thanks again for your help
  7. Engr. Adiktuzmiko
    #7 Source
    maybe his script doesn't support anything larger than the default or something (I didn't take a look at it). Anyway, since you're changing the sprites rather than add to it then I guess Hime's script would be sufficient. You could possibly use a single common event for it, though it will be very long :)