Quote:
Originally Posted by Milk-Man
Also been messing with your bluelines plugin. Is it normal to start tribes, have it green for 5-10 seconds then turn blue? what the what man?
|
depends on the setup but i've never had it apply that late personally
bluelines applies its colors with a command
groovcolor(destination,r, g,b);
on init the .dll looks for and tries to load customcolors.cs which is just a script that sends the groovcolor command for each destination
if it doesn't find customcolors.cs (or if you're using the win8 pluginfix .exe, which tries to load customcolors so early it fails) it should load the default blue settings
in that situation you can change customcolors.cs to customcolors.acs.cs and use that to override the defaults... which would load later
basically this is a long winded reply to explain that depending on your setup, plugins can load in different orders, at different times, etc and that can all affect how quickly things are applied
if say, you're not using the win8 pluginfix, and you're using a bunch of plugins, possibly with the old rasadhlp.dll that you have to do +p shortcut stuff, bluelines could be loading much later than if it was applying the defaults right away using the win8 pluginfix and the autoloader
or it could just be as simple as a slow hard drive loading the plugin late
sounds like your tribes install is a bit wacky tho - you could .zip it up and send it my way and i could check for derpy stuff