RC/repeater ''power rings''

[Nux]

i have a feeling you're missing someone to mention.

...and the same thanks goes to everyone else involved.

Yes. It's fully functional and more than that, it's available to all who want it. It only serves as a proof of concept so far as anyone who wishes to delve deeper into the code can implement the same thing in a way that suits the development's standards. For everyone else it's a free feature, woo!

Now, correct me if I'm wrong, but doesn't this involve looking at whatever code reads .shader files and adding classes/loops/if statements so you can tidy a wall of text into something smarter?

[Qrntz]

S00N(TM) after DNF2 is released.

lol

[/dev/humancontroller]

Now, correct me if I'm wrong, but doesn't this involve looking at whatever code reads .shader files and adding classes/loops/if statements so you can tidy a wall of text into something smarter?

adding functionality to define shaders in loops would be sufficient just to decrease the big shader file. however, there is no gain in doing that for just 1 file (no other shader file is in need of "loopy refactoring"), that will just cause more pain and potential bugs. the shader file should be left alone, unlike the game code.

[Nux]

I think the mindset the developers have is that of treating every new addition as one of possibly many, no matter how unlikely it seems at the moment because it probably never seems like the code will be used in ways it later will. Also, the file will become so much more readable if the logic can be condensed into it's basic patterns.

I don't know how you would pass that kind of functionality over to the shader files, and I don't know if it would be considered ill-advised to do so since it might open doors to some particularly nasty shader files. I don't even know if it's just the expanded nature of the file that the developers don't like. All I know is they refuse to take responsibility for it as it is.

[Plague Bringer]

This will likely dissolve into a battle of pride.