what should i write here?
is anyone out there close to finishing there dmod? im bored!
Yeah,It's only a year left!
Ohh Path that was funny !!
I shall attempt to complete mine within 6 months Any takers for less...
I shall attempt to complete mine within 6 months Any takers for less...
You'll see mine on the DN soon.
No.
Though my 2.0 version of the scourger should come out in about a month or so.
Though my 2.0 version of the scourger should come out in about a month or so.
if i learn to script, i shall have a dmod...sooner or later...
You should learn to script
I also had a pretty awesome D-Mod I was about to release, but it went lost with my fresh Windows 7 installation.
I also had a pretty awesome D-Mod I was about to release, but it went lost with my fresh Windows 7 installation.
Awesome? Glenn had an awesome D-Mod in making?
Awesome? Glenn had an awesome D-Mod in making?
Yep
The Scary Beast?
Yep
all the scripts ive tried to make epicly fail
Aww, remember to create threads if there are some scripts that you need help with
Yep
The Scary Beast?
Yep
all the scripts ive tried to make epicly fail
Aww, remember to create threads if there are some scripts that you need help with
i cant do something as simple as making a sign say something, dose anyone know how to explain scripting in a way that a 11 year old can understand?
You can refer to DinkC reference...
Three Amulets is not too far from beeing compleated, and to tell the truth I think it's quite awesome myself
And for you, bornfree15 I recommend this.
And for you, bornfree15 I recommend this.
I sympathize with you, when I'm working with Battle for Wesnoth, the markup language is simple and precise. When I look at a few Dink files or the scripts shown in "Dink Goes Boating" it looks like a jumbled mess. To someone with basic programming experience. I'll probably learn eventually (it took me 2 months and atleast 3 threads to learn WML, I give Dink scripting 1 year and 15 threads, but that's a rough estimate.)
Well, some simple 'rules' for DinkC; (These rules are called syntax, but you don't need to know that)
1. All commands that do something (not IF or GOTO) must have a semicolon ';' after them
2. Each script is broken into procedures each with it's own name, the most common are: main, talk, touch, hit
3. Procedures must have 'void' before and after (I'm not too sure on this but that's how I've always done it)
4. Certain things must be closed, these start with braces and end with braces '{}'
Hope that helps...
1. All commands that do something (not IF or GOTO) must have a semicolon ';' after them
2. Each script is broken into procedures each with it's own name, the most common are: main, talk, touch, hit
3. Procedures must have 'void' before and after (I'm not too sure on this but that's how I've always done it)
4. Certain things must be closed, these start with braces and end with braces '{}'
Hope that helps...