Nanospray colours

[jcnossen]

Oh yeah so happy.

Then what should be used?

Add it as a bool to the global unsycned struct, and read that from the config handler at load time...

[Neuralize]

I'm sorry what would be wrong if the modder can define
1. To use different colors if he wants
2. If the mod allows team colors or not.

Wouldn't everyone be happy then?

The code wasn't thrown about because the administrators were against nanosprays of different color, the code was thrown out because it because it was done in a matter which slowed down the game more than it should.

[unpossible]

From the SVN:

removed user defined team colored nanospray, because it's defined by the mod. Also ConfigHandler.GetInt() shouldn't be used in the middle of drawing for performance reasons.

I think this is the right way to go about it, doens't seem to make sense to have the user muck up the colour schemes of mods

(sorry for the repeat, i just found the new SVN log)

[Lindir The Green]

Yes, the modder should be able to decide exactly which color to use as the default, and how much transparency, and then whether the user is allowed to change that.

[Neddie]

I would rather have the power to define my own nanospray colour than be forced to use that of a mod, as most modders probably don't even care what colour it is.

Sure, have the default be mod - but honestly now, it's lame to have default colour nanospray when your side isn't that colour.

This was a very cool feature I was enthused with, and the removal of it is really just pathetic. Once the issues with the game-slowdown are resolved through recoding a different method of calling the colour, I think it should be returned to the players... I mean, hell, it's only cosmetic.

[AF]

Honestly I didnt see any slowdown at all in the code after i added it in, nor did anyoen else usign the svn code untill jelmer looked at the code a few weeks later.

I'm having to reprogram it but I'm adding in a tag to disable nanoframes and a tag to set wether a mod allows the user to switch the team colours on or not in mod_info.tdf.

Any suggestions on tag names?

allow_team_colours=1; ?

btw this will default to allow so if modders have a problem with team coloured nanosprays they can turn it off else users can switch as they please.

[Tobi]

Then what should be used?

cache the variable

[AF]

I have GlobalUnsyncedVariables and a problem.

How do i add a value to be parsed in mod_info.tdf?

Or si there a better place to load the tag from?

[Gnomre]

Make a new tdf file in the gamedata folder... Call it ParticleEffects.tdf or something like that so it can be reused later if more particle stuff is implemented.

As I see it, I agree that this should be entirely a modder decision: the players should not have any say (other than collectively bugging the modmaker if they dislike it). If I want teamcolored nanos in my mod, allow it. If I want all purple nanos in my mod, allow it. If the player wants all green nanos, tough luck. It's that simple.

[Neddie]

Make a new tdf file in the gamedata folder... Call it ParticleEffects.tdf or something like that so it can be reused later if more particle stuff is implemented.

As I see it, I agree that this should be entirely a modder decision: the players should not have any say (other than collectively bugging the modmaker if they dislike it). If I want teamcolored nanos in my mod, allow it. If I want all purple nanos in my mod, allow it. If the player wants all green nanos, tough luck. It's that simple.

It has no gameplay impact. It's a bloody colour! What business does the modder have in defining a cosmetic element that might just be a personal effect? It's completely pointless...

[AF]

gamedata\particles.tdf

Code: Select all

[NANOSPRAY]
{
    allow_team_colours=1;
}

[Zoombie]

Bring it back, but give it to the mod makers.

[Gnomre]

It has no gameplay impact. It's a bloody colour! What business does the modder have in defining a cosmetic element that might just be a personal effect? It's completely pointless...

Oh, right, we have to submit to the will of AA on this forum. I forgot: if it doesn't fit AA, it shouldn't be in the engine. My bad.

[AF]

huh?

He wasnt talking about AA, he was infact supporting the idea, not saying if wouldnt fit and it should be nuked =s.

I was rather hoping you'd comemnted on my previous post when i saw you'd posted =(

[Neddie]

It has no gameplay impact. It's a bloody colour! What business does the modder have in defining a cosmetic element that might just be a personal effect? It's completely pointless...

Oh, right, we have to submit to the will of AA on this forum. I forgot: if it doesn't fit AA, it shouldn't be in the engine. My bad.

I don't even know what that is about. Probably you don't know me at all, which would explain it. What, does this effect XTA? EE? FF? Gundam? Nanoblobs? I can see, maybe issues with WD, sure.

Provide an actual reason for modder colour definition, and I'll entertain it. But don't try to patronize me.

[AF]

WD wont be affected as I'm sure that it'd end up using the tags to show no nanospray whatsoever.

[FireCrack]

^The dead same reason that we dont have all other things customised in that way, you can't modify your game so a zeus looks like optimus prime. The same reasons users dont define their own deflector sheild, or laser colours.

Cosmetic effects should be designed my a mod, if I want my mod to have units made out of "grey goo" I should be able to, if I want the basis of my mod to be units are made out of fire of some sort i should be able to define my nanospray colour as red.

[Neddie]

See, that is a valid explanation, and I concede the point on the basis that numerous modders can be convinced to allow player control if the colour isn't integral to the mod.

[Zoombie]

What if you wanted different nanosprays for different teams? Like in TA:K, witch had 'kind of' nanosprays. But they made more sence because they were MAGIC!

[AF]

I think I've fixed it all. I'll make a patch once I've tested it though.