Category:File formats - Revision history

Retro00064: /* Copy Protection */ added Category:Content configuration.

2011-09-05T02:13:49Z

Copy Protection: added Category:Content configuration.

← Older revision		Revision as of 02:13, 5 September 2011
Line 14:		Line 14:
	== Copy Protection ==		== Copy Protection ==
	The use of an N3V binary file format should not be considered as a strong protection mechanism against snooping or modification except where specifically stated otherwise by N3V. Custom binary file formats are used to allow high-performance access to data from within the game environment. Security and obfuscation are neither primary not secondary goals for these formats, and N3V may provide mechanisms which convert from the binary formats back into "common" formats without prior notice. It should be noted that the technical capability of reverse-engineering the contents of a file does not equate to the legal right to modify or distribute said file. Before modifying someone else's content, please seek the permission of the creator. If you are in any doubt as to your rights in this area, please seek advice from a legal professional.		The use of an N3V binary file format should not be considered as a strong protection mechanism against snooping or modification except where specifically stated otherwise by N3V. Custom binary file formats are used to allow high-performance access to data from within the game environment. Security and obfuscation are neither primary not secondary goals for these formats, and N3V may provide mechanisms which convert from the binary formats back into "common" formats without prior notice. It should be noted that the technical capability of reverse-engineering the contents of a file does not equate to the legal right to modify or distribute said file. Before modifying someone else's content, please seek the permission of the creator. If you are in any doubt as to your rights in this area, please seek advice from a legal professional.

			[[Category:Content configuration]]

Windwalkr at 07:39, 4 May 2011

2011-05-04T07:39:33Z

← Older revision		Revision as of 07:39, 4 May 2011
Line 3:		Line 3:
	When creating files for use with Trainz, care should be taken to follow the specified format accurately. Even if a particular deviation from the documented format is permitted by the current game and tools, it may become disallowed in future versions as loaders are updated and validation techniques are improved.		When creating files for use with Trainz, care should be taken to follow the specified format accurately. Even if a particular deviation from the documented format is permitted by the current game and tools, it may become disallowed in future versions as loaders are updated and validation techniques are improved.


			== Reading N3V File Formats ==
	If you develop software which reads these file formats, you should accept and ignore minor deviations where feasible, in order to future-proof your software. Base your file reader on the documented format, not the particulars of the current Trainz implementation. It is likely that implementation-specific details will change between Trainz versions, whereas the file formats are typically extended but not often replaced.		If you develop software which reads these file formats, you should accept and ignore minor deviations where feasible, in order to future-proof your software. Base your file reader on the documented format, not the particulars of the current Trainz implementation. It is likely that implementation-specific details will change between Trainz versions, whereas the file formats are typically extended but not often replaced.


			== Writing Binary Files ==
			There exist a number of binary file formats which are produced by N3V or by N3V-provided utilities and which are not formally documented. We strongly recommend that third-party developers do not write directly ''to'' these formats. N3V does not support any such tools or any files created by these tools. Reading ''from'' these undocumented binary formats is considered harmless but unsupported.


			== Copy Protection ==
			The use of an N3V binary file format should not be considered as a strong protection mechanism against snooping or modification except where specifically stated otherwise by N3V. Custom binary file formats are used to allow high-performance access to data from within the game environment. Security and obfuscation are neither primary not secondary goals for these formats, and N3V may provide mechanisms which convert from the binary formats back into "common" formats without prior notice. It should be noted that the technical capability of reverse-engineering the contents of a file does not equate to the legal right to modify or distribute said file. Before modifying someone else's content, please seek the permission of the creator. If you are in any doubt as to your rights in this area, please seek advice from a legal professional.

Windwalkr: New page: The follow articles describe the format of various user-editable files used within the Trainz environment. When creating files for use with Trainz, care should be taken to follow the spec...

2010-02-03T14:35:14Z

New page: The follow articles describe the format of various user-editable files used within the Trainz environment. When creating files for use with Trainz, care should be taken to follow the spec...

New page

The follow articles describe the format of various user-editable files used within the Trainz environment.

When creating files for use with Trainz, care should be taken to follow the specified format accurately. Even if a particular deviation from the documented format is permitted by the current game and tools, it may become disallowed in future versions as loaders are updated and validation techniques are improved.

If you develop software which reads these file formats, you should accept and ignore minor deviations where feasible, in order to future-proof your software. Base your file reader on the documented format, not the particulars of the current Trainz implementation. It is likely that implementation-specific details will change between Trainz versions, whereas the file formats are typically extended but not often replaced.