IS TINY - Revision history

Flame CZE at 19:07, 13 February 2026

2026-02-13T19:07:52Z

Bokujishin: /* SubT */

2026-02-10T20:35:21Z

SubT

Bokujishin at 19:49, 9 February 2026

2026-02-09T19:49:47Z

Bokujishin at 19:38, 9 February 2026

2026-02-09T19:38:37Z

Bokujishin at 15:42, 9 February 2026

2026-02-09T15:42:08Z

Flame CZE at 00:57, 2 December 2023

2023-12-02T00:57:05Z

DarkTimes: /* Keep Alive */ Edited mistake

2010-04-11T14:22:01Z

Keep Alive: Edited mistake

DarkTimes at 18:03, 22 June 2009

2009-06-22T18:03:13Z

DarkTimes at 17:53, 22 June 2009

2009-06-22T17:53:01Z

DarkTimes at 17:36, 22 June 2009

2009-06-22T17:36:21Z

New page

== Introduction ==

The IS_TINY packet is a general purpose packet comprised of 4 bytes. The packet is designed to prevent repeating a common structure which would be the same for many packets. Its defining feature is the SubT or sub-type, which can have many different meanings based on the TINY_ enumeration.

== Packet Detail ==

=== Size ===

The size of the packet, always 4 bytes.

=== Type ===

The packet type from the ISP_ enumeration, always 3.

=== ReqI ===

The ReqI must always be set to non-zero when sending a request to LFS for information, and in turn the replying packet will contain the same value set in its ReqI.

=== SubT ===

* TINY_NONE: The InSim keep alive packet (see below)
* TINY_VER: Request for an [[IS_VER]] version packet
* TINY_CLOSE: Send to close the InSim system
* TINY_PING: Ping the system to test the connection
* TINY_REPLY: Sent in reply to a TINY_PING
* TINY_VTC: Sent when the current vote is cancelled
* TINY_SCP: Request a [[IS_SCP]] camera position packet
* TINY_SST: Request for [[IS_STA]] state packet
* TINY_GTH: Request the current race time in hundreds. A [[IS_SMALL]] with a SubT of SMALL_RTP is sent
* TINY_MPE: Sent when leaving or closing a multiplayer host
* TINY_ISM: Request for a [[IS_ISM]] InSim multi packet to be sent
* TINY_REN: Sent when the race ends (go back to track selection screen)
* TINY_CLR: Send to clear all players from the race
* TINY_NCN: Request for all [[IS_NCN]] connection packets
* TINY_NPL: Request for all [[IS_NPL]] player packets
* TINY_RES: Request for all [[IS_RES]] result packets
* TINY_NLP: Request a [[IS_NLP]] node lap packet
* TINY_MCI: Request a [[IS_MCI]] multi-car info packet
* TINY_REO: Request a [[IS_REO]] race reorder packet
* TINY_RST: Request a [[IS_RST]] race start packet
* TINY_AXI: Request a [[IS_AXI]] autocross info packet
* TINY_AXC: Sent when the current autocross layout is cleared
* TINY_RIP: Request a [[IS_RIP]] replay information packet

== Keep Alive ==

In order to maintain the connection with your program LFS will send a 'keep-alive' packet every 70 seconds. This packet must be replied to in order to prevent LFS from closing the connection. The keep alive packet is basically just a IS_TINY with a SubT of TINY_CLOSE. Whenever a TINY_CLOSE is received you must respond immediately with the same packet in order to inform LFS that your program is still alive. Failure to do this will cause your program to time out.

