Simple Game Tutorial - Revision history

Flozi: /* Step 3:Making a 3D Model */ update link

2013-10-29T18:14:08Z

Step 3:Making a 3D Model: update link

← Older revision		Revision as of 19:14, 29 October 2013
Line 38:		Line 38:
	Go into your 3D modeling program and make a 3D model, [http://taspring.clan-sy.com/w/images/b/b4/WingsCombine.PNG combine] all the objects and UV map the model, then separate it out into any parts that need to move independently of each other. Then Export the UV map as an Image File and Export the whole thing as a 3ds file. Put the original wings file, the UVMap image and the 3ds file into your working directory so you can find them later.		Go into your 3D modeling program and make a 3D model, [http://taspring.clan-sy.com/w/images/b/b4/WingsCombine.PNG combine] all the objects and UV map the model, then separate it out into any parts that need to move independently of each other. Then Export the UV map as an Image File and Export the whole thing as a 3ds file. Put the original wings file, the UVMap image and the 3ds file into your working directory so you can find them later.

	Wings 3D UV Mapping tutorial has been started here - [[~~Units~~:~~CreateModel~~]]		Wings 3D UV Mapping tutorial has been started here - [[3DModels:Wings3DTutorial]]

	==Step 4:Fixing Your Images==		==Step 4:Fixing Your Images==

Flozi: snip wanted page link

2013-02-22T01:31:59Z

snip wanted page link

← Older revision		Revision as of 02:31, 22 February 2013
Line 1:		Line 1:
	{{deprecated\|This page is out of date and has been marked for review.}}		{{deprecated\|This page is out of date and has been marked for review.}}
	[[Category:Deprecated]]		[[Category:Deprecated]]

	~~Until I Finish [[Mod Development]] is the place to go.~~

	This Tutorial Aims to get a person from knowing nothing about Spring to the point where they can create and edit mods.		This Tutorial Aims to get a person from knowing nothing about Spring to the point where they can create and edit mods.

Sinbadev at 12:51, 1 June 2012

2012-06-01T12:51:38Z

← Older revision		Revision as of 13:51, 1 June 2012
Line 1:		Line 1:
	[[~~template~~:Deprecated]]		{{deprecated\|This page is out of date and has been marked for review.}}
			[[Category:Deprecated]]

	Until I Finish [[Mod Development]] is the place to go.		Until I Finish [[Mod Development]] is the place to go.

Sinbadev at 12:49, 1 June 2012

2012-06-01T12:49:23Z

← Older revision		Revision as of 13:49, 1 June 2012
Line 1:		Line 1:
			[[template:Deprecated]]

	Until I Finish [[Mod Development]] is the place to go.		Until I Finish [[Mod Development]] is the place to go.

Line 453:		Line 455:
	*If it doesn't work, check you didn't zip the folder itself, but the contents, ie if you open mymod.sd7 with 7zip, you should see folders such as "unittextures" rather than a folder "mymod" containing unittextures.		*If it doesn't work, check you didn't zip the folder itself, but the contents, ie if you open mymod.sd7 with 7zip, you should see folders such as "unittextures" rather than a folder "mymod" containing unittextures.

	[[Category:Game development]]		Old Category:Game development

Abma: /* Making a New Mod with your unit/units */

2012-01-02T21:32:11Z

Making a New Mod with your unit/units

← Older revision		Revision as of 22:32, 2 January 2012
Line 249:		Line 249:

	====Making a New Mod with your unit/units====		====Making a New Mod with your unit/units====
	The following is an example of what will be in your modinfo.lua file if you are starting from scratch and making your own mod. This is also good when you are just testing one unit to see if it works.		The following is an example of what will be in your [[modinfo.lua]] file if you are starting from scratch and making your own mod. This is also good when you are just testing one unit to see if it works.

	<pre>		<pre>

Abq911: Fixed broken links and bad spelling, still needs some links to be fixed.

2011-07-27T05:24:41Z

Fixed broken links and bad spelling, still needs some links to be fixed.

Abma: /* Importing Your 3ds */

2011-06-12T12:07:58Z

Importing Your 3ds

← Older revision		Revision as of 13:07, 12 June 2011
Line 54:		Line 54:

	===Importing Your 3ds===		===Importing Your 3ds===
	Open ~~Upspring 1.3~~, go to file>load model and navigate to and open your 3DS model you exported, you should see the model in upspring as a 3d mesh. Go to the model tab and set the radius and height values to something other then zero... this defines where the health bar will show up, and more importantly, how big the collision sphere will be.		Open [[upspring]], go to file>load model and navigate to and open your 3DS model you exported, you should see the model in upspring as a 3d mesh. Go to the model tab and set the radius and height values to something other then zero... this defines where the health bar will show up, and more importantly, how big the collision sphere will be.

	You will also need to use all of the other tools on those tabs to resize and rotate and move your model to the right place... wings makes models that are 90 degrees off and about 30 times smaller than most spring models... make sure you click the "apply transform" button after any changes that you actually want to show up in the game.		You will also need to use all of the other tools on those tabs to resize and rotate and move your model to the right place... wings makes models that are 90 degrees off and about 30 times smaller than most spring models... make sure you click the "apply transform" button after any changes that you actually want to show up in the game.

Abma: /* Step 11:Testing Your Mod */

2010-12-05T01:09:39Z

Step 11:Testing Your Mod

← Older revision		Revision as of 02:09, 5 December 2010
Line 453:		Line 453:
	*If it doesn't work, check you didn't zip the folder itself, but the contents, ie if you open mymod.sd7 with 7zip, you should see folders such as "unittextures" rather than a folder "mymod" containing unittextures.		*If it doesn't work, check you didn't zip the folder itself, but the contents, ie if you open mymod.sd7 with 7zip, you should see folders such as "unittextures" rather than a folder "mymod" containing unittextures.

	[[Category:~~Mod~~ development]]		[[Category:Game development]]

Abma: moved Simple Mod Tutorial to Simple Game Tutorial

2010-12-05T00:59:21Z

moved Simple Mod Tutorial to Simple Game Tutorial

← Older revision	Revision as of 01:59, 5 December 2010
(No difference)

Coolfile: /* sidedata.lua */

2010-10-24T06:13:51Z

sidedata.lua

← Older revision		Revision as of 07:13, 24 October 2010
Line 361:		Line 361:

	(annotated on 2010-10-23)		(annotated on 2010-10-23)

			Moved the buildOptions definitions into the unitDef definitions, LuaParser
			Please read the change log line 77 [http://springrts.com/wiki/The_Talking_Changelog] for more information.

			(annotated on 2010-10-24)

	===moveDefs.lua===		===moveDefs.lua===

← Older revision		Revision as of 06:24, 27 July 2011
Line 21:		Line 21:

	''Want:''		''Want:''
	*[http://~~taspring.clan-sy~~.com/~~download.php~~ Spring] - The main program, you will likely need this to test if you've screwed up		*[http://springrts.com/wiki/Download Spring] - The main program, you will likely need this to test if you've screwed up
	*A Tiny Map (2x2) - to test your mod fast ~~(suggest [http://www.fileuniverse.com/?p=showitem&ID=2534 Simple Chess Map])~~		*A Tiny Map (2x2) - to test your mod fast

	''Need:''		''Need:''
	*'''Program listings can be found here:''' '''[http://~~taspring.clan-sy~~.com/wiki/Map~~%2C_Mod%2C_And_Unit_Development_Programs~~ Map, Mod, And Unit Development Programs]'''		*'''Program listings can be found here:''' '''[http://springrts.com/wiki/Map,_Mod,_And_Unit_Development_Programs Map, Mod, And Unit Development Programs]'''
	*3D Modeling Program - '''See above link'''		*3D Modeling Program - '''See above link'''
	*Notepad - to edit all the ~~miriad~~ of text files		*Notepad - to edit all the myriad of text files
	*A Graphical Editing Program - needs to handle RGBA TGAs (aka ~~tga~~'s with alpha channels), I suggest Photoshop if you have it, or The GIMP... needed for all of the texture making for UVmapping stuff... '''See above link'''		*A Graphical Editing Program - needs to handle RGBA TGAs (aka TGA's with alpha channels), I suggest Photoshop if you have it, or The GIMP... needed for all of the texture making for UVmapping stuff... '''See above link'''
	*Upspring 1.3 - To convert your models to the ~~approprite~~ s3o format (if you want to fight with 3do builder, then go ahead... a good trick is to get your model into ~~upspring~~ first and adjust all the ~~hierachy~~, then save it as an 3do... but why bother?). '''See above link'''		*Upspring 1.3 - To convert your models to the appropriate s3o format (if you want to fight with 3do builder, then go ahead... a good trick is to get your model into Upspring first and adjust all the hierarchy, then save it as an 3do... but why bother?). '''See above link'''
	*Scriptor - to make and compile your units "animation script"... or steal someone else's and make it work for your unit. '''See above link'''		*Scriptor - to make and compile your units "animation script"... or steal someone else's and make it work for your unit. '''See above link'''
	*Compression Utility - (I suggest [http://www.7-zip.org/ 7zip] - even if you are using zip compression and not 7zip, it's still good to have)		*Compression Utility - (I suggest [http://www.7-zip.org/ 7zip] - even if you are using zip compression and not 7zip, it's still good to have)
Line 35:		Line 35:
	==Step 3:Making a 3D Model==		==Step 3:Making a 3D Model==

	Go into your 3D ~~modelling~~ program and make a 3D model, [http://taspring.clan-sy.com/w/images/b/b4/WingsCombine.PNG combine] all the objects and UV map the model, then separate it out into any parts that need to move independently of each other. Then Export the UV map as an Image File and Export the whole thing as a 3ds file. Put the original wings file, the UVMap image and the 3ds file into your working directory so you can find them later.		Go into your 3D modeling program and make a 3D model, [http://taspring.clan-sy.com/w/images/b/b4/WingsCombine.PNG combine] all the objects and UV map the model, then separate it out into any parts that need to move independently of each other. Then Export the UV map as an Image File and Export the whole thing as a 3ds file. Put the original wings file, the UVMap image and the 3ds file into your working directory so you can find them later.

	Wings 3D UV Mapping tutorial has been started here - [[Units:CreateModel]]		Wings 3D UV Mapping tutorial has been started here - [[Units:CreateModel]]
Line 43:		Line 43:
	[[Basic s3o unit making guide\|This Article includes a UVMapping Guide]]		[[Basic s3o unit making guide\|This Article includes a UVMapping Guide]]

	Open up your UVMap in Photoshop (or whatever) go to the layer/chooser ~~thingy~~ and go to the Channels Tab, add a new layer (it should default to alpha) and fill it with 99% black so you can see your texture in upspring. If you want to can paint the UVmap and put white (1% black) on the alpha channel where you want your team ~~colours~~ to show up (you can use something between 1% and 99% to get a blend of your team ~~colour~~ along with the texture... for example 50% will give you your texture with 50% of the team ~~colour~~ mixed in...)		Open up your UVMap in Photoshop (or whatever) go to the layer/chooser dialog box and go to the Channels Tab, add a new layer (it should default to alpha) and fill it with 99% black so you can see your texture in upspring. If you want to can paint the UVmap and put white (1% black) on the alpha channel where you want your team colors to show up (you can use something between 1% and 99% to get a blend of your team color along with the texture... for example 50% will give you your texture with 50% of the team color mixed in...)

	I don't know how to do glow maps... XXreminder for someone to create a Glowmapping tutorial... you don't ~~acctually~~ need one for the model to show up.		I don't know how to do glow maps... XXreminder for someone to create a Glowmapping tutorial... you don't actually need one for the model to show up.

	Save these images both in the working directory.		Save these images both in the working directory.
Line 58:		Line 58:
	You will also need to use all of the other tools on those tabs to resize and rotate and move your model to the right place... wings makes models that are 90 degrees off and about 30 times smaller than most spring models... make sure you click the "apply transform" button after any changes that you actually want to show up in the game.		You will also need to use all of the other tools on those tabs to resize and rotate and move your model to the right place... wings makes models that are 90 degrees off and about 30 times smaller than most spring models... make sure you click the "apply transform" button after any changes that you actually want to show up in the game.

	Also, you will want to make the ~~hierachy~~ work using the cut, paste, and add empty buttons. You will need an object called "base" that all the other objects are connected to... the "origin object"... sometimes you get lucky and wings exports it properly... usually not.		Also, you will want to make the hierarchy work using the cut, paste, and add empty buttons. You will need an object called "base" that all the other objects are connected to... the "origin object"... sometimes you get lucky and wings exports it properly... usually not.

	===Importing Your UV and Glowmaps===		===Importing Your UV and Glowmaps===

	Go to the textures tab and make your UV/texture/team-~~colour~~ map as "texture1" and your UV/glow/reflectivity map as "texture2"... it should show up correctly in the preview pane.		Go to the textures tab and make your UV/texture/team-color map as "texture1" and your UV/glow/reflectivity map as "texture2"... it should show up correctly in the preview pane.

	===Exporting Your s3o===		===Exporting Your s3o===
Line 246:		Line 246:
	===modinfo.lua===		===modinfo.lua===

	modinfo.lua is a lua file that defines a number of things that are used when loading a mod, most of the information is self ~~explanitory~~ but basically what you are doing is defining what is going to show up in whatever mod-selection interface you use as well as what other files need to be loaded into memory in order for your mod to work.		modinfo.lua is a lua file that defines a number of things that are used when loading a mod, most of the information is self explanatory but basically what you are doing is defining what is going to show up in whatever mod-selection interface you use as well as what other files need to be loaded into memory in order for your mod to work.

	====Making a New Mod with your unit/units====		====Making a New Mod with your unit/units====
Line 269:		Line 269:
	-- for single units for example.		-- for single units for example.
	-- others - perhaps mutators and addon races that can be		-- others - perhaps mutators and addon races that can be
	-- enabled in addition to ~~xta~~ for example?		-- enabled in addition to XTA for example?
	modtype = "1",		modtype = "1",
	-- Number of other archives this one depends on		-- Number of other archives this one depends on