Talk:BASE.DAT - Revision history

7Saturn at 16:37, 20 March 2026

2026-03-20T16:37:28Z

← Older revision		Revision as of 16:37, 20 March 2026
Line 33:		Line 33:

	:It's surprising how such old code (XCOM) can raise so many questions and interesting ideas. -[[User:MikeTheRed\|MikeTheRed]] 21:39, 16 May 2008 (PDT)		:It's surprising how such old code (XCOM) can raise so many questions and interesting ideas. -[[User:MikeTheRed\|MikeTheRed]] 21:39, 16 May 2008 (PDT)

			== Faulty Claim About Base Flag Active ==
			I'm fairly certain that the statement about the last four bytes of a base is false for UFO. The flags do nothing in terms of base visibility. You can try it yourself. It does not matter what numbers are written there.

			However, the base's name itself holds the key of it being active or not. Apparently in both cases, razing a base yourself or losing it to an alien attack, the game does nothing with the last four bytes. But the base's name gets a net-length of 0. The first byte is made a zero-byte, making it a string of the length of 0 characters. Apparently that is what controls the presence of a base there. If the base record starts with a 0 byte, it's a goner.

			My guess: Someone falsely extrapolated from TFTD to UFO.

			- [[User:7Saturn\|7Saturn]]

MikeTheRed: /* Unidentified Values */ Reply to Arrow

2008-05-17T04:39:00Z

Unidentified Values: Reply to Arrow

← Older revision		Revision as of 04:39, 17 May 2008
Line 29:		Line 29:

	Actually, I was referring to the part about the 6 'unused values', including the 'gatling laser'. Should've been more clear. [[User:Arrow Quivershaft\|Arrow Quivershaft]] 21:23, 16 May 2008 (PDT)		Actually, I was referring to the part about the 6 'unused values', including the 'gatling laser'. Should've been more clear. [[User:Arrow Quivershaft\|Arrow Quivershaft]] 21:23, 16 May 2008 (PDT)

			:I did see that, Arrow; apologies that I didn't address your idea directly... NKF probably wrote the stuff about the Gatling, since he loves to find toys hidden in the code. (The hidden melee weapon stuff is a cool example.) But I'm just taking it one step at a time since, for one thing, it's not clear which of the unknown objects might be the gatling. I'm curious whether there's one single master list in the .exe or not. And then will wonder about the implications of whatever is the answer.

			:It's surprising how such old code (XCOM) can raise so many questions and interesting ideas. -[[User:MikeTheRed\|MikeTheRed]] 21:39, 16 May 2008 (PDT)

Arrow Quivershaft: Clarification

2008-05-17T04:23:59Z

Clarification

← Older revision		Revision as of 04:23, 17 May 2008
Line 27:		Line 27:
	:**BASE then skips 4 records and lists various items, as shown at record 80+ in [[BASE.DAT]], but [[OBDATA.DAT]] just continues on with various corpses (Hovertank, Tank, Civilians). Many of these BASE items can be "seen" in the battlescape, but none are actually objects that can be picked up on the battlescape - that's OBDATA's job. BASE's job is to list things that can be stored at a base.		:**BASE then skips 4 records and lists various items, as shown at record 80+ in [[BASE.DAT]], but [[OBDATA.DAT]] just continues on with various corpses (Hovertank, Tank, Civilians). Many of these BASE items can be "seen" in the battlescape, but none are actually objects that can be picked up on the battlescape - that's OBDATA's job. BASE's job is to list things that can be stored at a base.
	:Looked at one way, it all makes sense. But is XCOM truly using one source list in the executable, or did the programmers make two lists which look very similar, because there wasn't any reason not to cut and paste the two highly overlapping lists? I think it's the latter. They even use different internal numbers. Hmm. -[[User:MikeTheRed\|MikeTheRed]] 20:55, 16 May 2008 (PDT)		:Looked at one way, it all makes sense. But is XCOM truly using one source list in the executable, or did the programmers make two lists which look very similar, because there wasn't any reason not to cut and paste the two highly overlapping lists? I think it's the latter. They even use different internal numbers. Hmm. -[[User:MikeTheRed\|MikeTheRed]] 20:55, 16 May 2008 (PDT)

			Actually, I was referring to the part about the 6 'unused values', including the 'gatling laser'. Should've been more clear. [[User:Arrow Quivershaft\|Arrow Quivershaft]] 21:23, 16 May 2008 (PDT)

