Right. Since a lot of older users here are more experienced, it’s not about what you think. It’s about what you think the average user thinks. Put yourself in their shoes. To me, I could do this easily and probably figure it out without the guide. But a lot of people cannot. So I vote that way.
1 Like
Yeah, despite how easy it would be for some users to replicate, new and inexperienced GKC coders would have a hard time getting the grasp of this system.
1 Like
That’s why I do the the average number polls. Experience people will vote small and newer user will vote big, and it all evens out nicely.
1 Like
thats true recalledMemories
Your avatar looks familiar, yet you are new? However, welcome to the forums! If you haven’t already remember to read the guidelines.
Wait, if it checks to see if FallTime is equal to 100, adds 20 every tick you’re falling, and runs 20 times per second…
Shouldn’t you respawn after falling for one fourth of a second?
It would be 5 seconds wouldn’t it be? It adds 20 per second and 5 seconds would make it equal 100.
However, the block code makes it more like 3 seconds.
Oh, you’re talking about block speed. The 20 is the speed the block updates at. That’s why you add 20 per second to balance that out. Not the best explainer of it, but it won’t respawn every 1/4 of a second.
Bump! Awesome Guide by the way!
1 Like
oki, great guide but cant you just do this?:
make a zone wired to a respawn, because the PC device uses a lot of memory
there are too many dropdowns too…
This is an alternative that yes uses more memory, but allows the designer to make system and be done vice having to adjust zones everytime the height changes.
The dropdown amount it just fine. It keeps the guide organized and easy to read.
3 Likes
Height meter BUMP. I just realized the reusable bump…