@@ Line 1: / Line 1: @@
-== Introduction ==
+{{Infobox InSim packet
 The '''TINY''' packet is a general purpose packet comprised of 4 bytes. The packet is designed to prevent repeating a common structure which would be the same for many packets. Its defining feature is the SubT or sub-type, which can have many different meanings based on the TINY_ enumeration.
 {| class="wikitable"
@@ Line 24: / Line 35: @@
 | subtype, from TINY_ enumeration (e.g. TINY_RACE_END)
 |}
 === Size ===
@@ Line 75: / Line 84: @@
 * TINY_LCL: Request an [[IS_SMALL]] packet with SubT SMALL_LCL for the local car's lights
-== Keep Alive ==
+== Keep alive ==
 If LFS does not receive at least one packet every 70 seconds, it closes the connection with your program. The game will send a 'keep-alive' packet every 30 seconds, to which you should reply to ensure the connection is kept alive, even when no other packets are being sent or received. The keep alive packet is an IS_TINY with a SubT of TINY_NONE. Whenever a TINY_NONE is received, you should reply with the same packet in order to inform LFS that your program is still alive.
 [[Category:InSim packets]]

@@ Line 49: / Line 49: @@
 * TINY_REPLY: Sent in reply to a TINY_PING
 * TINY_VTC: Send to cancel the current vote/Sent when the current vote is cancelled
-* TINY_SCP: Request an [[IS_SCP]] camera position packet
+* TINY_SCP: Request an [[IS_CPP]] camera position packet
 * TINY_SST: Request an [[IS_STA]] state packet
 * TINY_GTM: Request the current race time in ms. An [[IS_SMALL]] with a SubT of SMALL_RTP is sent.
@@ Line 67: / Line 67: @@
 * TINY_RIP: Request an [[IS_RIP]] packet
 * TINY_NCI: Request [[IS_NCI]] packets for all connections (host only)
-* TINY_ALC: Request an [[IS_ALC]] packet
+* TINY_ALC: Request a [[InSim_enumerations#SMALL|SMALL_ALC]] packet
 * TINY_AXM: Request [[IS_AXM]] packets for the entire layout
 * TINY_SLC: Request [[IS_SLC]] packets for all connections

@@ Line 4: / Line 4: @@
 {| class="wikitable"
-|+ IS_MSL packet properties
+|+ IS_TINY packet properties
 |-
 ! Type !! Name !! Description

@@ Line 3: / Line 3: @@
 The '''TINY''' packet is a general purpose packet comprised of 4 bytes. The packet is designed to prevent repeating a common structure which would be the same for many packets. Its defining feature is the SubT or sub-type, which can have many different meanings based on the TINY_ enumeration.
-<big><pre>struct IS_TINY // General purpose 4 byte packet
+{| class="wikitable"
+|+ IS_MSL packet properties
-	byte	Size;		// 4
+|-
-	byte	Type;		// ISP_TINY
+! Type !! Name !! Description
-	byte	ReqI;		// 0 unless it is an info request or a reply to an info request
+|-
-	byte	SubT;		// subtype, from TINY_ enumeration (e.g. TINY_RACE_END)
+| byte
-};</pre></big>
+| Size
 == Packet Details ==
@@ Line 19: / Line 33: @@
 === Type ===
-The packet type from the ISP_ enumeration, always ISP_TINY.
+The packet type from the [[InSim_enumerations#ISP|ISP_]] enumeration, always ISP_TINY.
 === ReqI ===
@@ Line 27: / Line 41: @@
 === SubT ===
-The packet's sub-type, which is a value from the TINY_ enumeration.
+The packet's sub-type, which is a value from the [[InSim_enumerations#TINY|TINY_]] enumeration.
 * TINY_NONE: The InSim keep alive packet (see below)

@@ Line 1: / Line 1: @@
 == Introduction ==
-The IS_TINY packet is a general purpose packet comprised of 4 bytes. The packet is designed to prevent repeating a common structure which would be the same for many packets. Its defining feature is the SubT or sub-type, which can have many different meanings based on the TINY_ enumeration.
+The '''TINY''' packet is a general purpose packet comprised of 4 bytes. The packet is designed to prevent repeating a common structure which would be the same for many packets. Its defining feature is the SubT or sub-type, which can have many different meanings based on the TINY_ enumeration.
 <big><pre>struct IS_TINY // General purpose 4 byte packet
+{
-	byte Size;		// always 4
+	byte	Size;		// 4
-	byte Type;		// always ISP_TINY
+	byte	Type;		// ISP_TINY
-	byte ReqI;		// 0 unless it is an info request or a reply to an info request
+	byte	ReqI;		// 0 unless it is an info request or a reply to an info request
-	byte SubT;		// subtype, from TINY_ enumeration (e.g. TINY_RACE_END)
+	byte	SubT;		// subtype, from TINY_ enumeration (e.g. TINY_RACE_END)
 };</pre></big>
-== Packet Detail ==
+== Packet Details ==
 === Size ===
@@ Line 23: / Line 23: @@
 === ReqI ===
-The ReqI must always be set to non-zero when sending a request to LFS for information, and in turn the replying packet will contain the same value set in its ReqI.
+ReqI must be set to non-zero when sending a request for information to LFS, and in turn the replying packet will contain the same value set in its ReqI. For packets sent by LFS without a request, ReqI is zero.
 === SubT ===
 * TINY_NONE: The InSim keep alive packet (see below)
 * TINY_VER: Request for an [[IS_VER]] version packet
-* TINY_CLOSE: Send to close the InSim system
+* TINY_CLOSE: Send to close the InSim connection
 * TINY_PING: Ping the system to test the connection
 * TINY_REPLY: Sent in reply to a TINY_PING
-* TINY_VTC: Sent when the current vote is cancelled
+* TINY_VTC: Send to cancel the current vote/Sent when the current vote is cancelled
-* TINY_SCP: Request a [[IS_SCP]] camera position packet
+* TINY_SCP: Request an [[IS_SCP]] camera position packet
-* TINY_SST: Request for [[IS_STA]] state packet
+* TINY_SST: Request an [[IS_STA]] state packet
-* TINY_GTH: Request the current race time in hundreds. A [[IS_SMALL]] with a SubT of SMALL_RTP is sent
+* TINY_GTM: Request the current race time in ms. An [[IS_SMALL]] with a SubT of SMALL_RTP is sent.
 * TINY_MPE: Sent when leaving or closing a multiplayer host
-* TINY_ISM: Request for a [[IS_ISM]] InSim multi packet to be sent
+* TINY_ISM: Request for an [[IS_ISM]] packet to be sent
-* TINY_REN: Sent when the race ends (go back to track selection screen)
+* TINY_REN: Sent when the race ends (return to the race setup screen)
-* TINY_CLR: Send to clear all players from the race
+* TINY_CLR: Sent when all players are cleared from the race
-* TINY_NCN: Request for all [[IS_NCN]] connection packets
+* TINY_NCN: Request [[IS_NCN]] packets for all connections
-* TINY_NPL: Request for all [[IS_NPL]] player packets
+* TINY_NPL: Request [[IS_NPL]] packets for all players
-* TINY_RES: Request for all [[IS_RES]] result packets
+* TINY_RES: Request [[IS_RES]] packets for all results
-* TINY_NLP: Request a [[IS_NLP]] node lap packet
+* TINY_NLP: Request an [[IS_NLP]] packet
-* TINY_MCI: Request a [[IS_MCI]] multi-car info packet
+* TINY_MCI: Request an [[IS_MCI]] packet
-* TINY_REO: Request a [[IS_REO]] race reorder packet
+* TINY_REO: Request an [[IS_REO]] packet
-* TINY_RST: Request a [[IS_RST]] race start packet
+* TINY_RST: Request an [[IS_RST]] packet
-* TINY_AXI: Request a [[IS_AXI]] autocross info packet
+* TINY_AXI: Request an [[IS_AXI]] packet
 * TINY_AXC: Sent when the current autocross layout is cleared
-* TINY_RIP: Request a [[IS_RIP]] replay information packet
+* TINY_RIP: Request an [[IS_RIP]] packet
 == Keep Alive ==
-In order to maintain the connection with your program LFS will send a 'keep-alive' packet every 70 seconds. This packet must be replied to in order to prevent LFS from closing the connection. The keep alive packet is basically just a IS_TINY with a SubT of TINY_NONE. Whenever a TINY_NONE is received you must respond immediately with the same packet in order to inform LFS that your program is still alive. Failure to do this will cause your program to time out.
+If LFS does not receive at least one packet every 70 seconds, it closes the connection with your program. The game will send a 'keep-alive' packet every 30 seconds, to which you should reply to ensure the connection is kept alive, even when no other packets are being sent or received. The keep alive packet is an IS_TINY with a SubT of TINY_NONE. Whenever a TINY_NONE is received, you should reply with the same packet in order to inform LFS that your program is still alive.
 [[Category:InSim packets]]

←Older revision		Revision as of 00:57, 2 December 2023
Line 54:		Line 54:

	In order to maintain the connection with your program LFS will send a 'keep-alive' packet every 70 seconds. This packet must be replied to in order to prevent LFS from closing the connection. The keep alive packet is basically just a IS_TINY with a SubT of TINY_NONE. Whenever a TINY_NONE is received you must respond immediately with the same packet in order to inform LFS that your program is still alive. Failure to do this will cause your program to time out.		In order to maintain the connection with your program LFS will send a 'keep-alive' packet every 70 seconds. This packet must be replied to in order to prevent LFS from closing the connection. The keep alive packet is basically just a IS_TINY with a SubT of TINY_NONE. Whenever a TINY_NONE is received you must respond immediately with the same packet in order to inform LFS that your program is still alive. Failure to do this will cause your program to time out.
		+
		+	[[Category:InSim packets]]

←Older revision		Revision as of 14:22, 11 April 2010
Line 53:		Line 53:
	== Keep Alive ==		== Keep Alive ==

−	In order to maintain the connection with your program LFS will send a 'keep-alive' packet every 70 seconds. This packet must be replied to in order to prevent LFS from closing the connection. The keep alive packet is basically just a IS_TINY with a SubT of ~~TINY_CLOSE~~. Whenever a ~~TINY_CLOSE~~ is received you must respond immediately with the same packet in order to inform LFS that your program is still alive. Failure to do this will cause your program to time out.	+	In order to maintain the connection with your program LFS will send a 'keep-alive' packet every 70 seconds. This packet must be replied to in order to prevent LFS from closing the connection. The keep alive packet is basically just a IS_TINY with a SubT of TINY_NONE. Whenever a TINY_NONE is received you must respond immediately with the same packet in order to inform LFS that your program is still alive. Failure to do this will cause your program to time out.

←Older revision		Revision as of 17:53, 22 June 2009
Line 2:		Line 2:

	The IS_TINY packet is a general purpose packet comprised of 4 bytes. The packet is designed to prevent repeating a common structure which would be the same for many packets. Its defining feature is the SubT or sub-type, which can have many different meanings based on the TINY_ enumeration.		The IS_TINY packet is a general purpose packet comprised of 4 bytes. The packet is designed to prevent repeating a common structure which would be the same for many packets. Its defining feature is the SubT or sub-type, which can have many different meanings based on the TINY_ enumeration.
		+
		+	<big><pre>struct IS_TINY // General purpose 4 byte packet
		+	{
		+	byte Size; // always 4
		+	byte Type; // always ISP_TINY
		+	byte ReqI; // 0 unless it is an info request or a reply to an info request
		+	byte SubT; // subtype, from TINY_ enumeration (e.g. TINY_RACE_END)
		+	};</pre></big>

	== Packet Detail ==		== Packet Detail ==