[ ] Inventory serialization
It would be great to have the basic features of Bukkit available without addon. 😃
I reformatted the issue and removed things that have already are in progress and/or already have an issue.
Thank you so much! @Pikachu920
There's some stuff in here that's pretty basic and IMO should be supported which is why I'm doing low priority instead of lowest. Namely the events (especially the brew, anvil prepare, horse jump, and leashing events).
On fishing stuff, plugins list, addons list, loaded chunks [of world], refresh chunk, version of plugin ^^
By the way i have suggested load/unload script effets with more details in https://github.com/SkriptLang/Skript/issues/822 already.
Good shout, I removed loading/unloading scripts from this issue so #822 will remain the primary one for that request.
Some other ideas:
Spigot sound enum names are already supported in the play sound effect @TrademarkTM
@TrademarkTM if you can suggest a good syntax for titles I'm adding it.
The syntax would probably have to be pretty complicated to both be versatile and to read like English. I'm sure it could be improved but for starters, maybe something like this?
send (title %text% [with subtitle %text%]|subtitle %text%) [with a %timespan% fade(-| )in][(,|and|with) [a] %timespan% (linger|stay)][(,|and|with) [a] %timespan% fade(-| )out] to %players%
Title/subtitle should default to an empty string and each of the timespans defaulting to one second? You'd need to convert the timespans to ticks since the player#sendTitle function accepts the durations as the number of ticks as an integer.
If that works it would be versatile in how you could word it, all as pretty proper English. Would allow all of the following:
send title "Example" to all players
send subtitle "Just a subtitle" with a 3 second fade-out to player-argument
send title "Long example" with subtitle "Oh god" with a 99 second fade in, 3 second linger and a 1 second fade-out to all players
send title "Versatile fades!" with a 2 second stay and a 1 second fade-out to player's target
(send|show) %players% title %string% [with subtitle %-string%] for %timespan% [with %-timespan% fade(-| )in (, | and) %-timespan% fade(-| )out]?
I find the for %timespan% wording in title syntaxes a bit ambiguous since I don't think it's clear to the user that it indicates how long it should stay WITHOUT including the fades. If I was a new user that didn't know better I'd think the title should last that long in total, including the fades.
It think for is good for the general timespan, but not good for fade-in and fade-out in this case.
Lets open another issue for posting bugs ✨
As Blueyescat said, it's a pretty big effect to use timespan three times.
What about this? One timespan, fade-in and fade-out in ticks.
(send|display|show) %players% title %string% [with subtitle %string%] for %timespan%[( with|, )] %integer% [fade(-| )in](, | and) %integer% [fade(-| )out]
Lol i don't mean that, they all must be timespans but
for %timespan%[( with|,)] %timespan% [fade(-| )in]][(,| and) %timespan% [fade(-| )out]]
"for" is used for the general timespan only.
Not a single syntax convinced me sadly, this is mainly why I didn't implement it before. And integers won't work since it isn't concise and it isn't really user-friendly.
I'll think about it more though and see if I can come up with a syntax based off the suggested ones. Also, to not fill this issue with rather unrelated comments, further discussion can be done at #skript-talk in Skript-chat (just mention me if you get a suggestion).
Visibility and force chat are both addressed by pending PRs (#1302 and #1298, respectively)
Syntaxes for actionbars and titles:
(send|show|display) action[ ]bar %text% to %players%
(send|show|display) title %text%[( with | and |, )sub[ ]title %text%] for %timespan% to %players% [(with|and) fade[( |-)]in %timespan%( and |, ) fade[( |-)]out %timespan%]
I think it's more user-friendly now. Not sure if it's better to use fade-in and fade-out in the end or middle of the syntax.
I like the cuboid one, as @TrademarkTM suggested. Perhaps we could have also sphere, etc.
We could save cuboid properties into variable and then we could set blocks there, for example. Great alternative for simple WorldEdit skript or protected arenas, selections and so on.
Closing this issue since as I've said in #3269, 1 feature request per issue is preferable and the feature set being requested is just too much of a general thing with little detail on them.
Most helpful comment
I reformatted the issue and removed things that have already are in progress and/or already have an issue.