[UPDATE] A possible mix-up with Power Ring Spawners?

I think there might be a mix-up with the Power Ring Spawners in the SFX Shop. In the document lump it says to use the THIRD argument to control the size of the area for the ring spawners, but when I changed the SECOND argument of the blue one in SLADE and tested it ingame, the ring was bigger. I did manage however to include an updated wad shown below with the second and third arguments in DOCUMENT switched around. Is there a mistake, or am I mistaken?.

Looks like you're right; Args[1] (the second arg) controls the X offset, whereas Args[2] (the third arg) controls the Z velocity. The documentation has it backwards; luckily, fixing the documentation will be easy. Thanks for pointing this out!

EDIT: I moved this thread into the Repository section so it can be treated like a formal update thread so we can track changes.

I also noticed that the documentation states to use the first two args to control the spawn; however, it actually uses the 2nd and 3rd args (arg 1 does nothing). So I changed this and rolled the updated documentation into the package, with the demo map preserved as a separate WAD within the archive. I also added INFO and CREDITS lumps to the wad. The download is here, in case anybody else wants to test it out:

https://www.dropbox.com/s/cdmq0k4nh4lbj00/PowerRingPads.zip?dl=0

Oh, and it just occurred to me that the flags for A_SpawnItemEx are in numeric format, rather than using constants. This will need to be changed for readability's sake. The flags value is 129; I believe this represents SXF_TRANSFERTRANSLATION (value = 1) and SXF_CLIENTSIDE (value = 128), but I'll need someone knowledgeable about this to confirm. (The wiki no longer has the numeric values for each constant listed.)

That's correct.

Thanks! I've updated the download with constants used instead of numbers. I also noticed that there was an orb spawn missing at the 300 degree angle, and a redundant spawn at 360 degrees (there's already a spawn at 0 degrees, which is technically the same); so, I fixed that as well. I've also added an UPDATES lump. Please review.

Approved.

Updated.