Module:Engineers - Revision history

Sythan: sell_combined: support an explicit conjunction override (and/or) for two-item any-combination cases

2026-08-20T23:55:11Z

sell_combined: support an explicit conjunction override (and/or) for two-item any-combination cases

← Older revision		Revision as of 23:55, 20 August 2026
Line 925:		Line 925:
	----------------------------------------------------------------------		----------------------------------------------------------------------
	-- sell_combined -- one combined total across several distinct items,		-- sell_combined -- one combined total across several distinct items,
	-- every item individually linked.		-- every item individually linked. Defaults to "and" (three or more
			-- items reads naturally as a plain list); an explicit
			-- unlock.conjunction overrides this, e.g. "and/or" for a two-item
			-- "any combination counts" case, matching wording already used
			-- elsewhere on this wiki for the equivalent missions case.
	----------------------------------------------------------------------		----------------------------------------------------------------------

Line 934:		Line 938:

	local items =		local items =
	joinLinkedListWithConjunction(unlock.items, 'and')		joinLinkedListWithConjunction(unlock.items, unlock.conjunction or 'and')

	if not isNonEmpty(items) then		if not isNonEmpty(items) then

Sythan: Extend Module:Engineers for structured Odyssey Engineer data (typed unlock, referrals[], discovery{}, modifications{suit,weapon}); ship-facing behavior unchanged

2026-08-20T23:52:31Z

Extend Module:Engineers for structured Odyssey Engineer data (typed unlock, referrals[], discovery{}, modifications{suit,weapon}); ship-facing behavior unchanged

Show changes

Sythan: Add Odyssey Engineer support: formatUnlockLike shared helper, formatReferralTask, prerequisite_engineers (convergent referral), formatModifications, isOdysseyEngineer, p.odysseyDirectory; scope p.comparison() to ship Engineers only. All generalizations are no-ops for existing ship records — see Elite Dangerous Field Manual:Adding Structured Data.

2026-08-20T22:07:59Z

Add Odyssey Engineer support: formatUnlockLike shared helper, formatReferralTask, prerequisite_engineers (convergent referral), formatModifications, isOdysseyEngineer, p.odysseyDirectory; scope p.comparison() to ship Engineers only. All generalizations are no-ops for existing ship records — see Elite Dangerous Field Manual:Adding Structured Data.

Show changes

Sythan: Add linkifyText() helper: selective, declared-only prose linkification for meeting_requirement/invitation_requirement/access_note via new meeting_links/invitation_links/access_note_links JSON fields

2026-08-20T02:38:26Z

Add linkifyText() helper: selective, declared-only prose linkification for meeting_requirement/invitation_requirement/access_note via new meeting_links/invitation_links/access_note_links JSON fields

Show changes

Sythan at 00:44, 20 August 2026

2026-08-20T00:44:44Z

Show changes

Sythan at 20:26, 19 August 2026

2026-08-19T20:26:44Z

Show changes

EDFM Site Maintenance: Repair content model (previous save incorrectly wrote this as wikitext) + add p.count()

2026-08-18T13:02:20Z

Repair content model (previous save incorrectly wrote this as wikitext) + add p.count()

← Older revision	Revision as of 13:02, 18 August 2026
(No difference)

EDFM Site Maintenance: Add p.count() so the canonical-record count on List of Engineers is derived, not hardcoded

2026-08-18T13:01:14Z

Add p.count() so the canonical-record count on List of Engineers is derived, not hardcoded

