You know what, just all stop.
We already lost enough good guides-
your “challenging discussions” have literally nothing to do with “Repeater and Looping.”
Honestly this place should have maybe strict reinforcement like the banana guide.
That guide got closed down for excessive amounts of off-topicness, but this guide helps to challenge the way we think about devices and how we can innovate our maps to be more efficient. But I don’t think for most replies this is happening so far.
The best option would be to probably keep this close- or, option 2, we can strictly keep on-topic and don’t hesitate to flag. Honestly not even worth it to keep it open if this keeps happening.
That’s a good point Getrithekd. Maybe we go with option 2 then
You don’t stop off-topic stuff from closing a perfectly good guide. You do it by punishing the people who post off topic.
Why can’t we all EVER be on topic…? Is it that hard to go to a discussion and sick with it? What’s so hard about it? You say your gonna be on topic but you don’t. It’s so annoying how you just won’t listen, ESPECIALLY if you’re a regular. Regulars are role-models for this community and should act as one. Many people look up to you guys and you set bad examples. The second you say your gonna be on topic your going off topic AGAIN. MAKE IT MAKE SENSE
We already stopped the conversation about whoever is off-topic or not, please don’t encouraging more off-topic and inappropriate behavior by posting this.
Please don’t damage to this guide any further, this is to everybody.
Ok, for @Fleet (In a desparate attempt to get back on topic)
If you get a lifecycle, and set it to “Game Start,” it only transmits upon the host, because the host triggered the game to start.
Now if we get a trigger (player-scoped) that is deactivated on default, yet on game start, you activate it.
So once you get a KO that triggers the trigger, every pulse is blocked, except for the host’s pulse.
Code is inactive:)
Mechanism with counter, that counts the host’s knockouts.
Ironically the argument about whether this post should be closed has caused more chaos than the post itself.
I did notice that someone mentioned that the issue is not with the post itself, but rather with the people who reply to it. I would definitely appreciate if you all see someone behaving problematically, if you were to flag them and also append a note to the flag asking me to look into their behavior. Due to my studies, I don’t have time to just idly browse the forums, so I can’t figure that stuff out as easily.
I’d also like everyone who holds themself up as someone to tell others to get back on topic to take a hard look at themselves, because those people seem to be the most off topic in the first place.
This topic will remain open, as it holds legitimate grounding as an educating and thought provoking post (as can be seen by most of the comments)
Have a great day you all!
This topic was automatically opened after 16 hours.
the bug your trigger it’s not orange just like the bug topic but umm so what does this do?
It’s because it’s deactivated.
That would work, but it would take up way more memory than just using a repeater…
Sorry if I sound rude, I’m just saying that it uses a lot of devices.
more devices don’t mean more memory
it takes like 150 memory if not less… meanwhile the repeater takes up 400 (and 500 on first placement)
Fair.
bro that’s kinda true…
In addition to what eiq said, when the maps are high memory repeaters lag and won’t repeat exactly at the amount of time you set. Trigger loops do not.
Actually, trigger loops lag like crazy. They’re some of the most inconsistent things in the entire game. I’m pretty sure repeaters lag a bit less. Trigger loops only lag by tenths of a second though, so it’s not gonna matter for the majority of games (especially if everything is run on the same trigger loop).
wut about a wire repeater loop
Less inconsistent, but I’m sure there’s some observable lag.
@gimkitnoobie please no
i’ve done that
it’s awful
please no
@TheMostCcute what’s the solution for?
another solution (button>wire repeater 1, button>wire repeater 2, wire repeater 1 specifications>cooldown 1, wire repeater 2 specifications>cooldown>0.0 seconds)