Suggestions for extra (interactive) CRPL tutorials on wiki

[TheDutcher]

Heya folks,

Basically thought I'd start a threat where people can post ideas of new tutorials they'd like to see.
The idea behind this is that (I think) it's best to teach and explain something to somebody, instead of somebody having to ask questions constantly or copy code from others (where the reasons why that code works is often not told).

If there's enough demand for a certain tutorial I'll (or well, other people are free to do so too) create a page and make a little start, or perhaps the entire thing. It's then upto other people to finish it and decide whether or not that tutorial's content should be changed.

For moderators:

Spoiler

If anything I just said isn't right to do / is false / we're not allowed to do feel free to make a post or send a message and I'll change or delete the topic.

[close]

[warren]

is there a tutorial for, {a custom flying unit, a custom interface button, end of game dialogue, a boss monster, adding special graphics to terrain, creating new enemies and terrain mid game, effectively using the debugging and testing tools available, creating and targeting a fake mortar shell, screen shake effect, wrapping creeper past map edges, creating 50% built player units mid game, a self powered blaster that cannot be selected}?

[TheDutcher]

is there a tutorial for, {a custom flying unit, a custom interface button, end of game dialogue, a boss monster, adding special graphics to terrain, creating new enemies and terrain mid game, effectively using the debugging and testing tools available, creating and targeting a fake mortar shell, screen shake effect, wrapping creeper past map edges, creating 50% built player units mid game, a self powered blaster that cannot be selected}?

As I said, this place is for suggestions. If people actually show they want to get to learn such things a tutorial can be made.
I'm thinking about making a page on the tutorial branch concerning suggestions for tutorials, since not everybody that wants to learn CRPL reads the forums (and not everybody the wiki either).

[Xeos]

I have to say that it is hard if you are new to coding when there is limited info on things you want to do(that you can understand). So when I see something that I like in a map, I download it, get the scripts and look at them and mostly have no idea how they are working. It is only by many hours of experimenting and making test maps that I finally find out how to do something. My coding (if it works) is probably laughable but I do not know a better way. I just find ways that work.
There are often specific functions for what I want to do but sometimes I just can't understand enough about them to use them properly so I find a workaround. I'm not really learning much because I then have to use that workaround again because the method I should use I don't know enough about it to use it properly.

I commented earlier on a post by Grayzzur https://knucklecracker.com/forums/index.php?topic=18102.msg129176#msg129176

He explained it perfectly and I understood from that post the basic way to get lists working and then the more advanced way.

I know there are some great coders in these forums. When I look at some of the coding, the form of it looks poetic even and it blows me away, but you all had to start somewhere and there are quite a few of us that  need a little help and I know for one, that when someone takes some time to show us something, it puts a big smile on our faces when we 'get it' and we really appreciate the effort you guys have made.

Don't think we are asking you to write our code for us, just point us in the right direction that's all and I for one will be very grateful :)

Many thanks in advance
Xeos (Ian)

p.s I have had some help from a few of you already which has been invaluable. I thank you all for that :)

[warren]

I would like to point out that the purpose of a tutorial is not to show how to do a thing, but to show how to do a category of things, with a basic example selected from that category for illustration, and side discussion for features that may be required for more advanced cases.

Also, it always takes many hours to code. Unless it is something simple, then it only takes many hours to code the first time.

[TheDutcher]

I would like to point out that the purpose of a tutorial is not to show how to do a thing, but to show how to do a category of things, with a basic example selected from that category for illustration, and side discussion for features that may be required for more advanced cases.

You should note that, even though a tutorial should explain a couple things at a time (not to less, but not too many either), it's still best to put a tutorial in something practical. So still, you will have to create SOMETHING, and tell how you code that something.