First of all - I'm not really up to date with "told" changes in docs 2, so I don't know if it already exists or had been already denied - I joined the forum just some days(max 2-3 weeks) and I didn't use to spend a lot of time there. Sorry!
I thought of it for a while; it would be really great if we had it.
There's, for example, expression. There should be, instead of mentioning it in the description, a list of events it can be used in. With events as well - a list of connected expressions.
For example:
What would it give? Well; It will say if our syntax is ok when we wanna make condition or something; We wouldn't need to look for that on an expression list. I had such situation before - I was struggling to find any way to use 'location' hit by lightning and I got nothing. After that sb told me, that there isn't really a way to do that, if there's no entity there and I was so sad, but I wouldn't search docs for about 15 minutes to find anything; I would knew that!
The second thing is tag "unworking", "bugged*".
The first tag would be used, when the whole syntax of event/expression/etc. doesn't work, while the 2nd one would be used when some of listed supported expressions/events/etc. are not working or if it doesn't work with a specified addon
Again, easier life... And it would be found in the way of reports from community - fast and easy way; some reports give a clear situation, but it would have to be really, really well-described report - with versions, plugins and all this stuff (a special form to fill in?)
What do you think men? Let's do that!
EDIT:
As it is similar, i don't make a new thread - also, if it goes about types, i'd add info "Loopable: yes/no", because not all types are usable (the same about commands maybe, because there are types either usable as argument or unusable :V
EDIT:
Cancelable would also be nice thing for events
@BaeFell - what do You think?
I thought of it for a while; it would be really great if we had it.
There's, for example, expression. There should be, instead of mentioning it in the description, a list of events it can be used in. With events as well - a list of connected expressions.
For example:
On death
<Description>
This event supports these expressions:
<Description>
This event supports these expressions:
- victim
- attacker/damaged
- damage cause
- final damage
- don't really remember if there are others :V
The second thing is tag "unworking", "bugged*".
The first tag would be used, when the whole syntax of event/expression/etc. doesn't work, while the 2nd one would be used when some of listed supported expressions/events/etc. are not working or if it doesn't work with a specified addon
Again, easier life... And it would be found in the way of reports from community - fast and easy way; some reports give a clear situation, but it would have to be really, really well-described report - with versions, plugins and all this stuff (a special form to fill in?)What do you think men? Let's do that!
EDIT:
As it is similar, i don't make a new thread - also, if it goes about types, i'd add info "Loopable: yes/no", because not all types are usable (the same about commands maybe, because there are types either usable as argument or unusable :V
EDIT:
Cancelable would also be nice thing for events
@BaeFell - what do You think?
Last edited:
). Also not every1 is really capable of contacting with authors due to lack of english-talks basics (I know such people, who are using Skript, while they can't actually talk with others (grammar :V). I heard of such men even more xD)