← Older revision		Revision as of 13:01, 18 August 2026
Line 172:		Line 172:
	return '{\| class="wikitable sortable"\n! Engineer !! Specialties !! Prerequisite Engineer !! Unlock requirement\n'		return '{\| class="wikitable sortable"\n! Engineer !! Specialties !! Prerequisite Engineer !! Unlock requirement\n'
	.. table.concat(rows, '\n') .. '\n\|}'		.. table.concat(rows, '\n') .. '\n\|}'
			end

			-- {{#invoke:Engineers\|count}}, returns how many Engineers currently have a
			-- canonical JSON record in Module:Data/Engineers/index -- used so pages that
			-- cite this number (e.g. List of Engineers' {{Article status}} uncertainty
			-- text) stay correct automatically as records are added, instead of a
			-- hand-typed number silently going stale.
			function p.count()
			return tostring(#loadIndex())
	end		end

	return p		return p

Sythan: Allow Engineer infobox fields to be edited on article pages

2026-08-13T03:42:50Z

Allow Engineer infobox fields to be edited on article pages

@@ Line 88: / Line 88: @@
 		end
 	end
 	return fields
 end

Sythan: Clean Engineer infobox output: grouped sections, concise labels, and JSON image support

2026-08-08T17:33:21Z

Clean Engineer infobox output: grouped sections, concise labels, and JSON image support

← Older revision		Revision as of 17:33, 8 August 2026
Line 17:		Line 17:
	-- the same shape of infobox whether or not a JSON record exists yet.		-- the same shape of infobox whether or not a JSON record exists yet.
	local FIELD_ORDER = {		local FIELD_ORDER = {
	{ key = 'engineer_type', label = 'Engineer type' },		{ key = 'engineer_type', label = 'Engineer type', group = 'ENGINEER' },
	{ key = 'system', label = 'System' },		{ key = 'system', label = 'System' },
	{ key = 'body', label = 'Body' },		{ key = 'body', label = 'Body' },
Line 24:		Line 24:
	{ key = 'allegiance', label = 'Allegiance' },		{ key = 'allegiance', label = 'Allegiance' },
	{ key = 'specialties', label = 'Specialties' },		{ key = 'specialties', label = 'Specialties' },
	{ key = 'max_grade', label = 'Maximum ~~engineering~~ grade' },		{ key = 'max_grade', label = 'Maximum grade' },
	{ key = 'prerequisite_engineer', label = 'Prerequisite ~~Engineer~~' },		{ key = 'prerequisite_engineer', label = 'Prerequisite', group = 'ACCESS' },
	{ key = 'discovery_requirement', label = 'Discovery ~~requirement~~' },		{ key = 'discovery_requirement', label = 'Discovery' },
	{ key = 'invitation_requirement', label = 'Invitation ~~requirement~~' },		{ key = 'invitation_requirement', label = 'Invitation' },
	{ key = 'unlock_requirement', label = 'Unlock ~~requirement~~' },		{ key = 'unlock_requirement', label = 'Unlock' },
	}		}

Line 81:		Line 81:
	fields.prerequisite_engineer = '[[' .. d.prerequisite_engineer .. ']]' .. note		fields.prerequisite_engineer = '[[' .. d.prerequisite_engineer .. ']]' .. note
	else		else
	fields.prerequisite_engineer = 'None — available from the start'		fields.prerequisite_engineer = d.prerequisite_engineer_display or 'None — available from the start'
	end		end
	else		else
Line 102:		Line 102:
	local fields = buildFields(d, pargs)		local fields = buildFields(d, pargs)

	local args = { name = name, image = ~~pargs.~~image }		local image = pargs.image
			if ( image == nil or image == '' ) and d and d.image then
			image = d.image
			end

			local args = { name = name, image = image }
	local n = 0		local n = 0
	for _, f in ipairs(FIELD_ORDER) do		for _, f in ipairs(FIELD_ORDER) do
Line 108:		Line 113:
	if value ~= nil and value ~= '' then		if value ~= nil and value ~= '' then
	n = n + 1		n = n + 1
			if f.group then
			args['group' .. n] = f.group
			end
	args['label' .. n] = f.label		args['label' .. n] = f.label
	args['row' .. n] = value		args['row' .. n] = value
Line 141:		Line 149:
	local d = loadRecord(name)		local d = loadRecord(name)
	if d then		if d then
	local prereq = d.prerequisite_engineer and ('[[' .. d.prerequisite_engineer .. ']]') or 'None'		local prereq = d.prerequisite_engineer and ('[[' .. d.prerequisite_engineer .. ']]') or ( d.prerequisite_engineer_display or 'None' )
	table.insert(rows, string.format(		table.insert(rows, string.format(
	'\|-\n\| [[%s]] \|\| %s \|\| %s \|\| %s',		'\|-\n\| [[%s]] \|\| %s \|\| %s \|\| %s',