# Objective

- Updated version of #527 with some changes suggested by Jondolf

## Solution

- Reapply the changes from the previous PR
- Add a `SimpleCollider` trait that works for colliders with no context to shorten function signatures

## Changelog

- Custom colliders can now specify a SystemParam via `AnyCollider::Context`
- The context is passed to all `AnyCollider` methods, allowing data from the `World` to be fetched
- AnyCollider functions have been suffixed with `_with_collider`
- A new `SimpleCollider` trait has been added to retain the simplified methods for colliders that don't need context

## Migration Guide

- Custom colliders now need to specify a `Context` `SystemParam`, if this is unnecessary `()` should be used
- When trying to use methods from `AnyCollider` on an implementation with `()` context, `SimpleCollider` should be used instead
- Methods on `AnyCollider` have been suffixed with `_with_context`

---------

Co-authored-by: Gijs de Jong <14833076+oxkitsune@users.noreply.github.com>
Co-authored-by: aecsocket <aecsocket@tutanota.com>
Co-authored-by: Joona Aalto <jondolf.dev@gmail.com>

# Objective

#527 used a read-only `UnsafeWorldCell` for the initialization of `ColliderAabb` in an `on_add` hook for `Collider`. However, it uses methods that provide mutable access, which is unsafe and panics with debug assertions.

## Solution

Remove the whole AABB initialization logic and use of `unsafe`. Having it didn't make sense since the initial positions are likely wrong anyway.

`ColliderAabb` is now explicitly specified to be `ColliderAabb::INVALID` until the first physics update.