QUOTE('Naughty')
QUOTE('MiloDC')
It runs on drag-and-drop.
yeah, that's fine.. but the fact that you need instructions to play it (select tx channel and MMB-drag?) disqualifies it based on part B of rule 4): no additional actions needed
No it doesn't. The instructions are merely a courtesy; I'm sure that more people know how to play breakout than Plinko or an obscure version of Pac-Man (no offense to the writers of those great scripts).
Again, the ball pauses before the paddle is moved. If I create a button control that freezes action until the user presses it, the effect is the same.
If I want, I can remove the code that makes the ball pause before the user moves the paddle. Then the ball comes down and the user scrambles to catch it. What fun is that?
QUOTE('Naughty')
QUOTE('MiloDC')
If I have to set then reset everything in the user's environment that could possibly break my script, then I won't have much room (if any at all) to do anything else.
tough. some of us managed it.
Don't flatter yourself just yet. What we all "manage" unfortunately varies from coder to coder.
As I wrote above, Your MEL_1kCOMPO_Naughtys.mel results in an error if I run MEL_1kCOMPO_MRCOKE.mel first, while mine does not.
Likewise, in Maya 6.01, your script gets ugly to a degree of pointlessness if I set my time units to, say, milliseconds. In any version of Maya, it turns to utter ass if my up-axis is Z instead of Y.
Your code also leaves my playback loop type to "oscillate" and my playback speed to 30fps -- both of which violate rule no. 7.
And all of this is just the tip of the iceberg, baby. I could break your stuff (or anyone else's) all day long, to the point where you'd just throw up your hands and give up -- unless you people start refining the rules.
QUOTE('Naughty')
QUOTE('MiloDC')
Again, I can come up with a ton of ways to make all of our submissions useless.
You guys need to amend the rules with environmental pre-conditions.
yeah, maybe if you IGNORE the existing rules: 4.) The file must run on drag & drop into the viewport of a new Maya scene. no additional actions needed.
The rules are sound, as long as you actually bother to read and understand them.
How does my script not run on drag-and-drop? Does user input (e.g. moving a paddle or a little yellow ball) count as "additional actions"? If so, then how is that clear in the rules?
QUOTE('Naughty')
Ewerybody, if you don't force the rule about no additional actions needed in fact, you should re-word it to no additional actions ALLOWED!! then it kind of defeats the point of it being 1K, as the author can stipulate the user does all the set-up things his script should do..
Milo, please don't have a sulk-strop. Your MEL is cool, but it's not fully appropriate in this context (although it could still be with a re-write!)
and yes, I know it's all just for fun, but what's the point in having any rules at all if we're just gonna ignore them in the name of cool fun..?
What "sulk-strop"? As I see it, I broke no rules; I don't see how challenging your assertion that I have amounts to sulking.
Until now, I didn't mention the flaws in your code (which I encountered the first time I ran it), because it was clear to me that the 1K MEL rules are nebulous. It's pointless to be fastidious or haughty about nebulous rules. Check your ego.
Ewerybody has been very civil in his efforts to clarify the rules. I think his amendment to No. 4 is a step in the right direction. Why undermine that?