GDQuest / GDQuest/learn-gdscript

"Lesson 23 - Excercise 2: Realign the train tracks" problem to understand task

Open
#977 0 comments 1 reaction 0 assignees View on GitHub
content
Dominant language
GDScript
Stars
2.8k
Forks
235
PR merge metrics
No merged PRs in 30d

Description

**Issue description:**

From the goals description, i understand the situation as follows:

some train tracks are misaligned. my task is to align the tracks and do that from the end ("with negative indices"). i don't understand why the last part is important. i also don't understand what `align()` does exactly, because there is no reference

so i align _every_ track, starting with the last one. then every track should be perfectly aligned, right? (no)

![Screenshot from 2024-08-11 18 06 21](https://github.com/user-attachments/assets/56ffba01-3a48-4bd0-b2af-6871fb4d73e6)

My Code:
```
func fix_tracks():
var tracks_size = tracks.size() - 1
print(tracks_size)
for i in range(tracks_size):
print(i)
align(tracks[tracks_size - i])
```

Maybe the part "You have to find them..." is important here. How should i find misaligned tracks? Should i do that by looking at the visualization or create a function?

I did not need the information in the hints. I would need hints that lead me to the solution, or a better description of the goal in the first place.

maybe i'm thinking too complicated.

i have to look at the solution now (ohh)

---

latest offline course [downloaded from itch.io](https://gdquest.itch.io/learn-godot-gdscript). not sure if that is identical to the last release from github (1.5.2)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with Lesson 23 – Exercise 2 and compare its goals, hints, and solution, checking whether the itch.io version matches GitHub 1.5.2. Done means the exercise text or hints clearly explain why negative indices matter, what align() does, and how learners identify the misaligned tracks.

Written by the indexing model from the issue text.

Assessment

Tech stack
godot
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.