Lua Challenge: the Catastrophes plugin

[bearbin]

You should profile the server, find out what's making it run so slowly.

[tonibm19]

How much expensive is for the server to check height every tick?

[DiamondToaster]

It's just the sheer amount of entities that are involved in the process. It makes 2500+ falling block entities and a bunch of pickups.

[bearbin]

We want the server to be able to handle 2500 falling entities. With optimisation, that should be possible.

[worktycho]

If you've got a plugin that can trigger that many falling entities with console command, I'll take a look.

[tigerw]

I have an idea for optimisation: most cChunk::Get/SetBlock functions do multiple comparisons for error checking, which theoretically shouldn't be needed in release since I remember xoft saying in one of my PRs that those functions shouldn't do sanity checks for their callers, and someone else saying that the server will not be made to protect against badly written plugins.

Moving those checks into debug only conditions may help?

[DiamondToaster]

I'll upload the plugin once it stops crashing clients.

[worktycho]

@tiger I suspect that just inlining them would have a better cost/benefit ratio to start with.

[LO1ZB]

I can do profiling aswell. :>

[NiLSPACE]

I created a blackhole catastrophe.