Scripting - Revision history

Scratch: /* Workflow */

2017-06-27T11:22:33Z

‎Workflow

Scratch at 11:22, 27 June 2017

2017-06-27T11:22:20Z

Scratch: /* Workflow */

2017-06-27T11:22:00Z

‎Workflow

Scratch at 11:20, 27 June 2017

2017-06-27T11:20:56Z

Renesackers: Reworded IDE section, and added Visual Studio code extension and links.

2017-06-24T14:02:18Z

Reworded IDE section, and added Visual Studio code extension and links.

Scratch: /* IDE */

2017-06-22T10:35:52Z

‎IDE

Scratch: Created page with "Scripts in Serious Sam's Bogus Detour are written in [http://www.angelcode.com/angelscript/ Angelscript]. For a reference overview of the scripting language, check out [http:/..."

2017-06-22T10:25:23Z

Created page with "Scripts in Serious Sam's Bogus Detour are written in [http://www.angelcode.com/angelscript/ Angelscript]. For a reference overview of the scripting language, check out [http:/..."

New page

Scripts in Serious Sam's Bogus Detour are written in [http://www.angelcode.com/angelscript/ Angelscript]. For a reference overview of the scripting language, check out [http://www.angelcode.com/angelscript/sdk/docs/manual/doc_script.html "The script language"] on the Angelscript website.

== Script types ==
=== Game modes ===
Gamemodes define rules about what should happen on the global level. A gamemode is for example campaign, survival, deathmatch, team deathmatch, etc. See also [[Creating a GameMode]].

=== World scripts ===
Worldscripts are the in-editor visual scripting elements. Scripts have properties that can be set in the editor, they can target each other or other units, and they are only visible within the editor. In the game, only their functionality remains. Examples of worldscripts include SpawnUnit, AreaTrigger, LevelStart, LevelExit, Variable, ChangeVariables, etc. See also [[Creating a WorldScript]].

=== Behaviors ===
Behaviors are the brains of units. Each unit can have a behavior, which allows them to have logic such as movement or interaction. For example, this could be a Pickup, Breakable, CompositeActorBehavior, Player, etc. See also [[Creating a Behavior]].

== IDE ==
There is currently not a lot of good IDEs available that autocomplete Angelscript, sadly. Therefore, we recommend you use an advanced text editor such as Sublime Text or Notepad++. For Sublime Text, there is a pretty good [https://github.com/wronex/sublime-angelscript syntax highlighter for Angelscript] that you can install.

== API reference ==
You can find the API reference for the engine [http://ssbd.a000ff.com/docs/engine/ here], and the API reference for the base resources [http://ssbd.a000ff.com/docs/scripts/ here].

@@ Line 13: / Line 13: @@
 == Workflow ==
-By far the best way to work is by having the editor open together with an IDE. After [[Creating a Scenario|creating a scenario]], make a test level in your scenario and add your gamemode/worldscript/units to it. Then, after writing some code in your IDE, simply Alt+Tab to the editor and hit Ctrl+T to open the game.
+By far the best way to work is by having the editor open together with an IDE. After [[Creating a scenario|creating a scenario]], make a test level in your scenario and add your gamemode/worldscript/units to it. Then, after writing some code in your IDE, simply Alt+Tab to the editor and hit Ctrl+T to open the game.
 [[File:ScriptingWorkflow.png|900px]]

@@ Line 13: / Line 13: @@
 == Workflow ==
-By far the best way to work is by having the editor open together with an IDE. After [[Create a Scenario|creating a scenario]], make a test level in your scenario and add your gamemode/worldscript/units to it. Then, after writing some code in your IDE, simply Alt+Tab to the editor and hit Ctrl+T to open the game.
+By far the best way to work is by having the editor open together with an IDE. After [[Creating a Scenario|creating a scenario]], make a test level in your scenario and add your gamemode/worldscript/units to it. Then, after writing some code in your IDE, simply Alt+Tab to the editor and hit Ctrl+T to open the game.
 [[File:ScriptingWorkflow.png|900px]]

@@ Line 15: / Line 15: @@
 By far the best way to work is by having the editor open together with an IDE. After [[Create a Scenario|creating a scenario]], make a test level in your scenario and add your gamemode/worldscript/units to it. Then, after writing some code in your IDE, simply Alt+Tab to the editor and hit Ctrl+T to open the game.
-[[File:ScriptingWorkflow.png]]
+[[File:ScriptingWorkflow.png|900px]]
 == IDE ==

@@ Line 10: / Line 10: @@
 === Behaviors ===
 Behaviors are the brains of units. Each unit can have a behavior, which allows them to have logic such as movement or interaction. For example, this could be a Pickup, Breakable, CompositeActorBehavior, Player, etc. See also [[Creating a Behavior]].
 == IDE ==

@@ Line 12: / Line 12: @@
 == IDE ==
-There is currently not a lot of good IDEs available that autocomplete Angelscript, sadly. Therefore, we recommend you use an advanced text editor such as [https://www.sublimetext.com/ Sublime Text] or [https://notepad-plus-plus.org/ Notepad++]. For Sublime Text, there is a pretty good [https://github.com/wronex/sublime-angelscript syntax highlighter for Angelscript] that you can install.
+Unfortunately there are currently no full IDEs available for autocompletion with AngelScript. Here's what's currently available in terms of syntax highlighting and basic autocompletion:
 == API reference ==
 You can find the API reference for the engine [http://ssbd.a000ff.com/docs/engine/ here], and the API reference for the base resources [http://ssbd.a000ff.com/docs/scripts/ here].