Client Based Rendering Options

ID:2654875
 
Feb 9 2021, 11:54 pm
Applies to:DM Language
Status: Open
Issue hasn't been assigned a status value.
I don't know if this is currently doable, but I think it would be really convenient as a developer to be able to modify some rendering options on a per-client basis. I don't know how doable this would be but having some client vars could do the trick

client/filters[] = list("blur", "bloom", ...)

Or
#define FILTER_BLOOM
#define FILTER_BLUR

client/filters[] = list(FILTER_BLOOM, ...)


In both examples it could be set simply at runtime by adding/removing the filters from that client's filters variable, which would simply not render those filters on that client.

client/verb/NoBloomPlease()
    filters -= FILTER_BLOOM


So that we could, for example have settings in the game for different rendering options for the client. This would also be extremely helpful with running tests especially for performance to being able to just add/remove the filters from that list.

And perhaps the same for particles, although that could just be a simple boolean on the client

client/show_particles = TRUE // or false


By default these (and any other) variables would just have everything in them, so that it would work with backwards compatability.

Shit, do the same for animations, even!

But yeah. That's my request.