Open CerialPvP opened 1 year ago
There's a pr along the lines of adding inline loops #5244, however due to it being a draft I'm very unsure how long it would take for it to actually release anymore.
I'm not super in favor of how the example looks as it's basically a file without the file
There's a pr along the lines of adding inline loops #5244, however due to it being a draft I'm very unsure how long it would take for it to actually release anymore.
I'm not super in favor of how the example looks as it's basically a file without the file
Well again, it can be improved to Skript standards, but it was my suggestion. The inline PR looks better than mine but it doesn't allow for multiple effects in one line, which is also what I would hope would get added.
Personally I think the process of writing a section out in effect commands would be far more tedious than a test skript. That said, it's still a valid suggestion!
Personally I think the process of writing a section out in effect commands would be far more tedious than a test skript. That said, it's still a valid suggestion!
Agree, but it doesn't have to be loops, it can be any section like the spawn section.
bump
bump
Please don't add useless comments to issues. This is not a forum, "bumping" has no effect on whether your suggestion will be implemented. If you want it to be added more quickly, consider contributing it to the project yourself!
using a book UI could be an option. i'd agree with sovde that chat would be too tedious to warrant the feature
I don't think encouraging over-reliance on effect commands like this is healthy. They're not very safe to begin with, being completely untethered code, but this is even worse because you will end up with floating loops taking up space in the background silently that belong to nothing with no clear way to identify them or get rid of them.
Suggestion
Basically, make sections become available in effect commands. An example for this is the Python live interpreter, where if you type something like:
it allows you to enter more code in there, for example:
I suggest the same thing to be available within effect commands, if you enter for example:
it will allow you to continue the code, like this:
Obviously, only sections are allowed, you shouldn't be able to make an event or command using that.
To end a section, just put a
;
with the effect command prefix. This is a FizzBuzz example in Skript, which includes what I said.As you can tell, this is a generic FizzBuzz, but in Skript. You can also see you indent using periods, one indentation is
..
, two is....
, ect.Why?
Currently, the only way to test code which requires a section is to make a test skript, which can be tedious. This suggestion will help people like me and anyone else which is interested to test code.
Other
No response
Agreement