Having an error as Position in a explosion cause studio crash

System Information:
Windows 11 Pro 25h2

Beta Features:
New luau solver

Hi, thanks for the report! I wasn’t able to reproduce your problem, could you provide a reproduction file for us to look into? I might be missing some workspace properties or settings somewhere.

Sure, just noticed warning before the crash happens.

Will send the place in private message.

After a bit of looking here my config:
Streaming:
ModelStreamingBehavior: Improved
StreamingMinRadius: 1700
StreamingMaxRadius: 2700

And lot of parts that were put in cache by studio. (tested by importing the buildings from the place the issue happened to a baseplate place)

The crash you’re experiencing is likely caused by passing an invalid or nil Position value to the Explosion object, which the new Luau solver is now catching more strictly than before.Here’s what’s probably happening:Common causes:- Creating an Explosion with Position = nil instead of a Vector3- Referencing a destroyed part’s Position after it no longer exists- Position being set to a non-Vector3 value (string, number, etc.)- The part containing the explosion logic getting removed before the explosion firesQuick fix:lualocal explosionPos = script.Parent.Position -- Always verify this exists firstif explosionPos then local explosion = Instance.new("Explosion") explosion.Position = explosionPos explosion.Parent = workspaceelse warn("Position is nil, check if parent part exists")endBetter approach — validate before creating:lualocal targetPart = script.Parentif not targetPart or not targetPart.Parent then warn("Target part doesn't exist") returnendlocal explosion = Instance.new("Explosion")explosion.Position = targetPart.Positionexplosion.BlastRadius = 20explosion.BlastPressure = 500000explosion.Parent = workspaceThe Studio crash specifically happens because the new Luau solver performs stricter type checking at runtime. It’s catching type mismatches earlier, which is actually good—it forces you to write cleaner code.**Debugging steps:**1. Add print() statements before creating the Explosion to verify Position is a valid Vector32. Check that the part/object with the Position property still exists in the workspace3. Use assert() to catch nil values: assert(explosion.Position, "Position must be set")If you’re triggering this from a RemoteEvent (common for explosions in combat systems), ensure the Position is validated on both client and server before passing it through.

1 Like