Development:Npcs.xml - Revision history

Move page script: Move page script moved page Dev:Npcs.xml to Development:Npcs.xml: Rename Dev: to Development: so the miraheze import works

2024-03-27T03:56:46Z

Move page script moved page Dev:Npcs.xml to Development:Npcs.xml: Rename Dev: to Development: so the miraheze import works

← Older revision	Revision as of 03:56, 27 March 2024
(No difference)

Cassy: removing category

2015-03-11T08:26:38Z

removing category

← Older revision		Revision as of 08:26, 11 March 2015
Line 27:		Line 27:

	{{Template:Content XML}}		{{Template:Content XML}}
	~~[[Category:Reference]]~~

Jaxad0127: Jaxad0127 moved page Npcs.xml to Dev:Npcs.xml without leaving a redirect

2013-07-01T20:52:24Z

Jaxad0127 moved page Npcs.xml to Dev:Npcs.xml without leaving a redirect

← Older revision	Revision as of 20:52, 1 July 2013
(No difference)

Hoogli at 04:42, 22 November 2010

2010-11-22T04:42:33Z

← Older revision		Revision as of 04:42, 22 November 2010
Line 27:		Line 27:

	{{Template:Content XML}}		{{Template:Content XML}}
			[[Category:Reference]]

Kess: Typos

2009-02-16T18:20:49Z

Typos

← Older revision		Revision as of 18:20, 16 February 2009
Line 8:		Line 8:

	===<npc>===		===<npc>===
	~~And~~ individual NPC description. <code>npc</code>s have <code>id</code>, which are the view ID sent by the server. Note that client versions prior to 0.0.28 can only use NPCs ~~int he~~ range 100-199. 0.0.28 and above can use NPCs in the range 50-1001. TMWServ client can use any ID? <code>npc</code> elements contain sprite and particle tags to describe how the NPC should look.		An individual NPC description. <code>npc</code>s have <code>id</code>, which are the view ID sent by the server. Note that client versions prior to 0.0.28 can only use NPCs in the range 100-199. Version 0.0.28 and above can use NPCs in the range 50-1001. TMWServ client can use any ID? <code>npc</code> elements contain sprite and particle tags to describe how the NPC should look.

	===<sprite*gt;===		===<sprite>===
	A sprite to use when displaying the NPC. Multiple sprites are layered in the order they are put. <code>sprite</code>s have <code>variant</code>s and content. <code>variant</code> says which sprite variant to use from the given file. The tag's contents describe the sprite definition to use.		A sprite to use when displaying the NPC. Multiple sprites are layered in the order they are put. <code>sprite</code>s have <code>variant</code>s and content. <code>variant</code> says which sprite variant to use from the given file. The tag's contents describe the sprite definition to use.

	===<particlefx*gt;===		===<particlefx>===
	A particle effect to use when displaying the NPC. <code>particlefx</code> tags only have content, which describes the particle definition to use.		A particle effect to use when displaying the NPC. <code>particlefx</code> tags only have content, which describes the particle definition to use.

Crush2: added template

2009-02-16T16:55:47Z

added template

← Older revision		Revision as of 16:55, 16 February 2009
Line 25:		Line 25:
	</npcs>		</npcs>
	</code>		</code>

			{{Template:Content XML}}

Jaxad0127: initial revision

2009-02-16T15:18:15Z

initial revision

New page

This file describes the NPC IDs recognized by the client. Note that only client versions 0.0.25 and above use this file.

==Structure==
NPC DBs are in XML format.

===<npcs>===
This is the root element of the file.

===<npc>===
And individual NPC description. <code>npc</code>s have <code>id</code>, which are the view ID sent by the server. Note that client versions prior to 0.0.28 can only use NPCs int he range 100-199. 0.0.28 and above can use NPCs in the range 50-1001. TMWServ client can use any ID? <code>npc</code> elements contain sprite and particle tags to describe how the NPC should look.

===<sprite*gt;===
A sprite to use when displaying the NPC. Multiple sprites are layered in the order they are put. <code>sprite</code>s have <code>variant</code>s and content. <code>variant</code> says which sprite variant to use from the given file. The tag's contents describe the sprite definition to use.

===<particlefx*gt;===
A particle effect to use when displaying the NPC. <code>particlefx</code> tags only have content, which describes the particle definition to use.

==Example==

<code>
<npcs>
<npc id="100"><sprite variant="0">npc.xml</sprite></npc>
<npc id="101"><sprite variant="1">npc.xml</sprite><particlefx>graphics/particles/some_particle.xml</particlefx></npc>
...
</npcs>
</code>