Adding tickets does not respect TickType#doesSimulate()

[Rothes]

Expected behavior

If doesSimulate() is false, chunks added tickets that does not simulate should not being ticked.

Observed/Actual behavior

The chunk is ticking entities. Not sure if it's ticking block entities.

Steps/models to reproduce

1. Modifying any TicketType flag, remove FLAG_SIMULATION. In my case, I modified TicketType.PORTAL.
2. Summon a entity on any nether portal.
3. See the entity being ticked on the other dimension, and getTicketDebugString(chunkKey, true) shows the result that this chunk should not be ticked.

Plugin and Datapack List

No needs

Paper version

Confirmed on

This server is running Paper version 1.21.8-21-main@ed31825 (2025-07-31T02:36:28Z) (Implementing API version 1.21.8-R0.1-SNAPSHOT)
+
This server is running Paper version 1.21.11-38-main@4446f17 (2025-12-09T22:51:57Z) (Implementing API version 1.21.11-R0.1-SNAPSHOT)

Other

On Spigot servers, this inconsistence doesn't exist.

getTicketDebugString result:
Load Ticket: Ticket[TicketType[timeout=300, flags=11] 30 (null)] to die in 289
Tick Ticket: Ticket[TicketType[timeout=0, flags=14] 33 (2)] to die in -9223372036854775808 (2)

Were Tick/Simulate Ticket level shows 33 (I have another player observing this chunk far away), this should not tick anything.
I assume that the chunk system rewrite breaks this vanilla behavior.

[lynxplay]

Internal behavior is not something that needs to stay in line with spigot or vanilla or even previous paper versions.

Unless this somehow expresses itself in a vanilla gameplay behavior bug, this is a works as intended.

[Rothes]

I understand. This shouldn't cause problems on a clean Paper server.

So, I'm closing this issue.