Author Topic: Output Event - SetAppearance(Setbodyparts - setbodycolors) V4  (Read 18769 times)

I've used the same appearance since Vanilla.  No, it doesn't get boring.  I chose an appearance I liked and my preference for it hasn't changed, so why should I pick something different?  Anyway, that doesn't have much to do with this topic.  I suppose you could PM me if still have issues with my wardrobe.

ow :( i wasn't attacking you or nothin'

anyways done talking here yeah, rot doesn't want this in his thread

Gikon, shut up, Trader is right, you are just mad because he made something that also changes the look of a player and he is getting feedback.

Yours is no better, it just changes color, what good does that do?

This does that AND appearance (i can say it changes color because if you recolor your avatar and all.)   Just go away.  And way to advertise your mod here, that is not cool, you should never advertise your mod/content somewhere else being like "Yeh, here's mine, it owns yours, kthnxbai!"

Gikon, stop being a little bitch.

On another note, I think this Output event should require to be in a minigame, or perhaps trust while outside of one.

Gikon, shut up, Trader is right, you are just mad because he made something that also changes the look of a player and he is getting feedback.

Yours is no better, it just changes color, what good does that do?

This does that AND appearance (i can say it changes color because if you recolor your avatar and all.)   Just go away.  And way to advertise your mod here, that is not cool, you should never advertise your mod/content somewhere else being like "Yeh, here's mine, it owns yours, kthnxbai!"
I was not advertising you loving handicap. I was clearing stating I already DID the color output and mine does not have the disadvantages that HIS DOES.
Now go loving die in a hole jirue-cigarette.
Hows that for being pissy?  :cookieMonster:


Good job Rotondo, encore.

This looks great.

Just a few suggestions/changes:

Code: [Select]
function FxDTSBrick::onactivate(%brick,%player,%loc,%rot)
{
%player.client.lastbrickactivated = %brick;
Parent::onactivate(%brick,%player,%loc,%rot);
}
function FxDTSBrick::onplayertouch(%brick,%player,%loc,%rot)
{
%player.client.lastbrickactivated = %brick;
Parent::onplayertouch(%brick,%player,%loc,%rot);
}

Idea: Package fxDTSBrick::processInputEvent(%brick,%input,%client) for this instead? Then it'll be compatible with every input event.

Quote
      %brick.hip = getword(%save,%hn++);
Quote
servercmdupdatebodyparts(%client,%brick.hat,%brick.accent,%brick.pack,%brick.secondpack,%brick.chest,%brick.hipt,%brick.lleg,%brick.rleg,%brick.larm,%brick.rarm,%brick.lhand,%brick.rhand);
Is it supposed to be like this?

Somehow I didn't notice fxDTSBrick::processInputEvent when running trace, I'll look into that.


I thought I already fixed the hipt mistype, but apparently it decided to stick around, fixed now re-download.

I thought I already fixed the hipt mistype, but apparently it decided to stick around, fixed now re-download.

I hate it when stuff does that.

I was the first person that made an event that changed a player's colors :(

I was the first person that made an event that changed a player's colors :(

 :cookie: to you for being the 1st

AWAOME LOVE IT downloading now ten cookies for you  :cookie: :cookie: :cookie: :cookie: :cookie: :cookie: :cookie: :cookie: :cookie: :cookie:  :cookieMonster:

This add-on makes some of my events not work properly, such as target events

Win, downloading. :D

I'm gonna make a blockhead machine with this >.>

Updated: now works with every input event, thanks to Space Guy.

Well except onbottouch, might be a bit odd to make work.