Moderocky
Moderocky
I think I'd rather fix the function return behaviour than make a syntax for this.
> there is no bug in function return behavior is works how it's intended to And I'm saying the behaviour is poor and could be done better.
> It can't be done better when the function literally can't support `set {_blah} to clamp(10.6, 1, 10)` this isn't exclusive to clamp when round function has the same flaw....
> Why are they getting compared to themselves? I feel like these should be checking if the output is set. If I remember correctly this was one of the ways...
> ```java > static final Experiment MY_FEATURE = Skript.experiments().register(addon, "my feature", LifeCycle.STABLE, "my [cool] feature"); > ``` I can definitely add an extra method for that, I just want to...
> could we make this extensible by addons? skript-reflect has a similar structure to opt in to beta features. it would be nice to keep them consistent! It absolutely is,...
Maybe I'm a heretic, but I feel like this could be done better as a second, extra loop syntax. We could borrow inspiration from other languages and have something like...
I still really don't like modifying the `loop` syntax like this because it's such an established thing.
> I'm strongly against adding multiple conditions in one line. However, as a substitute, perhaps the following? > > ``` > if any: > a > b > or/and if...
Absolutely agree, we're planning to start deprecating aliases as of 2.9 anyway and moving towards and optional (opt-in) model in future.