Factorio Forums

spiro9 wrote: ↑Mon Jan 15, 2024 11:30 am … I've noticed there's no way to change an individual ammo item's set range, despite the fact that other ranges throughout the game can be configured with mods. Enabling ammo ranges to be tweaked alongside other ranges (turrets, guns, etc.), via mod config settings, technology upgrades, etc. …

Pi-C wrote: ↑Mon Jan 15, 2024 2:42 pm You want to change the range during the control stage -- is that correct? ... Properties like "turret_range" or "radar_range" belong to LuaEntityPrototype and are read-only. You can modify these, but only on starting the game (during data stage).

BraveCaperCat wrote: ↑Mon Jan 15, 2024 10:59 pm Use ammo_type.range_modifier, as said by the first reply to your post.

heyqule wrote: ↑Tue Jan 16, 2024 3:23 am You can set the max range for the projectiles under action delivery.

https://lua-api.factorio.com/latest/typ ... ivery.html

Code: Select all

        attack_parameters = {
            ammo_type = {
                category = "laser",
                target_type = "entity",
                action = {
                    type = "direct",
                    action_delivery = {
                        type = "projectile",
                        projectile = "projectile-name',
                        starting_speed = 0.35,
                        max_range = attack_range * 1.5  <<<< This will set the max range of the projectile.
                    }
                }
            },
        }

-- This mod overwhelms the game's handling of default & modded ammo types, which appear to be strictly range-limited to around a maximum of 30-50
-- However, there is no indication that this range-limit is hardcoded so much as a softcoded "suggestion" from which to build
-- Iterating over each and setting its range to something absurd should help in correcting this issue
-- Rather, in simpler terms, look through every single ammo item and check for a maximum range, then if one is found, set it to something like 1000 so ammo can fly forever >:D
for _, a in pairs(data.raw["ammo"]) do
	local t = a.ammo_type
	if t.action then
		for _, q in ipairs(t.action) do
			if q.action_delivery then
				if q.action_delivery.max_range then
					log("Before: " .. tostring(q.action_delivery.max_range))
					local c = q.action_delivery.max_range
					
					q.action_delivery.max_range = 1000
					log("After: " .. tostring(q.action_delivery.max_range))
					
					if c == q.action_delivery.max_range then
						log("Uh-oh! These are the same!")
					end
				end
			end
		end
	end
end

BraveCaperCat wrote: ↑Tue Jan 16, 2024 8:43 am

spiro9 wrote: ↑Tue Jan 16, 2024 8:37 am

heyqule wrote: ↑Tue Jan 16, 2024 3:23 am You can set the max range for the projectiles under action delivery.

https://lua-api.factorio.com/latest/typ ... ivery.html

Code: Select all

        attack_parameters = {
            ammo_type = {
                category = "laser",
                target_type = "entity",
                action = {
                    type = "direct",
                    action_delivery = {
                        type = "projectile",
                        projectile = "projectile-name',
                        starting_speed = 0.35,
                        max_range = attack_range * 1.5  <<<< This will set the max range of the projectile.
                    }
                }
            },
        }

Can you post your log?

I'm already doing this:

Code: Select all

-- This mod overwhelms the game's handling of default & modded ammo types, which appear to be strictly range-limited to around a maximum of 30-50
-- However, there is no indication that this range-limit is hardcoded so much as a softcoded "suggestion" from which to build
-- Iterating over each and setting its range to something absurd should help in correcting this issue
-- Rather, in simpler terms, look through every single ammo item and check for a maximum range, then if one is found, set it to something like 1000 so ammo can fly forever >:D
for _, a in pairs(data.raw["ammo"]) do
	local t = a.ammo_type
	if t.action then
		for _, q in ipairs(t.action) do
			if q.action_delivery then
				if q.action_delivery.max_range then
					log("Before: " .. tostring(q.action_delivery.max_range))
					local c = q.action_delivery.max_range
					
					q.action_delivery.max_range = 1000
					log("After: " .. tostring(q.action_delivery.max_range))
					
					if c == q.action_delivery.max_range then
						log("Uh-oh! These are the same!")
					end
				end
			end
		end
	end
