%brick.isPlanted not robust

[Plexious]

In my CRP mod I have this problem. Whenever a player places a brick in the air or on somebody else's brick that they don't have trust with, it still charges them for the brick making their funds decrease but the brick does not place. I have the code check if the brick is planted but %brick.isPlanted isn't enough. How would I check the ghost brick if it was floating or if the ghost brick is on somebody's brick you don't trust?

Also, on a second note: $Server::PlayerCount doesn't update when a player disconnects.

[Ad Bot]

[Chrono]

Instead of $Server::PlayerCount, use ClientGroup.getCount()

[Mold]

Doesn't a brick planted without trust first plants, then kills?

[Treynolds416]

Schedule an object check, if it's still there then deduct the whatever

@mold yes

[Ipquarx]

Schedule an object check, if it's still there then deduct the whatever

At the most 50ms schedule, idk if a 0 schedule would work

[Treynolds416]

At the most 50ms schedule, idk if a 0 schedule would work

I've done some previous testing and it should, in theory. He might want to raise it just to cope with unforseen complications such as lag

[Kalphiter]

Doing "0" will schedule it for the next tick, which means after the current tick.

[Ipquarx]

Doing "0" will schedule it for the next tick, which means after the current tick.

I assume this means a 0 schedule will work.

[Kalphiter]

No, it means it does work and it's useful.

>engine takes care of current tick
>takes care of schedules
>new schedule added to schedule queue

>next tick
>takes care of schedules

etc...

[Plexious]

isPlanted() gives me the same results.

[Port]

Doing "0" will schedule it for the next tick, which means after the current tick.

More specifically, it schedules it for the next frame (so a [mspf] millisecond delay).

[Kalphiter]

More specifically, it schedules it for the next frame (so a [mspf] millisecond delay).

Servers don't render any frames.

[Port]

Servers don't render any frames.

The main loop still counts in “frames“.

[Kalphiter]

The main loop still counts in “frames“.

When it's only a server, it's better referred to as "ticks".

[Nexus]

I would suggest deducting the money or whatever from them, and then packaging the function that kills the brick to refund them.