Skip to content

docs: Document the resolved-camera fields in the raycast skill #1905

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hatayama merged 1 commit into from
Jul 21, 2026
Merged

docs: Document the resolved-camera fields in the raycast skill #1905

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .agents/skills/uloop-raycast/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,7 @@ uloop raycast --x 960 --y 540 --layer-mask 1
Returns JSON with:
- `Success`: Whether the command completed
- `Message`: Status message
- `CameraName` / `CameraPath`: The camera that `Camera.main` resolved to and that the ray was cast from, reported on both hit and no-hit responses. When a `No physics hit` result looks wrong, check these first — another camera in the scene carrying the `MainCamera` tag can silently win the `Camera.main` resolution, so the ray may not come from the viewpoint you expect
- `Hit`: Whether physics hit anything
- `HitGameObjectName` / `HitGameObjectPath`: Hit object identity when `Hit` is true
- `HitLayer` / `HitLayerName`: Hit object layer when `Hit` is true
Expand Down
1 change: 1 addition & 0 deletions .claude/skills/uloop-raycast/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,7 @@ uloop raycast --x 960 --y 540 --layer-mask 1
Returns JSON with:
- `Success`: Whether the command completed
- `Message`: Status message
- `CameraName` / `CameraPath`: The camera that `Camera.main` resolved to and that the ray was cast from, reported on both hit and no-hit responses. When a `No physics hit` result looks wrong, check these first — another camera in the scene carrying the `MainCamera` tag can silently win the `Camera.main` resolution, so the ray may not come from the viewpoint you expect
- `Hit`: Whether physics hit anything
- `HitGameObjectName` / `HitGameObjectPath`: Hit object identity when `Hit` is true
- `HitLayer` / `HitLayerName`: Hit object layer when `Hit` is true
Expand Down
1 change: 1 addition & 0 deletions Packages/src/Editor/FirstPartyTools/Raycast/Skill/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,7 @@ uloop raycast --x 960 --y 540 --layer-mask 1
Returns JSON with:
- `Success`: Whether the command completed
- `Message`: Status message
- `CameraName` / `CameraPath`: The camera that `Camera.main` resolved to and that the ray was cast from, reported on both hit and no-hit responses. When a `No physics hit` result looks wrong, check these first — another camera in the scene carrying the `MainCamera` tag can silently win the `Camera.main` resolution, so the ray may not come from the viewpoint you expect
- `Hit`: Whether physics hit anything
- `HitGameObjectName` / `HitGameObjectPath`: Hit object identity when `Hit` is true
- `HitLayer` / `HitLayerName`: Hit object layer when `Hit` is true
Expand Down