Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Nullable type on Vector3 causing error in older project

Open
#1,482 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
game-dev

Research direction

Start by opening the linked issue #938 and the attached MRP, then reproduce the error in Redot 26.3 RC2 using the reported conversion from Redot 4.3. The issue does not identify the responsible source file or test, so trace the debugger error to its code path. Done means the converted project no longer errors when the Vector3 value is Null, with a regression test covering the case.

Written by the indexing model from the issue text.

Description

bug confirmed topic:gdscript usability
Tested versions

REDOT 26.3 rc2 for Windows
Converted MRP project from REDOT 4.3

System information

Windows 11 Home, i5, Nvidia 5060 GTX

Issue description

While going back through some earlier bugs, I came across this error. While looking into an older MRP from this issue:
https://github.com/Redot-Engine/redot-engine/issues/938
I converted the MRP from Redot 4.3 to Redot 26.3 RC2, and immediately received en error from a Vector3 in the project that was set to Null.

Steps to reproduce
  1. download the MRP
  2. load the project into Redot 26.3 RC2
  3. The Null error should appear immediately in the debugger.

Dave also found the error, plus found a temporary fix, which I have posted here with the MRP

Minimal reproduction project (MRP)
Image

issue-938-MRP-WIP.zip

Dominant language
C++
Stars
6.1k
Forks
337
Avg merge
1d 1h
Merged PRs (30d)
41

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Redot-Engine/redot-engine

All issues in Redot-Engine/redot-engine

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.