MikeTheRed: /* Unidentified Values */

2008-05-17T03:55:37Z

Unidentified Values

← Older revision		Revision as of 03:55, 17 May 2008
Line 18:		Line 18:

	You're right, base.dat's item listing is only the quantities. Values, language file string index reference, weights, etc. are in the executable. -[[User:NKF\|NKF]] 20:35, 16 May 2008 (PDT)		You're right, base.dat's item listing is only the quantities. Values, language file string index reference, weights, etc. are in the executable. -[[User:NKF\|NKF]] 20:35, 16 May 2008 (PDT)

			:Right, ok, here are further differences between the [[BASE.DAT]] and [[OBDATA.DAT]] item listings:
			:*OBDATA (record 0) starts at record 15 (the Pistol) in BASE; this makes sense inasmuch as all the BASE items less than its record 15 would not be found on a battlescape
			:*It looks like OBDATA fills in the gaps for the BASE items which are "unknown"
			:*At record 73 of BASE (Reaper Corpse) / record 57 of OBDATA (reaper corpse 1), differences become very evident:
			:**BASE uses one record for each type of corpse, but OBDATA uses four (for the four battlescape quadrants of the corpse)
			:**BASE lists Reaper, Sectopod, and Cyberdisc (one record each), but OBDATA lists Reaper, ''Cyberdisc'', Sectopod (4 records each)
			:**BASE then skips 4 records and lists various items, as shown at record 80+ in [[BASE.DAT]], but [[OBDATA.DAT]] just continues on with various corpses (Hovertank, Tank, Civilians). Many of these BASE items can be "seen" in the battlescape, but none are actually objects that can be picked up on the battlescape - that's OBDATA's job. BASE's job is to list things that can be stored at a base.
			:Looked at one way, it all makes sense. But is XCOM truly using one source list in the executable, or did the programmers make two lists which look very similar, because there wasn't any reason not to cut and paste the two highly overlapping lists? I think it's the latter. They even use different internal numbers. Hmm. -[[User:MikeTheRed\|MikeTheRed]] 20:55, 16 May 2008 (PDT)

NKF: /* Unidentified Values */

2008-05-17T03:35:47Z

Unidentified Values

← Older revision		Revision as of 03:35, 17 May 2008
Line 16:		Line 16:

	:Thanks Arrow, I guess Uncarryable Items gives suggestions, but I still don't entirely understand that Item listing. All I did was reformat what was already on the page, so I could relate it to the PRODUCT.DAT info I'd just looked at - and the gaps became clear when I did the offset math. One thing that puzzles me is that BASE.DAT obviously isn't the "ultimate source" of this list, since it's only showing quantities at a base. There must be some other "real" source which includes names, properties, etc. I've looked around the wiki but can't seem to find it. Maybe it's hard-coded into the .EXE and only gets tossed out in this "one step removed" kind of format, for BASE.DAT and PRODUCT.DAT? shrug -[[User:MikeTheRed\|MikeTheRed]] 20:08, 16 May 2008 (PDT)		:Thanks Arrow, I guess Uncarryable Items gives suggestions, but I still don't entirely understand that Item listing. All I did was reformat what was already on the page, so I could relate it to the PRODUCT.DAT info I'd just looked at - and the gaps became clear when I did the offset math. One thing that puzzles me is that BASE.DAT obviously isn't the "ultimate source" of this list, since it's only showing quantities at a base. There must be some other "real" source which includes names, properties, etc. I've looked around the wiki but can't seem to find it. Maybe it's hard-coded into the .EXE and only gets tossed out in this "one step removed" kind of format, for BASE.DAT and PRODUCT.DAT? shrug -[[User:MikeTheRed\|MikeTheRed]] 20:08, 16 May 2008 (PDT)

			You're right, base.dat's item listing is only the quantities. Values, language file string index reference, weights, etc. are in the executable. -[[User:NKF\|NKF]] 20:35, 16 May 2008 (PDT)

MikeTheRed: /* Unidentified Values */

2008-05-17T03:08:48Z

Unidentified Values

