Jump to content

El Excellente

Member
  • Posts

    1061
  • Joined

  • Last visited

Posts posted by El Excellente

  1. On 24.7.2017 at 2:11 PM, kipper said:

    also to add to this, if you're able to provide one sample model with all the currently available bodygroups/skins that'd be super useful if only for testing stuffs

    here you go, the old wip female 01 model. i already zipped and uploaded it before i finalized it but you'll get the gist

    i've included a few textures too

     

    https://cl.ly/2f2v162D4735

     

    since the models are now all completely done, i will make an excel table for you with all the bodygroups.

    ie. set a medics head bodygroup to 4 if he does /beret etc

  2.  

    Hi, since I'm on loa I just skimmed through your post and saw a few things I could give you some quick insight to

     

     

    Quote

    However, this rationale does not promote MIs, line troopers especially, to take risks, distinguish themselves, or allow for anything but pre-determined outcomes. I also understand that in some situations authoritative action is necessary and that what might have been explained at the beginning of a mission will be tedious and obnoxious to explain to players who just connected.

     

    That's the point. If you reach the point where your Trooper distinguishes themself and does something out of the ordinary, he is susceptible to harsher CK rules. He cannot be a ordinary Trooper out of the blob who gets NLRd when he tries to lasso a tanker bug.

     

    Quote

    Default rule that /rolls are allowed when in any and all PvP situations unless otherwise stated at the beginning of a mission - in line with the rules on this thread: http://forums.starshiptroopersrp.net/index.php?/topic/63-how-permacharacter-kills-work-on-sstrp/. Maybe there could be some sort of indicator that /rolls are not allowed during a certain mission. Notice at the beginning of the mission is the main issue.

     

    Mind you that very thread was created for the sake of sparring - only later we started using it for fighting seperatists or using the roll command for other stuff entirely. Noting something at the very beginning of the mission is always an issue; either they don't listen, they forget or they weren't even there.

     

     

    Quote

    Rolls being incorporated into a /me so that it is easier to distinguish what the specific roll is for, this may be useful when there are a lot of things going on.

     

    I think that's a good idea and you're totally free to do that.

     

    12 hours ago, Mack said:
    • Less passive aggressiveness from admins when someone does a /roll or tries to be different, its pretty negative to begin with and simply urges people to conform. It is certainly annoying for someone to use /report repeatedly when their issue isn't addressed but then again when there is no indication it is being considered or responded to - are we simply to let it go or try again, we have no idea without a response. There is no getting around how it might be irritating, particularly when there are things occurring all at once.

     

    If you're unsure whether your report is being handled, report it again. Usually we take notice of reports but often are unsure ourselves how the mission leader would like to handle certain things. That's why there's always a small delay unless there's multiple admins running a mission (while yes, there often are many admins helping, we often only know a few parameters which we're told to handle because we joined late or reasons).

     

  3. Hello

     

    I'm gonna split this into two parts, one for kipper and the other for the admin team to discuss.

     

    Firstly, Mobile Infantry models are going to come with a lot of skins and bodygroups. Faces will be skins. Bodygroups will be equipment such as belts, backpacks and radio, ie. they will cover the whole body. My suggestion here is to have a model selector similar to the render menu in gmod (right click on any model in Q-menu - edit this icon). Zoom in on the face when selecting skins with the possibility to rotate the head, zoom out (view the whole body) to select bodygroups with the possibility to rotate.

     

     

    Secondly - our offduty and onduty models are two seperate models and I don't know how exactly we will handle this, but I assume I'm going to pitch all the custom heads and head variants to deadeye so he can incorporate them, meaning all the heads we have for the MI, we have for the offduty variant, too.

     

    The issue I see with this is that it's two models - therefore I suggest saving both models to the sql (or whatever database we're using) upon creation. Ie. I create a male14 with skin 9, bodygroup 1 2, 2 4 etc., it spawns me with the offduty model of male14. When I type /mi or whatever, it loads the thing I entered upon character creation (with the possibility to edit it later of course)

     

    I hope this was somewhat comprehensible. I am more coffee than man.

×
×
  • Create New...