Jump to content

Fuse294

Members
  • Posts

    314
  • Joined

  • Last visited

Posts posted by Fuse294

  1. Create a new .zip file and then create and copy the following folders into it (it's better to make fresh ones as they are empty).

     

    ext_data then into that copy a folder called npcs then inside THAT folder place a .npc file with the rocks data into it, feel free to alter the first line of the text before the personality data (before the {) to say rubble to avoid conflicts, then make sure to change the zip to a .pk3 which can be done by a simple rename (either with pakscape or 7-zip which I use once a file is open and I go up a level)

     

    Alternatively for the copy part place the folders into each other BEFORE moving them to the .ZIP.

  2. I don't think it would be overly hard to copy the .npc file for it.

     

     

    rocks
    {
    playerModel rocks
    weapon WP_NONE
    scale  100
    health 100
    snd jawa
    sndcombat jawa
    reactions 3
    aim 1
    move 3
    aggression 3
    evasion 1
    intelligence 5
    rank crewman
    playerTeam TEAM_NEUTRAL
    enemyTeam TEAM_FREE
    class CLASS_KYLE
    yawspeed 90
    walkSpeed 55
    runSpeed 150
    dismemberProbHead 0
    dismemberProbArms 0
    dismemberProbLegs 0
    dismemberProbHands 0
    dismemberProbWaist 0
    }
    LucyTheAlien likes this
  3. Actually there is a way around it, simply replace the code in the .sab file like so:

    Kyle
    {
    name "Katarn"
    saberType SABER_SINGLE
    saberModel "models/weapons2/saber/saber_w.glm"
    soundOn "sound/weapons/saber/saberon.wav"
    soundLoop "sound/weapons/saber/saberhum4.wav"
    soundOff "sound/weapons/saber/saberoff.wav"
    saberLength 40
    saberColor blue
    }
    single_1
    {
    name "Katarn"
    saberType SABER_SINGLE
    saberModel "models/weapons2/saber/saber_w.glm"
    soundOn "sound/weapons/saber/saberon.wav"
    soundLoop "sound/weapons/saber/saberhum4.wav"
    soundOff "sound/weapons/saber/saberoff.wav"
    saberLength 40
    saberColor blue
    }

    Doing this will cause the altered hilt to override the assets hilt by replacing "Arbiter" for example with the model for Gorc.

     

    For increased size it has to be uploaded server size as the length has to be altered as shown below for it to work at a longer length, otherwise it will always be 40.

    saberLength 40
    saberLength 52

    One example is the variation of Desanns hilt from the others

    Desann
    {
    name "Retribution"
    saberType SABER_SINGLE
    saberModel "models/weapons2/saber_desann/saber_w.glm"
    soundLoop "sound/weapons/saber/saberhum2.wav"
    // saberLength 48
    saberLength 64
    saberRadius 6
    saberColor red
    notInMP 1
    }
    The same works in reverse, you can make them shorter for smaller characters, if the server has a supported modelscale file that is enabled so you can be a Jawa that is the correct height:
    Training
    {
    name "Training"
    saberType SABER_SINGLE
    saberModel "models/weapons2/saber_reborn/saber_w.glm"
    soundOn "sound/weapons/saber/saberon.wav"
    soundLoop "sound/weapons/saber/saberhum4.wav"
    soundOff "sound/weapons/saber/saberoff.wav"
    saberLength 32
    saberColor yellow
    notInMP 1
    }
    

    Altering the name so you see it is safe as it will only register on your client, everyone else would see the standard Arbiter hilt, hope this helps.

    Smoo likes this
×
×
  • Create New...