end

This code however has no effect despite logs confirming the change is being made in the data-final-fixes substage.

spiro9 wrote: ↑Tue Jan 16, 2024 8:47 am

BraveCaperCat wrote: ↑Tue Jan 16, 2024 8:43 am

spiro9 wrote: ↑Tue Jan 16, 2024 8:37 am

heyqule wrote: ↑Tue Jan 16, 2024 3:23 am You can set the max range for the projectiles under action delivery.

https://lua-api.factorio.com/latest/typ ... ivery.html

Code: Select all

        attack_parameters = {
            ammo_type = {
                category = "laser",
                target_type = "entity",
                action = {
                    type = "direct",
                    action_delivery = {
                        type = "projectile",
                        projectile = "projectile-name',
                        starting_speed = 0.35,
                        max_range = attack_range * 1.5  <<<< This will set the max range of the projectile.
                    }
                }
            },
        }

Can you post your log?

I'm already doing this:

Code: Select all

-- This mod overwhelms the game's handling of default & modded ammo types, which appear to be strictly range-limited to around a maximum of 30-50
-- However, there is no indication that this range-limit is hardcoded so much as a softcoded "suggestion" from which to build
-- Iterating over each and setting its range to something absurd should help in correcting this issue
-- Rather, in simpler terms, look through every single ammo item and check for a maximum range, then if one is found, set it to something like 1000 so ammo can fly forever >:D
for _, a in pairs(data.raw["ammo"]) do
	local t = a.ammo_type
	if t.action then
		for _, q in ipairs(t.action) do
			if q.action_delivery then
				if q.action_delivery.max_range then
					log("Before: " .. tostring(q.action_delivery.max_range))
					local c = q.action_delivery.max_range
					
					q.action_delivery.max_range = 1000
					log("After: " .. tostring(q.action_delivery.max_range))
					
					if c == q.action_delivery.max_range then
						log("Uh-oh! These are the same!")
					end
				end
			end
		end
	end
end

This code however has no effect despite logs confirming the change is being made in the data-final-fixes substage.

Log file.

spiro9 wrote: ↑Tue Jan 16, 2024 9:13 am The only reason I can think of regarding other mods overriding the behavior of mine is, my attempt to ensure my mod loads last by appending 'zzzzzz' was futile.

• data: Create the essential prototypes for your mod.
• data-updates (optional): Create optional prototypes and adjust your essential prototypes depending on what the other mods have created.
• data-final-fixes (optional): Make final adjustments to existing prototypes, but don't create new ones!

Pi-C wrote: ↑Tue Jan 16, 2024 11:11 am

spiro9 wrote: ↑Tue Jan 16, 2024 9:13 am The only reason I can think of regarding other mods overriding the behavior of mine is, my attempt to ensure my mod loads last by appending 'zzzzzz' was futile.

It doesn't really make sense to use prefixes like "zzz" for making your mod load last. Other modders may also want to load last, so they might add a 'z' more … The best way is to add (optional) dependencies on the mods known to interfere with yours. Also, the multi-phase data stage is useful if everybody follows some guidelines:

• data: Create the essential prototypes for your mod.
• data-updates (optional): Create optional prototypes and adjust your essential prototypes depending on what the other mods have created.
• data-final-fixes (optional): Make final adjustments to existing prototypes, but don't create new ones!

If you want to see whether any other mods have overwritten your changes, you can use the in-game prototype browser. You can use CTRL+SHIFT+E to open a GUI that provides access to all prototypes in the game, or you can hover your cursor over any entity, item, recipe etc. and type CTRL+SHIFT+F to directly open the view of its prototype. Also, when hovering the cursor over something, the description appearing on the right side of the display shows the order in which mods created/changed the prototype.