Not logged inOpenClonk Forum
Up Topic Functions in proplist constants, Effects

This board is threaded (i.e. has a tree structure). Please use the Reply button of the specific post you are referring to, not just any random button. If you want to reply to the topic in general, use the Post button near the top and bottom of the page.

Post Reply
In Response to Zapper
Why is Target not a property of the effect (like CommandTarget) but passed as an argument everywhere?

I think it would look a lot nicer, if target would just be a property of the effect. It would also not be much more to type (fx.Target) but instead remove having to add one obligatory argument everywhere (ideally even when it's not needed as a hint to the next coder about how the signature of the call really looks to remove possible error sources).

TL;DR: I think Target belongs to the effect properties instead of the argument list - would be cleaner and more unified!

Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill