Invisible characters in ship names - Revision history

Yarn: fixed the non-ASCII characters

2015-11-09T06:14:22Z

fixed the non-ASCII characters

← Older revision		Revision as of 06:14, 9 November 2015
Line 1:		Line 1:
	One of the handy features of FS2 is that its internal font does not support a lot of the high-ASCII characters, and just has a blank space instead of the actual symbol. This means that characters like Ã¹, Ã¸, or Â¤ will appear as blank spaces inside of FS2 (but not [[Portal:FRED\|FRED]]). This fact can be exploited to much benefit.		One of the handy features of FS2 is that its internal font does not support a lot of the high-ASCII characters, and just has a blank space instead of the actual symbol. This means that characters like ù, ø, or ¤ will appear as blank spaces inside of FS2 (but not [[Portal:FRED\|FRED]]). This fact can be exploited to much benefit.

	For example, say I want a ship to jump out and then jump back in later in the mission. Technically this is impossible, since a ship can only be created once in a mission (i.e. once the [[GTD Aquitaine\|''Aquitaine'']] has been created, if she leaves or is destroyed, she cannot be created again). However, it is possible to have the ''Aquitaine'' jump out of the mission, and then later have the ~~AquitaineÂ¤~~ jump in. In reality, the names are different, but to the player they will look identical.		For example, say I want a ship to jump out and then jump back in later in the mission. Technically this is impossible, since a ship can only be created once in a mission (i.e. once the [[GTD Aquitaine\|''Aquitaine'']] has been created, if she leaves or is destroyed, she cannot be created again). However, it is possible to have the ''Aquitaine'' jump out of the mission, and then later have the Aquitaine¤ jump in. In reality, the names are different, but to the player they will look identical.

	Another example is the use of "counter ships". Say I want to give the player a directive to scan 7 of 10 cargo containers. There is no percent-ships-scanned [[SEXP]], so if I simply use the is-cargo-known-delay SEXP, I will need to make a very complicated event covering every possible combination that would give me 70% scanned containers and 30% unscanned. But if I use counter ships, my life becomes much much easier:		Another example is the use of "counter ships". Say I want to give the player a directive to scan 7 of 10 cargo containers. There is no percent-ships-scanned [[SEXP]], so if I simply use the is-cargo-known-delay SEXP, I will need to make a very complicated event covering every possible combination that would give me 70% scanned containers and 30% unscanned. But if I use counter ships, my life becomes much much easier:

	First, I place 10 hostile stealth fighters far away from the field of battle, and name them things like Â¤, Ã¿, Ã¾, Ãº, Ã¸, and so on. Next, I set the departure cue of each one so that it leaves when one of the cargo containers is scanned (i.e. when Cargo 1 is scanned, Â¤ departs, when Cargo 2 is scanned, Ã¿ departs). Now in the directive I can use the nice and easy percent-ship-departed SEXP with all your counter ships listed underneath it as the condition for the SEXP returning true. Meanwhile, because I used high-ASCII characters for names, the ships won't even appear on the player's ship list when he presses F3—as far as he knows, they don't even exist. Remember to check "No Arrival Music" or you'll have constant battle music playing, even in quiet parts of your mission.		First, I place 10 hostile stealth fighters far away from the field of battle, and name them things like ¤, ÿ, þ, ú, ø, and so on. Next, I set the departure cue of each one so that it leaves when one of the cargo containers is scanned (i.e. when Cargo 1 is scanned, ¤ departs, when Cargo 2 is scanned, ÿ departs). Now in the directive I can use the nice and easy percent-ship-departed SEXP with all your counter ships listed underneath it as the condition for the SEXP returning true. Meanwhile, because I used high-ASCII characters for names, the ships won't even appear on the player's ship list when he presses F3—as far as he knows, they don't even exist. Remember to check "No Arrival Music" or you'll have constant battle music playing, even in quiet parts of your mission.
	{{Table3610\|As of 2008.04.06, you can use the # symbol for this purpose. This has multiple advantages—everything after the # is invisible, so you can use more descriptive names, like #cargo1, #cargo2, #cargo3 etc, or Aquitaine#round2 for example. More importantly, if these high-ASCII characters ARE ever implemented in FS2 (which may happen someday to allow Unicode and better support the international fans), the previous method would become visible, whereas the # can now be considered the "proper" way to do it. After all, [[ships.tbl]] and [[weapons.tbl]] entries already behave like this. }}		{{Table3610\|As of 2008.04.06, you can use the # symbol for this purpose. This has multiple advantages—everything after the # is invisible, so you can use more descriptive names, like #cargo1, #cargo2, #cargo3 etc, or Aquitaine#round2 for example. More importantly, if these high-ASCII characters ARE ever implemented in FS2 (which may happen someday to allow Unicode and better support the international fans), the previous method would become visible, whereas the # can now be considered the "proper" way to do it. After all, [[ships.tbl]] and [[weapons.tbl]] entries already behave like this. }}

	[[Category:FRED Tips]]		[[Category:FRED Tips]]

Wanderer: changed template to table3610

2009-06-14T14:46:13Z

changed template to table3610

← Older revision		Revision as of 14:46, 14 June 2009
Line 6:		Line 6:

	First, I place 10 hostile stealth fighters far away from the field of battle, and name them things like Â¤, Ã¿, Ã¾, Ãº, Ã¸, and so on. Next, I set the departure cue of each one so that it leaves when one of the cargo containers is scanned (i.e. when Cargo 1 is scanned, Â¤ departs, when Cargo 2 is scanned, Ã¿ departs). Now in the directive I can use the nice and easy percent-ship-departed SEXP with all your counter ships listed underneath it as the condition for the SEXP returning true. Meanwhile, because I used high-ASCII characters for names, the ships won't even appear on the player's ship list when he presses F3—as far as he knows, they don't even exist. Remember to check "No Arrival Music" or you'll have constant battle music playing, even in quiet parts of your mission.		First, I place 10 hostile stealth fighters far away from the field of battle, and name them things like Â¤, Ã¿, Ã¾, Ãº, Ã¸, and so on. Next, I set the departure cue of each one so that it leaves when one of the cargo containers is scanned (i.e. when Cargo 1 is scanned, Â¤ departs, when Cargo 2 is scanned, Ã¿ departs). Now in the directive I can use the nice and easy percent-ship-departed SEXP with all your counter ships listed underneath it as the condition for the SEXP returning true. Meanwhile, because I used high-ASCII characters for names, the ships won't even appear on the player's ship list when he presses F3—as far as he knows, they don't even exist. Remember to check "No Arrival Music" or you'll have constant battle music playing, even in quiet parts of your mission.
	{{~~Table37~~\| As of 2008.04.06, you can use the # symbol for this purpose. This has multiple advantages—everything after the # is invisible, so you can use more descriptive names, like #cargo1, #cargo2, #cargo3 etc, or Aquitaine#round2 for example. More importantly, if these high-ASCII characters ARE ever implemented in FS2 (which may happen someday to allow Unicode and better support the international fans), the previous method would become visible, whereas the # can now be considered the "proper" way to do it. After all, [[ships.tbl]] and [[weapons.tbl]] entries already behave like this. }}		{{Table3610\|As of 2008.04.06, you can use the # symbol for this purpose. This has multiple advantages—everything after the # is invisible, so you can use more descriptive names, like #cargo1, #cargo2, #cargo3 etc, or Aquitaine#round2 for example. More importantly, if these high-ASCII characters ARE ever implemented in FS2 (which may happen someday to allow Unicode and better support the international fans), the previous method would become visible, whereas the # can now be considered the "proper" way to do it. After all, [[ships.tbl]] and [[weapons.tbl]] entries already behave like this. }}

	[[Category:FRED Tips]]		[[Category:FRED Tips]]

TopAce at 14:07, 28 December 2008

2008-12-28T14:07:41Z

← Older revision		Revision as of 14:07, 28 December 2008
Line 1:		Line 1:
	~~==The wonders~~ of ~~invisible~~ characters ~~in names~~:==		One of the handy features of FS2 is that its internal font does not support a lot of the high-ASCII characters, and just has a blank space instead of the actual symbol. This means that characters like Ã¹, Ã¸, or Â¤ will appear as blank spaces inside of FS2 (but not [[Portal:FRED\|FRED]]). This fact can be exploited to much benefit.

	One of the handy features of FS2 is that its internal font does not support a lot of the high-ASCII characters, and just has a blank space instead of the actual symbol. This means that characters like Ã¹, Ã¸, or Â¤ will appear as blank spaces inside of FS2 (but not Fred). This fact can be exploited to much benefit.		For example, say I want a ship to jump out and then jump back in later in the mission. Technically this is impossible, since a ship can only be created once in a mission (i.e. once the [[GTD Aquitaine\|''Aquitaine'']] has been created, if she leaves or is destroyed, she cannot be created again). However, it is possible to have the ''Aquitaine'' jump out of the mission, and then later have the AquitaineÂ¤ jump in. In reality, the names are different, but to the player they will look identical.
	~~<br><br>~~
	For example, say I want a ship to jump out and then jump back in later in the mission. Technically this is impossible, since a ship can only be created once in a mission (i.e. once the ~~Aquitane~~ has been created, if he leaves or is destroyed he cannot be created again). However, it is possible to have the ~~Aquitane~~ jump out of the mission, and then later have the ~~AquitaneÂ¤~~ jump in. In reality, the names are different, but to the player they will look identical.		Another example is the use of "counter ships". Say I want to give the player a directive to scan 7 of 10 cargo containers. There is no percent-ships-scanned [[SEXP]], so if I simply use the is-cargo-known-delay SEXP, I will need to make a very complicated event covering every possible combination that would give me 70% scanned containers and 30% unscanned. But if I use counter ships, my life becomes much much easier:
	~~<br><br>~~
	Another example is the use of "counter ships". Say I want to give the player a directive to scan 7 of 10 cargo containers. There is no percent-ships-scanned ~~sexp~~, so if I simply use the is-cargo-known-delay ~~sexp~~, I will need to make a very complicated event covering every possible combination that would give me 70% scanned containers and 30% unscanned. But if I use counter ships, my life becomes much much easier:		First, I place 10 hostile stealth fighters far away from the field of battle, and name them things like Â¤, Ã¿, Ã¾, Ãº, Ã¸, and so on. Next, I set the departure cue of each one so that it leaves when one of the cargo containers is scanned (i.e. when Cargo 1 is scanned, Â¤ departs, when Cargo 2 is scanned, Ã¿ departs). Now in the directive I can use the nice and easy percent-ship-departed SEXP with all your counter ships listed underneath it as the condition for the SEXP returning true. Meanwhile, because I used high-ASCII characters for names, the ships won't even appear on the player's ship list when he presses F3—as far as he knows, they don't even exist. Remember to check "No Arrival Music" or you'll have constant battle music playing, even in quiet parts of your mission.
	~~<br><br>~~		{{Table37\| As of 2008.04.06, you can use the # symbol for this purpose. This has multiple advantages—everything after the # is invisible, so you can use more descriptive names, like #cargo1, #cargo2, #cargo3 etc, or Aquitaine#round2 for example. More importantly, if these high-ASCII characters ARE ever implemented in FS2 (which may happen someday to allow Unicode and better support the international fans), the previous method would become visible, whereas the # can now be considered the "proper" way to do it. After all, [[ships.tbl]] and [[weapons.tbl]] entries already behave like this. }}
	First, I place 10 hostile stealth fighters far away from the field of battle, and name them things like Â¤, Ã¿, Ã¾, Ãº, Ã¸, and so on. Next, I set the departure cue of each one so that it leaves when one of the cargo containers is scanned (i.e. when Cargo 1 is scanned, Â¤ departs, when Cargo 2 is scanned, Ã¿ departs). Now in the directive I can use the nice and easy percent-ship-departed ~~sexp~~ with all your counter ships listed underneath it as the condition for the ~~sexp~~ returning true. Meanwhile, because I used high-ASCII characters for names, the ships won't even appear on the player's ship list when he presses F3--as far as he knows, they don't even exist. Remember to check "No Arrival Music" or you'll have constant battle music playing, even in quiet parts of your mission.
	{{Table37\| As of 2008.04.06, you can use the # symbol for this purpose. This has multiple advantages -- everything after the # is invisible, so you can use more descriptive names, like #cargo1, #cargo2, #cargo3 etc, or ~~Aquitane~~#round2 for example. More importantly, if these high-ASCII characters ARE ever implemented in FS2 (which may happen someday to allow Unicode and better support the international fans), the previous method would become visible, whereas the # can now be considered the 'proper' way to do it. After all, ships.tbl and weapons.tbl entries already behave like this. }}

	[[Category:FRED Tips]]		[[Category:FRED Tips]]

TopAce: The wonders of invisible characters in names moved to Invisible characters in ship names

2008-12-28T14:03:37Z

The wonders of invisible characters in names moved to Invisible characters in ship names

← Older revision	Revision as of 14:03, 28 December 2008
(No difference)

Backslash: /* The wonders of invisible characters in names: */

2008-04-06T23:13:57Z

The wonders of invisible characters in names:

← Older revision		Revision as of 23:13, 6 April 2008
Line 8:		Line 8:
	<br><br>		<br><br>
	First, I place 10 hostile stealth fighters far away from the field of battle, and name them things like Â¤, Ã¿, Ã¾, Ãº, Ã¸, and so on. Next, I set the departure cue of each one so that it leaves when one of the cargo containers is scanned (i.e. when Cargo 1 is scanned, Â¤ departs, when Cargo 2 is scanned, Ã¿ departs). Now in the directive I can use the nice and easy percent-ship-departed sexp with all your counter ships listed underneath it as the condition for the sexp returning true. Meanwhile, because I used high-ASCII characters for names, the ships won't even appear on the player's ship list when he presses F3--as far as he knows, they don't even exist. Remember to check "No Arrival Music" or you'll have constant battle music playing, even in quiet parts of your mission.		First, I place 10 hostile stealth fighters far away from the field of battle, and name them things like Â¤, Ã¿, Ã¾, Ãº, Ã¸, and so on. Next, I set the departure cue of each one so that it leaves when one of the cargo containers is scanned (i.e. when Cargo 1 is scanned, Â¤ departs, when Cargo 2 is scanned, Ã¿ departs). Now in the directive I can use the nice and easy percent-ship-departed sexp with all your counter ships listed underneath it as the condition for the sexp returning true. Meanwhile, because I used high-ASCII characters for names, the ships won't even appear on the player's ship list when he presses F3--as far as he knows, they don't even exist. Remember to check "No Arrival Music" or you'll have constant battle music playing, even in quiet parts of your mission.
			{{Table37\| As of 2008.04.06, you can use the # symbol for this purpose. This has multiple advantages -- everything after the # is invisible, so you can use more descriptive names, like #cargo1, #cargo2, #cargo3 etc, or Aquitane#round2 for example. More importantly, if these high-ASCII characters ARE ever implemented in FS2 (which may happen someday to allow Unicode and better support the international fans), the previous method would become visible, whereas the # can now be considered the 'proper' way to do it. After all, ships.tbl and weapons.tbl entries already behave like this. }}

	[[Category:FRED Tips]]		[[Category:FRED Tips]]

Shade: removed category

2006-04-13T23:28:30Z

removed category

← Older revision		Revision as of 23:28, 13 April 2006
Line 9:		Line 9:
	First, I place 10 hostile stealth fighters far away from the field of battle, and name them things like Â¤, Ã¿, Ã¾, Ãº, Ã¸, and so on. Next, I set the departure cue of each one so that it leaves when one of the cargo containers is scanned (i.e. when Cargo 1 is scanned, Â¤ departs, when Cargo 2 is scanned, Ã¿ departs). Now in the directive I can use the nice and easy percent-ship-departed sexp with all your counter ships listed underneath it as the condition for the sexp returning true. Meanwhile, because I used high-ASCII characters for names, the ships won't even appear on the player's ship list when he presses F3--as far as he knows, they don't even exist. Remember to check "No Arrival Music" or you'll have constant battle music playing, even in quiet parts of your mission.		First, I place 10 hostile stealth fighters far away from the field of battle, and name them things like Â¤, Ã¿, Ã¾, Ãº, Ã¸, and so on. Next, I set the departure cue of each one so that it leaves when one of the cargo containers is scanned (i.e. when Cargo 1 is scanned, Â¤ departs, when Cargo 2 is scanned, Ã¿ departs). Now in the directive I can use the nice and easy percent-ship-departed sexp with all your counter ships listed underneath it as the condition for the sexp returning true. Meanwhile, because I used high-ASCII characters for names, the ships won't even appear on the player's ship list when he presses F3--as far as he knows, they don't even exist. Remember to check "No Arrival Music" or you'll have constant battle music playing, even in quiet parts of your mission.

	~~[[Category:FRED]]~~
	[[Category:FRED Tips]]		[[Category:FRED Tips]]

Shade at 18:54, 13 April 2006

2006-04-13T18:54:00Z

← Older revision		Revision as of 18:54, 13 April 2006
Line 10:		Line 10:

	[[Category:FRED]]		[[Category:FRED]]
			[[Category:FRED Tips]]

Wanderer at 17:28, 3 April 2006

2006-04-03T17:28:16Z

← Older revision		Revision as of 17:28, 3 April 2006
Line 1:		Line 1:
	==The wonders of invisible characters in names:==		==The wonders of invisible characters in names:==

	One of the handy features of FS2 is that its internal font does not support a lot of the high-ASCII characters, and just has a blank space instead of the actual symbol. This means that characters like Ã¹, Ã¸, or Â¤ will appear as blank spaces inside of FS2 (but not Fred). This fact can be exploited to much benefit. <br>		One of the handy features of FS2 is that its internal font does not support a lot of the high-ASCII characters, and just has a blank space instead of the actual symbol. This means that characters like Ã¹, Ã¸, or Â¤ will appear as blank spaces inside of FS2 (but not Fred). This fact can be exploited to much benefit.
	<br>		<br><br>
	For example, say I want a ship to jump out and then jump back in later in the mission. Technically this is impossible, since a ship can only be created once in a mission (i.e. once the Aquitane has been created, if he leaves or is destroyed he cannot be created again). However, it is possible to have the Aquitane jump out of the mission, and then later have the AquitaneÂ¤ jump in. In reality, the names are different, but to the player they will look identical.		For example, say I want a ship to jump out and then jump back in later in the mission. Technically this is impossible, since a ship can only be created once in a mission (i.e. once the Aquitane has been created, if he leaves or is destroyed he cannot be created again). However, it is possible to have the Aquitane jump out of the mission, and then later have the AquitaneÂ¤ jump in. In reality, the names are different, but to the player they will look identical.
	<br>		<br><br>
	Another example is the use of "counter ships". Say I want to give the player a directive to scan 7 of 10 cargo containers. There is no percent-ships-scanned sexp, so if I simply use the is-cargo-known-delay sexp, I will need to make a very complicated event covering every possible combination that would give me 70% scanned containers and 30% unscanned. But if I use counter ships, my life becomes much much easier:		Another example is the use of "counter ships". Say I want to give the player a directive to scan 7 of 10 cargo containers. There is no percent-ships-scanned sexp, so if I simply use the is-cargo-known-delay sexp, I will need to make a very complicated event covering every possible combination that would give me 70% scanned containers and 30% unscanned. But if I use counter ships, my life becomes much much easier:
			<br><br>
			First, I place 10 hostile stealth fighters far away from the field of battle, and name them things like Â¤, Ã¿, Ã¾, Ãº, Ã¸, and so on. Next, I set the departure cue of each one so that it leaves when one of the cargo containers is scanned (i.e. when Cargo 1 is scanned, Â¤ departs, when Cargo 2 is scanned, Ã¿ departs). Now in the directive I can use the nice and easy percent-ship-departed sexp with all your counter ships listed underneath it as the condition for the sexp returning true. Meanwhile, because I used high-ASCII characters for names, the ships won't even appear on the player's ship list when he presses F3--as far as he knows, they don't even exist. Remember to check "No Arrival Music" or you'll have constant battle music playing, even in quiet parts of your mission.

	First, I place 10 hostile stealth fighters far away from the field of battle, and name them things like Â¤, Ã¿, Ã¾, Ãº, Ã¸, and so on. Next, I set the departure cue of each one so that it leaves when one of the cargo containers is scanned (i.e. when Cargo 1 is scanned, Â¤ departs, when Cargo 2 is scanned, Ã¿ departs). Now in the directive I can use the nice and easy percent-ship-departed sexp with all your counter ships listed underneath it as the condition for the sexp returning true. Meanwhile, because I used high-ASCII characters for names, the ships won't even appear on the player's ship list when he presses F3--as far as he knows, they don't even exist. Remember to check "No Arrival Music" or you'll have constant battle music playing, even in quiet parts of your mission.		[[Category:FRED]]

81.182.81.212 at 16:45, 7 June 2005

2005-06-07T16:45:36Z

New page

==The wonders of invisible characters in names:==

One of the handy features of FS2 is that its internal font does not support a lot of the high-ASCII characters, and just has a blank space instead of the actual symbol. This means that characters like Ã¹, Ã¸, or Â¤ will appear as blank spaces inside of FS2 (but not Fred). This fact can be exploited to much benefit. <br>
<br>
For example, say I want a ship to jump out and then jump back in later in the mission. Technically this is impossible, since a ship can only be created once in a mission (i.e. once the Aquitane has been created, if he leaves or is destroyed he cannot be created again). However, it is possible to have the Aquitane jump out of the mission, and then later have the AquitaneÂ¤ jump in. In reality, the names are different, but to the player they will look identical.
<br>
Another example is the use of "counter ships". Say I want to give the player a directive to scan 7 of 10 cargo containers. There is no percent-ships-scanned sexp, so if I simply use the is-cargo-known-delay sexp, I will need to make a very complicated event covering every possible combination that would give me 70% scanned containers and 30% unscanned. But if I use counter ships, my life becomes much much easier:

First, I place 10 hostile stealth fighters far away from the field of battle, and name them things like Â¤, Ã¿, Ã¾, Ãº, Ã¸, and so on. Next, I set the departure cue of each one so that it leaves when one of the cargo containers is scanned (i.e. when Cargo 1 is scanned, Â¤ departs, when Cargo 2 is scanned, Ã¿ departs). Now in the directive I can use the nice and easy percent-ship-departed sexp with all your counter ships listed underneath it as the condition for the sexp returning true. Meanwhile, because I used high-ASCII characters for names, the ships won't even appear on the player's ship list when he presses F3--as far as he knows, they don't even exist. Remember to check "No Arrival Music" or you'll have constant battle music playing, even in quiet parts of your mission.