I apparently checked the GMod news feed from November 6th and it said "BETA RELEASE" on top and not "NEWS".

So it is likely not just an announcement, but also a small hotfix.

Indeed, this broke several addons, including mine, the Team Fortress 2 Bots. Looks like this is a pretty widespread issue.

引用自 MrNiceGuy518：

Indeed, this broke several addons, including mine, the Team Fortress 2 Bots. Looks like this is a pretty widespread issue.

I've created a fix for my addon, perhaps the author of this one will see this post and may find this helpful.


The second argument of ENTITY:CreateParticleEffect() must now be a model attachment, and the table that used to define particle control points seems to now be unused.

What I found is that ENTITY:CreateParticleEffect() actually returns an instance of CNewParticleEffect, which has a variety of methods for controlling the particle system, including control point definitions via CNewParticleEffect:AddControlPoint(): https://wiki.facepunch.com/gmod/CNewParticleEffect:AddControlPoint

The indices of the control points are now explicitly specified in the first argument of the aforementioned method, rather than implicitly derived from the indices of the table formerly passed in the second argument of the original function.


Here's an example from some of my tests that may prove useful:

THIS:
local CPoint0 = {
["entity"] = entity1,
["attachtype"] = PATTACH_ABSORIGIN_FOLLOW,
}
local CPoint1 = {
["entity"] = entity2,
["attachtype"] = PATTACH_ABSORIGIN_FOLLOW,
}
entity1:CreateParticleEffect("medicgun_beam_red",{CPoint1,CPoint0})


Must become, THIS:
local pfx = entity1:CreateParticleEffect("medicgun_beam_red",0)
pfx:AddControlPoint(0, entity1,PATTACH_ABSORIGIN_FOLLOW)
pfx:AddControlPoint(1, entity2,PATTACH_ABSORIGIN_FOLLOW)



Hope that helps someone!

same problem

引用自 MrNiceGuy518：

引用自 MrNiceGuy518：

Indeed, this broke several addons, including mine, the Team Fortress 2 Bots. Looks like this is a pretty widespread issue.

I've created a fix for my addon, perhaps the author of this one will see this post and may find this helpful.


The second argument of ENTITY:CreateParticleEffect() must now be a model attachment, and the table that used to define particle control points seems to now be unused.

What I found is that ENTITY:CreateParticleEffect() actually returns an instance of CNewParticleEffect, which has a variety of methods for controlling the particle system, including control point definitions via CNewParticleEffect:AddControlPoint(): https://wiki.facepunch.com/gmod/CNewParticleEffect:AddControlPoint

The indices of the control points are now explicitly specified in the first argument of the aforementioned method, rather than implicitly derived from the indices of the table formerly passed in the second argument of the original function.


Here's an example from some of my tests that may prove useful:

THIS:
local CPoint0 = {
["entity"] = entity1,
["attachtype"] = PATTACH_ABSORIGIN_FOLLOW,
}
local CPoint1 = {
["entity"] = entity2,
["attachtype"] = PATTACH_ABSORIGIN_FOLLOW,
}
entity1:CreateParticleEffect("medicgun_beam_red",{CPoint1,CPoint0})


Must become, THIS:
local pfx = entity1:CreateParticleEffect("medicgun_beam_red",0)
pfx:AddControlPoint(0, entity1,PATTACH_ABSORIGIN_FOLLOW)
pfx:AddControlPoint(1, entity2,PATTACH_ABSORIGIN_FOLLOW)



Hope that helps someone!

I see.
This mod hasn't been updated since 2017, so the code this addon uses seems to be obsolete. I'm not a coding expert, btw.

I am having issues with this as well, this needs an update.

Should be fixed now, let me know if there's still problems.

引用自 no loafing：

Should be fixed now, let me know if there's still problems.

Thanks for finding this out! It has been fixed.

I retitled the discussion so everyone should ignore it now.

I think this mod was indeed broken from the GMod update since I am on the x86-64 branch, which is one of the many branches that test out upcoming major updates every few months or so. Thanks to my effort and the creator, it has been fixed since November 15th.