To make a very primitive eventParticle() all you have to do is this:

This will only work for particles spawned with the Module API, sadly. You also have to replace tfm.exec.displayParticle() with tfm.exec.dP().
I don't really know what eventParticle() is useful for, but I bet you could find something.

Alternatively you can do:

dP = tfm.exec.displayParticle
function tfm.exec.displayParticle(id,x,y,vx,vy,ax,ay,name)
eventParticle(id,x,y,vx,vy,ax,ay,name)
dP(id,x,y,vx,vy,ax,ay,name)
end
function eventParticle(id,x,y,vx,vy,ax,ay,name)
print "Particle event!"
end

Which will give the same results if used with the default tfm.exec.displayParticle()

lol, I knew that I could just do dP, but I liked the tfm.exec.dP() :P

You seemed to have misunderstood me. xD I meant with the script I posted, eventParticle() triggers even if you use the default tfm.exec.displayParticle().

No, I understood, I just didn't want to admit I was wrong :P

Is there any practical use for this? objectList and playerList are lists that make sense since they're things that update and can be removed. Particles on the other hand can't be modified or removed as they're spawned and disappear within a second.

Well, I just thought it was cool. But I bet if someone wanted to have a special place for stuff when they play certain particles instead of just having it within the loop with tfm.exec.displayParticle().