← Older revision		Revision as of 03:08, 17 May 2008
Line 14:		Line 14:

	[[Item_Weight#Uncarryable_items\|This]] of any help, MTR? [[User:Arrow Quivershaft\|Arrow Quivershaft]] 19:51, 15 May 2008 (PDT)		[[Item_Weight#Uncarryable_items\|This]] of any help, MTR? [[User:Arrow Quivershaft\|Arrow Quivershaft]] 19:51, 15 May 2008 (PDT)

			:Thanks Arrow, I guess Uncarryable Items gives suggestions, but I still don't entirely understand that Item listing. All I did was reformat what was already on the page, so I could relate it to the PRODUCT.DAT info I'd just looked at - and the gaps became clear when I did the offset math. One thing that puzzles me is that BASE.DAT obviously isn't the "ultimate source" of this list, since it's only showing quantities at a base. There must be some other "real" source which includes names, properties, etc. I've looked around the wiki but can't seem to find it. Maybe it's hard-coded into the .EXE and only gets tossed out in this "one step removed" kind of format, for BASE.DAT and PRODUCT.DAT? shrug -[[User:MikeTheRed\|MikeTheRed]] 20:08, 16 May 2008 (PDT)

Arrow Quivershaft: Unidentified values

2008-05-16T02:51:50Z

Unidentified values

← Older revision		Revision as of 02:51, 16 May 2008
Line 9:		Line 9:

	It should be noted that despite all values being unsigned little debian and thus having a fairly large range, there is a cap of 9999 instances/units of a given item at a given base. [[User:Arrow Quivershaft\|Arrow Quivershaft]] 17:28, 5 April 2008 (PDT)		It should be noted that despite all values being unsigned little debian and thus having a fairly large range, there is a cap of 9999 instances/units of a given item at a given base. [[User:Arrow Quivershaft\|Arrow Quivershaft]] 17:28, 5 April 2008 (PDT)


			==Unidentified Values==

			[[Item_Weight#Uncarryable_items\|This]] of any help, MTR? [[User:Arrow Quivershaft\|Arrow Quivershaft]] 19:51, 15 May 2008 (PDT)

Arrow Quivershaft: An item cap of 9,999 units of a given item exists and should be noted.

2008-04-06T00:28:15Z

An item cap of 9,999 units of a given item exists and should be noted.

← Older revision		Revision as of 00:28, 6 April 2008
Line 4:		Line 4:

	- [[User:NKF\|NKF]]		- [[User:NKF\|NKF]]


			==Little Endian==

			It should be noted that despite all values being unsigned little debian and thus having a fairly large range, there is a cap of 9999 instances/units of a given item at a given base. [[User:Arrow Quivershaft\|Arrow Quivershaft]] 17:28, 5 April 2008 (PDT)

NKF: /* fixed wikilink */

2007-01-29T08:04:54Z

fixed wikilink

← Older revision		Revision as of 08:04, 29 January 2007
Line 1:		Line 1:
	The holes in the item list are the 6 unused items in obdata.dat. Starting from the standard pistol, the object table in the base and craft files match the entries in [[~~obdata~~.~~dat~~]].		The holes in the item list are the 6 unused items in obdata.dat. Starting from the standard pistol, the object table in the base and craft files match the entries in [[OBDATA.DAT]].

	The six unused items don't have any text labels associated with them apart from the description in obdata.dat. If you inspect obdata.dat, you'll notice that they are a few weapons and ammo clips, however one or two of their crucial switches have been turned off so that they do not function. TFTD uses these slots for the gauss clips and drills.		The six unused items don't have any text labels associated with them apart from the description in obdata.dat. If you inspect obdata.dat, you'll notice that they are a few weapons and ammo clips, however one or two of their crucial switches have been turned off so that they do not function. TFTD uses these slots for the gauss clips and drills.

	- [[User:NKF\|NKF]]		- [[User:NKF\|NKF]]

NKF: /* object table holes */

2007-01-29T08:04:16Z

object table holes

New page

The holes in the item list are the 6 unused items in obdata.dat. Starting from the standard pistol, the object table in the base and craft files match the entries in [[obdata.dat]].

The six unused items don't have any text labels associated with them apart from the description in obdata.dat. If you inspect obdata.dat, you'll notice that they are a few weapons and ammo clips, however one or two of their crucial switches have been turned off so that they do not function. TFTD uses these slots for the gauss clips and drills.

- [[User:NKF|NKF]]