Worst triggerArea

In sdk6 utils library was better, for example: i need lift trigger area i could do one trigger area with 26 meters of building for access from all floors -- in current library execution i can't do it, trigger area works only from bottom + 3 meters, all upper part doesn't work. And one stupid tech and manage behavior -- in decentraland engine position for shape use center point, here debug shape starts from center point of the shape, but trigger area start work only from center point, but bottom half part of the shape doesn't works. You did mistake in general concept of position point in decentraland engine and in this library.

Library too much draft.

I saw source code of trigger area, look likes too much science based language to naming and something like differential or integral in rude view with cycles for areas like for chunks, too much academic term intersection, but in code realisation just Vector3 substract and add methods.

Fake strong minded code, which didn't correctly simple things.
I did fast simpler analog for 62 strings of code which works in simpler cases VS your 473 strings of code with over engineering and without ability to do though simple thingas

Start by reading the trigger-area source referenced in the report and reproducing the described behavior with a tall area spanning multiple floors. Compare the debug shape's center-point behavior with the actual trigger bounds, then define tests for the lower and upper portions of the area. Done means the reported 26-meter trigger area works consistently throughout its volume.

Written by the indexing model from the issue text.