deck26 wrote:

sussybaga-123 wrote:

the system uses a steping function, where after each dot is placed it will look for the next number in the hailstone number list and put a point there on the graph. please just look at the code instead of just making asumptions

deck26 wrote:

sussybaga-123 wrote:

the dots on my graph shouldnt have any way of changing their y axis after doing it the first time but they do it anyways. the dots are coded in sprite 4 of my project. Also if anyone has ideas on how to shrink the code at all i would love to hear it bc there are massive chunks of code. Posting this again because the only reply sent the exact opposite of what i wanted. I cannot just put
forever
set y to (y value)
end
because there can be different amounts of dots, i am not creating 100 variables named y value
If you use a list each hailstone just needs to access its own item in the list. Just give each clone a unique number and it can access that list item. I can't make sense of how to see the problem.

the system uses a steping function, where after each dot is placed it will look for the next number in the hailstone number list and put a point there on the graph. please just look at the code instead of just making asumptions
Not sure who that's addressed to but I did try to look at your code but couldn't make sense of the project more generally. If we can't replicate the issue it makes it harder to help so it is up to you to help us to help you.
why didnt you just try the system to see what i was talking about.