Skip to content
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.

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

Vector4i is referred to as Vector3i #8802

Closed
ScriptlessWeek opened this issue Jan 20, 2024 · 0 comments · Fixed by godotengine/godot#87523
Closed

Vector4i is referred to as Vector3i #8802

ScriptlessWeek opened this issue Jan 20, 2024 · 0 comments · Fixed by godotengine/godot#87523
Labels
area:class reference Issues and PRs about the class reference, which should be addressed on the Godot engine repository bug content:proofreading Issues and PRs related to proofreading the documentation
Milestone

Comments

@ScriptlessWeek
Copy link

ScriptlessWeek commented Jan 20, 2024

Godot 4.2

Vector4i documentation

Under Notes in the Description it says:

"In a boolean context, a Vector4i will evaluate to false if it's equal to Vector4i(0, 0, 0, 0). Otherwise, a Vector3i will always evaluate to true."

It is referred to as Vector3i instead of Vector4i.

https://docs.godotengine.org/en/stable/classes/class_vector4i.html#class-vector4i

This is my first ever bug report on Github. If this isn't how I'm supposed to do this please tell me.

@AThousandShips AThousandShips added area:class reference Issues and PRs about the class reference, which should be addressed on the Godot engine repository content:proofreading Issues and PRs related to proofreading the documentation labels Jan 20, 2024
@AThousandShips AThousandShips added this to the 4.3 milestone Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:class reference Issues and PRs about the class reference, which should be addressed on the Godot engine repository bug content:proofreading Issues and PRs related to proofreading the documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants