About the scripting answers

[12p]

I didn't want to make off-topic replies on a certain post I've speak at.

both 50p and John_Michael are right.

John's truth: It is okay to leave errors, so they have to fix it. And with the fixing, they learn.

50p's truth: BUT you should tell him there's an error. Otherwise they could say "omg it is not working you bad scripter blahblah fix it please"; they will do nothing, they won't learn anything, etc... You should already know how do people react.

We could do like Towncivilian does; have a copy-paste "code":

Install the latest patch

Install the latest DirectX runtimes

etc...

BUT applied to scripting.

EXAMPLE 1

Do what I do when I give an answer to a scripting question:

Check following documentation, please.

guiCreateWindow 
guiSetSize 
guiGetText 
triggerServerEvent 

EXAMPLE 2

Give whole code with errors, and tell the one who asks, to find it debugging, and fix them.

Here you go.

--Code 

NOTE: This script has errors. Use debug to find them, and fix them yourself.

EXAMPLE 3

Tell the guy what does he need to do (with the needed functions), and give him a link to the wiki.

You need to create a window (guiCreateWindow), create a button on it (guiCreateButton), and give the button and event handler. In this one, tell the server (triggerServerEvent, addEvent) to create a vehicle in front of the player with createVehicle, you could use the useful function called "getPointFromDistanceRotation" to spawn it IN FRONT of the player... And you're done Here, you can find all of those things: https://wiki.multitheftauto.com

Tell what do you think, which should we use, or do whatever you want.

But we cannot act like Dev does (no offense, dude, but you're not acting in the right way), giving whole code with fails, no comments to aid the guy who asks to understand, or anything.

Edited November 24, 2011 by Guest

[unknooooown]

I agree..

I just think its gonna be hard to pick one of your examples that we always would have to use.

Some people have no idea what they should do.

If we can see from the first post, that "this guy" has no idea what he is doing and probably never will, then its either keep helping like we do now or turn him down.

Making code with errors in for people to fix, or at least comment the line where the bug is, would be a nice way if we could make it work. People would learn much more that way. If you look at my posts you will see that I started scripting about 5-6 months ago. Sure I asked a lot of studpid questions to begin with, but most of the time I only had to ask once. I got my answer, tried it a lot of times and learned how to use it.. ( Still ask stupid questions.. )

Most people that we help in here most likely quit scripting after a few weeks, but there are some people out there that really want to learn.

Its a tough question Benxamix2

[12p]

I agree..

I just think its gonna be hard to pick one of your examples that we always would have to use.

Some people have no idea what they should do.

If we can see from the first post, that "this guy" has no idea what he is doing and probably never will, then its either keep helping like we do now or turn him down.

Making code with errors in for people to fix, or at least comment the line where the bug is, would be a nice way if we could make it work. People would learn much more that way. If you look at my posts you will see that I started scripting about 5-6 months ago. Sure I asked a lot of studpid questions to begin with, but most of the time I only had to ask once. I got my answer, tried it a lot of times and learned how to use it.. ( Still ask stupid questions.. )

Most people that we help in here most likely quit scripting after a few weeks, but there are some people out there that really want to learn.

Its a tough question Benxamix2

Yeah, I think you're right ^^

[qaisjp]

1. We cannot give errors in every script we give, that is just misleading. Only sometimes, and if we have realised the person has debugged it themselves afterwards.

2.

But we cannot act like ^Dev-Point^ does (no offense, dude, but you're not acting in the right way), giving whole code; with fails, no comments to aid the guy who asks to understand, or anything.

Giving whole code, but also fails in making it? and then shows ' '

[12p]

Have you looked at his codes?

Well, what's your answer about this topic. Shall we use another example?

[qaisjp]

Yea

[12p]

Show us.

Don't stay there just saying "yes".

[CapY]

Why, this examples are quite good.

[unknooooown]

Why, this examples are quite good.

Derp.. Which one? There are 3...

[CapY]

First 2

[NotAvailable]

If i was you i would change

^Dev-Point^

To something else.

Or ask ^Dev-Point^ for permission.

See... Everybody started like ^Dev-Point^. Posting topics asking for help etc.

But he's atleast trying to help people and learning lua at the same time.

Kind Regards,

Jesse

(Please, don't see this post as a negative post)

[BinSlayer1]

Example 3 combined with Example 1 in general, but if the code is easy as pie give it fully