It's the 'execute file' action, if you didn't find it.

I'd go with pairer object, the other methods look a bit hacky.

Was it this?

What linkman said. Trigger once only runs where you have repeated conditions which go on/off in cycles, mainly collisions.

It's normal for some CPU to be being used even when idle, don't worry about it.

Haha.. wow, well, it should probably still work, but it's not really a problem.

Those events will run every tick, if you don't want them to, set a variable or use functions, so they only run once.

I don't like the fact someone new to WoW has to pay a chunky upfront fee and then continue to pay; other MMORPGs and games have it right by just charging subscription. Charging a very nominal fee for WoW and the expansions is fine, they have to cover the disc and box costs, but if you want to download it you shouldn't have to pay.

The particle system's an optimised system of particle display which by optimisation precludes certain functions, which very few people need. Collisions for 1000s of particles would slow a game to a crawl, for example. (In any case, the particles are custom drawn, and are not sprites.)

Asking for certain things to be wangled into plugins or behaviors is like asking for a 'make my game for me button' .

Just curious, what would you want to add to it (and are you using it for its intended purpose, the display of data on screen)? Most functions are wrapped in the ACEs, so if you need anything and it's useful we could always add it.

Did the original pause during scrolling?

It's infeasible for individual particles to test for collisions; in most cases it'd be very very slow. You can always create a custom particle solution if it's necessary.

The listbox object doesn't draw anything, it just wraps MFC's CListBox.