Position should not be allowed to have a null World (remove Position from Block)

[dktapps]

Problem description

This is bizarre and unexpected.

Proposed solution

It's only needed because Blocks contain Positions that need to initialize with something when they aren't in a world. Really, this is an issue about removing Position from Block and having it injected via function parameters where it's needed, because the current design has resulted in a multitude of issues.

However, removing Position from Block is a huge change that I've unsuccessfully tried to do several times before. It would involve:

• Everything that uses Block as Position to be updated
• All plugin APIs that expose a position via Block would have to be changed
• New APIs on events to include positions separated from blocks
• Many BC breaks within the Block package to pass World and Vector3 params

[dktapps]

Turns out Position in Block is also a significant factor in the poor performance of GC. Since Position ref World ref Server, and Server is an expensive object to do GC on. These objects cause Server to get frequently scanned for GC.