What do you want to see?
 

I've written a few articles on various subjects (Textured backgrounds, JJ1 water, Limit Visible Region...) but they don't seem to get many responses, so maybe I'm not finding a target audience. And yet I like writing articles. So, what do you, the general public, want to see documented? Bridges in JJ1? Water in JJ2? Binary trigger systems? Anything? Just give me some idea, and if I like it, I'll try to document it for you.
(Obviously, the chances of any one idea being taken are increased if more than one person wants it.)

How to make a fully automated Roast Tag level with triggers.

A way to isolate splitscreeners in Multiplayer modes.

Pyro: What do you mean by isolate? Do you want a program that bans anyone using splitscreen from your server? Do you want them separated into two different places despite appearing at the same time? Or what?

BlurreD: That would be nice, but I don't see how Roast Tag could be automated...how would you keep track of who is "it"?

Binary trigger systems might be nice to have documented publicly.

The problem is people on splitscreen share the same trigers right?
well, maybe allow the first player to play, and keeping the others trapped in a box, or just trapping anyone who's in splitscreen

Untested
 

J
S
S
S
G
C
W

J = Jazz Start Pos.
S = Down Sucker Tube.
G = Regenerating Gold Coin.
C = Coin Warp (needs five coins) that leads to the main level.
W = Warp which leads to an isolated box.


In theory that should work, though splitscreen and lag are a dangerous thing, so I doubt it'll be foolproof.

Of course, just kicking splitscreeners would work a lot better. It's not like splitscreeners are a major problem.

And Syntax, I realized that already, but I was hoping to pose a challenge for Violet. From what I can tell, the only way Roast Tag could be easy to manage is with some sort of memory editing program (which no one wants to make).

Ok.

As those of you in my server just now saw, no cigar. I assumed that roast tag involved the person who was it doing the tagging, instead of the other way around, so that didn't work out. I'm not sure how to make it automated in the way that was intended, and what I did make didn't quite work either. So...

anything else?

It's not that they get no respsone, most people just don't post comments. I found them sort of useful for a few levels I was creating, altough they contained little info I didn't know. It's just useful to have stuff documented in an easy to read way.

maybe an article about all the oddities concerning CTF bases

I read all of your articles, I just find it stupid to post a comment like "Good article." or "Hey, that's smart."

Binary Trigger Systems? Do explain.

When you kill the leader in Assassination, it scores a point to the opposite team of the leader. How does it work?

It's just a simple glitch with CTF bases that EvilMike exploited. It works like this: if a red player passes through two blue bases in a row, he scores once for blue team and keeps the second blue flag. Same thing vice versa.

So, why don't people use it on teambattle levels?

Because you do keep the flag afterwards. The reason it works for assassination is that only one person can go to the bases, and that's the person who already has the flag. With more people, you'd have to have several double sets of flags, and that could get complicated, and people would end up going into the wrong hole at some point. I suppose one could try a random pool effect using triggers, but it wouldn't be good if anyone joined the server... ah, but it's a JDC event, anyway, sometimes, right? Why isn't Team Battle done like that? What am I not thinking of right now?

Pyro: All the oddities? Hmm. That sounds like it might be interesting. Ok, so it looks like CTF Bases or Binary Triggers for now. Anyone want to tilt the decision a bit?

Hey! I found that glitch and made the first Team Battle level with it. Mike just made a better one that actually worked.

But Mike still exploited that glitch within the first Assassination level ever created. And I didn't say he found the glitch anyway.

Since no one is posting here, how about a way to make an event (like a coin, a powerup, or let's say a shield) only attainable to one person when two or more people try to get it at the same time. Something that works with lag and is easy to implement.