Blockland Forums > General Discussion
The client event topic!
Killer2:
How is white F9F9F9?
Anyways, if you can't fit everything on one event, take how long the first one is and multiply it by 1000 and use that as the delay for the next event.
phflack:
--- Quote from: Killer2 on January 17, 2011, 03:51:00 PM ---How is white F9F9F9?
Anyways, if you can't fit everything on one event, take how long the first one is and multiply it by 1000 and use that as the delay for the next event.
--- End quote ---
a darkish white -> grey
phflack:
--- Quote from: Nexus on January 17, 2011, 03:20:29 PM ---no, that's dumb. There would be doubles and no prime numbers. the way I showed you gets all numbers exactly once.
--- End quote ---
so, it can't talk? i know it can't
i'll see if fa is the same as af next time i'm playing..
also, with your method, what would ff be?
16*16 = 256, + 16 = 272, ooh look, it went over the maximum!
Snaily:
To expand on Blaze's tip, instead of relays, use printDecrements. That way, it is client sided; you keep the event loop even after you die.
0 onActivate -> self -> decrementPrintCount -> 9
0 onActivate -> self -> decrementPrintCount -> 1
100 onPrintCountUnderflow -> self -> decrementPrintCount -> 9
100 onPrintCountUnderflow -> self -> decrementPrintCount -> 1
onPrintCountUnderflow -> self -> VCE if Value -> ...
(Make sure to make a delay)
Also, you may want to make the activate event disable itself as to not allow anyone else to 'steal' your event loop.
phflack:
hmm, you don't keep the relay loop on death? i thought you did, it's just that print counts can target the client directly without need of VCE
and the minimum delay for a print loop is 33 i think, and there can be multiple loops on the same brick so no need to disable the input :D