Skip to content

bring back tick!#192

Open
Thorioum wants to merge 1 commit into
kaboomserver:masterfrom
Thorioum:master
Open

bring back tick!#192
Thorioum wants to merge 1 commit into
kaboomserver:masterfrom
Thorioum:master

Conversation

@Thorioum

@Thorioum Thorioum commented Mar 1, 2026

Copy link
Copy Markdown

its an S tier command that rivals the likes of /weather and /cartographytable

I would argue the pros of this command outweigh the cons

@OptimisticDeving

Copy link
Copy Markdown
Contributor

What pros? 😊

@hyfehnated

Copy link
Copy Markdown

I am a pro at having hot gooey sex with your mother

@UIFreestyler

Copy link
Copy Markdown

I am a pro at having hot gooey sex with your mother

mi bomboclat

@Yaodeowo

Copy link
Copy Markdown

Bring back /tick!
In a no-rules server, abuse is expected. The PR says it's "abused hella lots"—but so are /sudo, /tpall, and /deop. Unless /tick is actually crashing the server or killing TPS, that reason alone isn't enough to remove it.

@qwertyad1

Copy link
Copy Markdown

The main concern mabye is that tick freeze might interrupt command blocks

@Yaodeowo

Yaodeowo commented Jul 23, 2026

Copy link
Copy Markdown

The main concern mabye is that tick freeze might interrupt command blocks

This does not prove any point. what wrong interrupt command block?
Will this cause a crash or some other problem?

@qwertyad1

Copy link
Copy Markdown

well i feel like thats one of the unspoken goals the people running kaboom have.
see: the new command block gamerule being locked to enabled

@qwertyad1

Copy link
Copy Markdown

If they wanna start unlocking stuff and breaking this whole thing of keeping the command cores functional then im all for it but thats not what it looks like to me

@Yaodeowo

Yaodeowo commented Jul 23, 2026

Copy link
Copy Markdown

well i feel like thats one of the unspoken goals the people running kaboom have. see: the new command block gamerule being locked to enabled

You're right, but kaboom not only us.
To be honest, gamerule command_blocks_work shouldnt be locked.

@Yaodeowo

Yaodeowo commented Jul 23, 2026

Copy link
Copy Markdown

If they wanna start unlocking stuff and breaking this whole thing of keeping the command cores functional then im all for it but thats not what it looks like to me

"Free OP, anarchy, creative" that's not what this server is.
"This server is built for player that use command blocks. If the command gets blocked? Too bad."

@qwertyad1

qwertyad1 commented Jul 23, 2026

Copy link
Copy Markdown

back on topic, we could unblock the tick command if we lock tick freeze
i gotta do a bit of testing but i dont think higher or lower ticks are gonna affect command blocks TOO badly

@qwertyad1

Copy link
Copy Markdown

ok so the one thing i forgot about was the motion slowing that might be kind of annoying

@Yaodeowo

Yaodeowo commented Jul 23, 2026

Copy link
Copy Markdown

ok so the one thing i forgot about was the motion slowing that might be kind of annoying

As i said, there is more annoy commands.
The problem actually with the players.

@OptimisticDeving

Copy link
Copy Markdown
Contributor

Bring back /tick! In a no-rules server, abuse is expected. The PR says it's "abused hella lots"—but so are /sudo, /tpall, and /deop. Unless /tick is actually crashing the server or killing TPS, that reason alone isn't enough to remove it.

A bot or malicious player could very easily spam /tick freeze and make the server unplayable - though now that cloops have been neutered it's much less abusable than before but a malicious bot developer could very easily send /tick freeze via their command core as soon as ticks become unfrozen.

It's also worth noting that /tick isn't just /tick freeze, otherwise it would more or less be okay to unblock the command, but it's also /tick rate. You can set this to a very low tick rate and delay client animations (opening the chat, etc) which is excruciating to deal with. You could also spam set this to a very low value.

An acceptable compromise would be to clamp the tick rate to something like 10-30

@OptimisticDeving

Copy link
Copy Markdown
Contributor

well i feel like thats one of the unspoken goals the people running kaboom have. see: the new command block gamerule being locked to enabled

Well, I don't think anyone wants bots spamming /gamerule command_blocks_work true whenever someone decides to spam disable the gamerule. Might I add that with the new set gamerule packet, you can do this much faster than the rate at which command blocks execute. Forcing it to true just maintains the old behavior before the gamerule was introduced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

6 participants