#🍌 Preview 1.21.80.22

1 messages · Page 2 of 1

analog bane
fleet heath
#

Behavior pack hierarchy... I guess if the top pack registers a command with the name je:help and then the pack below the top one registers a command with the same name it will error on the second pack

buoyant jacinth
#

It's revealed they are working on the Progress Screen and turning it into ORE-UI:

vernal dragon
#

Try it out ehappy

#

It's in 2.0.0-beta script API

buoyant jacinth
vernal dragon
#

Ah

hidden ledge
hidden ledge
#

Nvm

uncut venture
#

CUSTOM COMMANDS

#

IM CRYING

queen charm
#

Loads of issues

#

Hoping it’s fixed next preview

rare venture
#

Thats good tbh

uncut venture
#

the fact that there will be custom commands in a polished state at any time is what is making me cry

#

no more chatsend shitty things

vernal dragon
queen charm
trim rose
#

woah i completely missed this!!!

ember mango
#

classic texture pack makes all creepers look like charged creepers now :<

jade socket
#

How do we use the new custom commands in JS ?

quartz glade
#

because of namespaces

night shore
#

heh?

jade socket
#

ok thx

quartz glade
#

i never used custom commands

#

because they need to have namespaces

jade socket
#

Ah ok fortunately I was scared

digital ember
queen charm
#

Also besides that. The custom commands have very limited abilty of what we can do right now since we can’t get the sender of the command

#

(Getting fixed next preview I think)

ember stag
#

but, it's better than not having custom commands itself.

queen charm
# ember stag but, it's better than not having custom commands itself.

Hm well for now using the prefix commands is the way as we have support for everything. Even the things the developers have said most likely will never be supported for the native custom commands, like the sub commands( due to the command error system being too complicated to do so if I remember correctly ). And prefix commands are shorter and more appealing due to not using namespaces

#

The namespace stuff is just opinion tho

wind beacon
night shore
#

The new command could have an option to make the command with or without namespace

If two addon adding the same command name then addon with higher priority (higher position in behaviour packs list) take the command

#

idk how addon is loaded in the background; but if it loads from top to bottom then just ignore existed command name from registering?

#

I quite love the namespace prefix tho, kinda handy when you just need to type out the namespace and get all the related command to that addon

quartz glade
#

Rel

sharp adder
#

I will reiterate my opinion on namespaces with commands. Outside of chat they are necessary, but in chat, having the ability to type them without it when there's no conflict would be excellent QOL

buoyant jacinth
#

but that won't make sense for it to be implemented right

buoyant jacinth
#

i just see it as something extra work since there is things like autocomplete when you press TAB

sharp adder
#

Besides, even with TAB it's still more convenient to type just the command without having to worry about the namespace

queen charm
# buoyant jacinth but that won't make sense for it to be implemented right

Agree with slsilicon here, outside of the chat it’s definitely useful but it’d be a nice QOL to have it optional in the chat. And for the namespace stuff to where you can type it out in chat and see all related commands. An idea for this is to just have the namespaces be “invisible” where you can still see all related commands to that addon but you don’t actually have to type it out

#

I doubt the namespace stuff will be changed at all tho. I haven’t seen any developer feedback about it

#

There’s pros and cons to it

crude nymph
#

Instead of namespace, having it as a subcommand (when that gets available)
E.g. /butterfly home @p 100 ~ 100
Where butterfly is the namespace and home the command, possible with nested subcommands:
/butterfly home home1 @p (home1 being the subcommands)

digital ember
#

cri Subcommands aren't on the roadmap...we might get beforeChatSend and Entity.target stable before that.

crude nymph
#

Yeah I heard that. I thought of it as a possible solution

queen charm
#

a lot of things are wanted 😭

dreamy shale
#

While it's not 1:1 with vanilla, it's certainly far better than what we currently have with using custom prefixes

queen charm
dreamy shale
#

What exactly is stopping you from making your commands not as complex using the new method?

queen charm
#

But, this is just my feedback from messing with the commands for a good 30-40 minutes

#

Stopped when I realised we can’t callback to the sender

willow dome
#

If they added the text parameter (which the game supports), that would let you have more "complex" commands at the cost of losing auto completion, but still having a slash command

night shore
willow dome
#

a text parameter just captures the rest of the input, so it would show as something like "/prefix:command <arguments: string>" but then you could parse arguments however you want

night shore
#

I mean, you said "at the cost of losing auto completion"
I don't quite get that what parts make it lost except that those parameters after text parameter

#

/prefix:command <arguments: string> <value: bool> ?

night shore
willow dome
#

yeah pretty much

night shore
#

there are a lot of parameters type not currently added tho

#

like json

#

do command parameter get added?

queen charm
#

Idk about anything else

tender hinge
quartz glade
#

2137

sharp adder
vernal dragon
wind beacon
#

John Paul II

vernal dragon
#

Oh the last Pope

mighty kelp
#

TODAY IS A PREVIEW DAY!!! :D

errant bluff
#

tomorrow

mighty kelp
#

Oh :(

coarse ember
#

one of the best bug ever

digital ember
coarse ember
mighty kelp
#

does it drop in survival

queen charm
night shore
#

I miss wither cage

leaden helm
#

im gonna test this nonsense

sharp adder
#

Welcome back seed planting

leaden helm
#

oh no those poor farmers

slate grail
#

the guide system?

leaden helm
#

yes the tutorial

queen charm
leaden helm
#

rng block destroyer lets go

#

or ig not just destroy but…

#

exiled from the plane of existence

thick epoch
#

Exposed new fields to data driven jigsaw structures: start_height, dimensional_padding, pool_aliases, max_distance_from_center
made height_map_projection optional and changed anchor to start_jigsaw_name

Do we have any docs on these?

dusk hedge
thick epoch
#

Would you be able to explain what those do and if you have an example of them being used that'd be great

wintry viper
dusk hedge
wintry viper
#

Though i really want that mojang will convert all structures into jigsaw structures

#

That would be cool for addon makers

vernal dragon
#

I'm not 100% on that. A Mojangster said it last Tuesday, but something could have changed since then. I haven't been keeping up

simple zinc