Posts: 144
Threads: 22
Joined: Feb 2011
I just looked at the scripting thread, and I am impressed to say the least. It look like it'd be alot of fun to make all of those, but I have no idea where to start.
Soooo, can someone tell me
What language is used?
Where to put them when you make/get them? (in the autoexec?)
Where can I learn the language? (don't answer if it's c++ or something well known)
I've done some small menu editing and stuff, but I have no idea where to start with actually writing scripts. . .
Sorry if this is posted somewhere else. . .
Posts: 1,331
Threads: 44
Joined: Jun 2010
04 Mar 11, 12:30AM
(This post was last modified: 04 Mar 11, 12:31AM by Bukz.)
It uses a special scripting language specific to cube engine games called "CubeScript". The original game "cube 1" had the first implementation of it AFAIK. It was quite basic back then but has had many advancements throughout the years.
Here are some good links to check out if you're a beginner trying to figure out wth is going on with all that mumbo jumbo :P
AssaultCube Reference (list of cubescript commands)
AssaultCube CubeScript Tutorial
CubeScript @ AC Wiki
AC CubeScript Documentation
Read through that and start playing around with your first basic scripts! :D
Posts: 144
Threads: 22
Joined: Feb 2011
Posts: 3,462
Threads: 72
Joined: Jun 2010
I am very disappointed in you Bukz. You can ask real time in IRC: #cubescript @gamesurge.net
You can connect
here if you so wish.
We will be happy to help :)
Posts: 1,823
Threads: 20
Joined: Jun 2010
04 Mar 11, 03:22AM
(This post was last modified: 04 Mar 11, 04:06AM by Gibstick.)
I think Cube 1 didn't even have semicolons in CubeScript, because I've seen code that looked like
bind E [(&& (edittoggle) (fullbright))]
Posts: 3,462
Threads: 72
Joined: Jun 2010
Which is bad code, because there is no closing )...
Just sayin.
Posts: 1,823
Threads: 20
Joined: Jun 2010
Posts: 3,780
Threads: 33
Joined: Jun 2010
04 Mar 11, 08:35AM
(This post was last modified: 04 Mar 11, 08:36AM by V-Man.)
Semicolons are more or less a (sometimes redundant) way to explicitly state that you are bringing the current command to a close.
If a command has all its arguments filled (or completely encapsulated in square brackets or parentheses), it doesn't need a semicolon.
A hard return functions nearly the same way as a semicolon, except that it is not treated as an actual character.
Just sayin.
