Skip to content

Conversation

NiseVoid
Copy link
Contributor

Objective

It should be possible to use the spatial query API for non-standard colliders

Solution

  • Refactor the whole thing
  • Add generics everywhere

Changelog

  • The spatial query API has been reworked to allow use of non-standard collider types

Migration Guide

TODO

@Jondolf Jondolf added C-Enhancement New feature or request A-Spatial-Query Relates to spatial queries, such as ray casting, shape casting, and intersection tests C-Breaking-Change This change removes or changes behavior or APIs, requiring users to adapt labels Aug 23, 2025
@Jondolf Jondolf marked this pull request as draft August 23, 2025 14:57
@NiseVoid NiseVoid force-pushed the generic_spatial_query branch from abeb2aa to e4cb487 Compare August 24, 2025 13:13
@NiseVoid NiseVoid force-pushed the generic_spatial_query branch from e4cb487 to 1f375a7 Compare September 28, 2025 11:41
@NiseVoid NiseVoid force-pushed the generic_spatial_query branch from 1f375a7 to 5baf1b3 Compare October 8, 2025 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-Spatial-Query Relates to spatial queries, such as ray casting, shape casting, and intersection tests C-Breaking-Change This change removes or changes behavior or APIs, requiring users to adapt C-Enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants