![[de]](/mwf/flags/de.png "Germany")
Sven2 has already touched the topic with his latest commit in the lights branch:
At the moment, all lights are visible by everyone. That's not desirable of course. Especially for melees, we don't want players to see the light cones of their enemies. For explosions, all players seeing them might not even be the worst idea, since it might add some strategic element to the game (if you make explosions, you will be seen for a short while).
How about we make the light visible to the controller of the light source object, and all allies. Objects without controller would be visible by everyone. Would this cover most usecases, or are there other suggestions?
> Currently, all players see the light. In the future, we may want limit it to the controller of the explosion.
At the moment, all lights are visible by everyone. That's not desirable of course. Especially for melees, we don't want players to see the light cones of their enemies. For explosions, all players seeing them might not even be the worst idea, since it might add some strategic element to the game (if you make explosions, you will be seen for a short while).
How about we make the light visible to the controller of the light source object, and all allies. Objects without controller would be visible by everyone. Would this cover most usecases, or are there other suggestions?
>How about we make the light visible to the controller of the light source object, and all allies. Objects without controller would be visible by everyone.
Sounds like the ideal way imo.
I think the controller of the object is good if it concerns torches and flashlights for example, but for explosions I'd prefer something global somehow.
>How about we make the light visible to the controller of the light source object, and all allies. Objects without controller would be visible by everyone. Would this cover most usecases, or are there other suggestions?
The controller of an exploding flint is the throwing player. This is necessary to trace kills correctly.
So this would not cover the flint case. I am a fan of making the explosion visible for everyone, too. :)
Can't it default to controller + allies and then for the flint (and maybe other objects) you can specify global. This must be easily possible with the helper object created by Sven once the engine supports this.
*klick*
I like global lighting for all light sources. It's realistic and strategically the most interesting.
I like global lighting for all light sources. It's realistic and strategically the most interesting.
It is definitely the most realistic, but this would mean that any light source other than the clonk can always be detected by the enemy. So there are no sneaky weapons or tools you can use which involve lights. I am not sure I like that, I agree with you however, that explosions, fire arrows and boompacks should be visible by all.
We could also make explosions visible only if it's within view range of one of your clonks. Although if we continue to disallow scrolling, we already have that.
Yeah, that's pretty much the way I intended it to work. There's a number of interesting design considerations though - for example we probably want torches in one way or the other eventually. So should torches only work for their owners? Spontaneously, it would make a lot of sense to me to make "viewpoint" lights visible to allies (initially just Clonks, but maybe we'll have "wards"?), but all actual light objects visible to everybody. After all, it's realistic and we might get some strategic decisions out of it. We could even decide to shorten the Clonk view range considerably so carried torches become a true resource.
For more insight into this topic you can watch the video Sven, Newton and I made of the current state of the lights branch.
I am currently working on fire arrows and explosive arrows, so that we can test a little the effects of visibility with ranged weapons in the lights branch.
By the way, would it be okay if I commit these objects directly to the lights branch once they are done?
By the way, would it be okay if I commit these objects directly to the lights branch once they are done?
> By the way, would it be okay if I commit these objects directly to the lights branch once they are done?
It would be okay for me, but I hope we can also merge the lights branch into master soon.
Yes that would be good as well, to merge, I think the Parkours have been tested sufficiently and seem okay.
That's why I wanted to also test some melee functionality.
That's why I wanted to also test some melee functionality.
Does anyone have objections to merging the branch in the state it is now?
> Does anyone have objections to merging the branch in the state it is now?
Merged! Please do all lights developments and bugfixes now in master :)
For now I have just created a nice dark melee with fire and explosive arrows. See attachment.
Btw: Sven should the Fx_Light object be a vehicle? It then falls out of the screen, so I already changed it to staticback locally, I can push that if needed.
I hereby license the file CaveBattle.ocs.tar.gz under the CC-BY license
Btw: Sven should the Fx_Light object be a vehicle? It then falls out of the screen, so I already changed it to staticback locally, I can push that if needed.
I hereby license the file CaveBattle.ocs.tar.gz under the CC-BY license
Attachment: CaveBattle.ocs.tar.gz (118k)
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill
