We use const to declare a constant string, similar to the original Go code.
Instead of len(), we use the length() method to get the string length.
GDScript doesn’t have a direct equivalent to Go’s byte-level access, so we use ord_at() to get the Unicode code point of each character.
For rune counting, we simply use length() as GDScript strings are already Unicode-aware.
We use a for loop with range() to iterate over the string, which is similar to Go’s range loop.
Instead of utf8.DecodeRuneInString, we directly index into the string to get characters.
We use unicode_at(0) to get the Unicode code point of a character.
The examine_character function works similarly to the Go version, comparing characters directly.
Note that GDScript handles Unicode strings more transparently than Go, so some of the complexity in dealing with UTF-8 encoding is abstracted away. The output will be similar, but the byte-level details are not exposed in the same way as in Go.