User:Knorke/Sandbox1 - Revision history

Knorke at 22:23, 23 April 2014

2014-04-23T22:23:01Z

← Older revision		Revision as of 23:23, 23 April 2014
Line 11:		Line 11:
	* text editor with synthax coloring		* text editor with synthax coloring
	* copy of [[SpringTutorialGame]]		* copy of [[SpringTutorialGame]]
	* some small map because those load faster		* [http://springfiles.com/spring/spring-maps/aliendesert some small map] because those load faster
	* Spring set to [[Springsettings.cfg#Fullscreen\|windowed mode]] for easier switching between editor/game		* Spring set to [[Springsettings.cfg#Fullscreen\|windowed mode]] for easier switching between editor/game
	* a very bit familiar with programing (variables, functions, loops, arrays = enough)		* a very bit familiar with programing (variables, functions, loops, arrays = enough)

2014-04-23T13:16:50Z

go go gadgets time!

← Older revision		Revision as of 14:16, 23 April 2014
Line 198:		Line 198:
	We learned widgets can only "look at" the gamestate or do things that players can do, for example ordering units to attack another unit.		We learned widgets can only "look at" the gamestate or do things that players can do, for example ordering units to attack another unit.

	On the other gadgets are scripts that are able to alter the state of the game.		On the other hand gadgets are scripts that are able to alter the state of the game.
	With gadgets it is possible to implent new game logic like jumpjets, drop pods, tech tree systems, etc.		With gadgets it is possible to implent new game logic like jumpjets, drop pods, tech tree systems, etc.

	Unlike widgets, gadgets must be included in a game or in a map.		Unlike widgets, gadgets must be [[Gamedev:Structure#LuaRules.5C\|included in a game or in a map.]]

	To do so it is best to unpack the game file into an [[Gamedev:Archives\|.sdd archive]]		To do so it is best to unpack the game file into an [[Gamedev:Archives\|.sdd archive]]

Line 207:		Line 208:

	===synced & unsynced===		===synced & unsynced===
	Gadgets are split into a synced and into a unsynced part.		Gadgets are split into a synced and into an unsynced part.

	In simple terms that means the synced part is usually for controlling the game logic.		In simple terms that means the synced part is usually for controlling the game logic.

	The unsynced part is for drawig graphics.		The unsynced part is for drawig graphics.

2014-04-23T12:48:10Z

Finding errors and infolog.txt

← Older revision		Revision as of 13:48, 23 April 2014
Line 98:		Line 98:
	In that logfile you can look up all errors even if they have disappeared from chat.		In that logfile you can look up all errors even if they have disappeared from chat.
	Fix the error, reload the widget and it is green again. Oha.		Fix the error, reload the widget and it is green again. Oha.

			FIXME: expand this

	===widget sees you and only you and your allies===		===widget sees you and only you and your allies===

2014-04-23T12:46:30Z

gadgets etc

2014-04-23T03:25:43Z

I made enough "hello world" widgets. What now?

← Older revision		Revision as of 04:25, 23 April 2014
Line 181:		Line 181:
	widgets are for interface stuff.		widgets are for interface stuff.

	That usually ~~widgets~~ either...		That means widgets usually need to either...
	* ...draw something on the screen. (for example the health of Commander)		* ...draw something on the screen. (for example the health of Commander)
			and/or
	* ...give orders to units. (for example make Commander automatically run away from danger)		* ...give orders to units. (for example make Commander automatically run away from danger)

2014-04-23T00:46:55Z

Requirements

← Older revision		Revision as of 01:46, 23 April 2014
Line 14:		Line 14:
	* Spring set to windowed mode for easier switchting between editor/game		* Spring set to windowed mode for easier switchting between editor/game
	* a very bit familiar with programing (variables, functions, loops, arrays = enough)		* a very bit familiar with programing (variables, functions, loops, arrays = enough)
			* read through [[TestingYourGame\|this tips page]] once

	=Wupget and friends=		=Wupget and friends=

2014-04-23T00:44:33Z

Examples

← Older revision		Revision as of 01:44, 23 April 2014
Line 193:		Line 193:
	See these [[TestingYourGame\|pro-tips]] to make testing less frustrating.		See these [[TestingYourGame\|pro-tips]] to make testing less frustrating.

	=~~Examples~~=		==Look at more examples==
	Common hint for learning spring Lua is: ''"Look at some examples in other games."''		Common hint for learning spring Lua is: ''"Look at some examples in other games."''

	But a spring game usually has dozen of wupdgets and only a few are useful examples for beginners. Many scripts deal with some very specifique problem or are just way too long.		But a spring game usually has dozen of wupdgets and only a few are useful examples for beginners. Many scripts deal with some very specifique problem or are just way too long.
	Or one has to be familiar with the game to even understand what the script even does.		Or one has to be familiar with the game to even understand what the script even does.

2014-04-23T00:42:30Z

2014-04-22T23:08:58Z

2014-04-22T13:32:11Z

test