construct caps

read and

If you still want it, pm for it. i may change it into something new when i get time.

Amazing! Useful and very well written.

Sticky this.

I disagree. There is no information on standard methods of picking, or the SOL. The SOL is first mentioned in the "family hack" section and it's not explained exactly what the SOL is. Other sections as well need further explanation than what is given.

While, Or, Else, Trigger Once and Every X Milliseconds don't really have anything to do with picking, but they take up a good portion of your picking tutorial. For Each is the one part of that section that might be helpful, but there is no basic explanation of what For Each is, just a list of do's and don'ts. "The For Each condition... runs the actions on each instance that meet the condition(s)." How is that different from a regular event? Things like that need to be explained.

And the general tone of the writing is rather cynical, which might turn off new users by making them think that picking is a terrible chore. Which it shouldn't be if picking is explained properly. Telling the user they're in "picking hell" or calling certain conditions "a**holes" or calling a legitimate method of picking a "hack" just makes it seem like a bad thing, when it's not.

Sorry for the criticism, just my two cents.

Usually dead's not this negative about stuff, but then I saw these parts...

[quote:5k47r6vv]AKA Picking: What they don't want you to know about. You can also pre-order my soon to be released book on this subject for $50, or sign-up for a subscription to my monthly newsletter website for only $10 per month.

Huh?

[quote:5k47r6vv]Declaimer: This guide is solely based on the opinions of a novice/intermediate level Construct user. This guide is an "as is" reference. The poster cannot be held responsible for any damage done to you or your computer by following the provided advice given.

Wut?

Honestly I wish you luck with this, but perhaps you should change the attitude a bit.

Also you might want to wait a while for a finished program, wiki, and more experience.

Moved here to avoid confusion / wasting viewers time.

The double family thing is not a hack, it's just logical..

Also, the guide isn't really about picking, it's more of a general explanation of various events and Construct features, and how to use them. And subevents in a for each are great, I use them all the time.

What's wrong with using subevents under a for-each loop? It works fine...

[quote:1kvzqdp0]AKA Picking: What they don't want you to know about.

Who doesn't want you to know about this? If its not we, is it the same people who want to charge for the information on an open source project?

Declaimer?....

Stuff like that, I mean its not a war, its not difficult, and nobody here wants to obfuscate information, that's just not apparent.

I disagree. Sorry for the criticism, just my two cents.

ll criticisms are welcome [quote:37c6kqkm]There is no information on standard methods of picking, or the SOL.

There is no information about the SOL in the wiki either, or anywhere else really. Wiki links does/would of covered that stuff for more "depth" if you will. This is intended to point out the NOT so obvious things that no one seems to mention (when I can remember as I go along; hence "as is"), unless it's a explained randomly deep in a thread somewhere.

As for the tone, we are going for something more interesting here as fun theme, no one will take that seriously.

BTW Deadeye I meant to link your tutorial also somewhere - your post reminding me. Though linking straight to the wiki would cover it, because I can't remember anything specifically picking related for stuff that's complicated. The last time I downloaded was with the first couple of lessions where someone posted some wierd stuff with walking around on a circle with trig. I would need to look at ones but, it seems you say the new version broke all the caps?

Guide Stuff

Today's update will include stuff about actions, triggers, containers.

the guide isn't really about picking, it's more of a general explanation of various events and Construct features, and how to use them.

can/should rename it, but I kinda like the name. If there are appropriate wiki articles that would be linked. There's really little encouragement for me to get all technical, I probably can't anyway. :

What's wrong with using subevents under a for-each loop? It works fine...

ou are right, they do. I think the words in the guide will agree. It just points out to be careful and not get complicated with for each + sub-event.

Thanks for comments. I will continue to make updates while trying to think about those "little things" no one else remembers to document for guys like me.

Cover the basics first, then build on them. Also, I think it would be greatly productive if examples were supplied; documented, basic example cap. Use colored balls - red, yellow, blue - and show how is picking done, the differences etc.

Good point. I hope someone else considers making a guide like you are suggestiong. Unfortonately, I'd only be capable of doing that with much more experience and completing a worthy game/progject... Then I'd probably have to turn it into a book, because it'd be worth sharing the whole process and it'll have some authenticity. Right now, I can only share what (from my experienced) think should be avoided and very small bits of information I know/remember but don't see them writen elsewhere.

Summing up rest of thread:

I guess I shouldn't have wasted my time posting wiki links to every object I mention, cause apparently that doesn't matter and I have to repeat everything in there. Since links don't do any good, we could sum this up by saying: I have the same problem as Deadeye and others who didn't want to start from the very very basic; otherwise, they wouldn't write them due to boredom. But that's my problem because of the name I gave it while writing this on a whim. This is more for the users, future or present, who know enuogh of the basics, but still keep making mistakes and falling into traps because they still attempt to apply them using wrong approaches with no proof that it actually works - or they go overboard with crazy events after seeing an example, or reading a wiki article... These people usually don't need their hand held, but need a push in the right direction or a quick reference with tips that usually cause failure so they can avoid them all together. But hey, I could be wrong.

I should apologize for all the confusion. I'm used to forums where they understand something that's "cynical" when dealing with computer stuff (cause we all know computers are evil) - it's supposed to be obvious it's not serious (especially in this case because of how lame it sounds... I mean, come on...). Again, that would be my fault. I should know better than to assume.

I hope that clears stuff up. (4GOOD)

Crappy guide > no guide.

I believe that a complete newcomer to Construct would be confused after reading first few paragraphs of the guide, they don't follow your thought process quite yet. Cover the basics first, then build on them.

Also, I think it would be greatly productive if examples were supplied; documented, basic example cap. Use colored balls - red, yellow, blue - and show how is picking done, the differences etc.

That would go a long way in my opinion! Kudos for the effort so far.

> What's wrong with using subevents under a for-each loop? It works fine...

> ou are right, they do. I think the words in the guide will agree. It just points out to be careful and not get complicated with for each + sub-event.

They're not necessarily complicated or dangerous at all. They work perfectly logically like you'd expect. I'm all in favour of people writing their own hints and tips, but it should

• be correct and properly checked - for example random("n") is misleading because it does not take a string, it takes a number!
• be written by someone well experienced who knows if something really is difficult/complicated, because in the case of subevents in for each loops, there really is nothing wrong with them and that kind of advice might mislead beginners.

Man wrote that he's not that experienced to make his article worth reading. Actually I didn't understand it much probably because of having much experience already.

Edit: 1

[The person that was meant to read this already did so. No content related to guide.]

Edit: 2

I wrote this based on experience from using older builds from 2008. Now that I'm getting a chance to thoroughly test newer builds, I can say a lot of the issues that I previously commonly encounted are fixed, or there are better/newer methods to get things done. Rendering some things in this guide obsolete. (I'm tempted to remove this "guide")

A Tips and tricks thread could be useful ...for stuff that doesn't really belong in the wiki I mean.

Plus the tips and tricks can be discussed and improved (or if it doesn't make sense one could point out why).