Sometimes the webclient will continue to draw a missile (generated with the missile() proc) standing there after the missile has reached its target. While investigating this, I discovered a number of other irregularities:
1. Missiles appear to instantly cross space in webclient.
2. Missiles may be blocked by dense atoms in webclient (unverified, but would explain some otherwise random things), and may stick around indefinitely after hitting somethign.
3. Missiles are confused by moving targets in webclient, and may stick around indefinitely.
Numbered Steps to Reproduce Problem:
Create an environment with moving and unmoving mobs and a verb that generates a missile() towards them. Hosting in webclient, you will never see your missile when used against an unmoving mob.
For the sake of detail: all my test missiles are generated from an object prototype. Some have icons, some have maptext. All prototypes used have a glide_size specified.
Code Snippet (if applicable) to Reproduce Problem:
missile(obj/prototype,src,target)
Expected Results:
Missile is animated crossing the screen at a rate commensurate with glide_size until it reaches target; missile then vanishes.
Actual Results:
Missile fails to appear or appears near the target and stays.
Does the problem occur:
Every time? Or how often? Missiles generated under the conditions described above misbehave with 100% consistency, though as described above the manifestation varies somewhat.
In other games? In both RealmLike and a test environment.
In other user accounts? Yes, it was reported by a player.
On other computers? Yes, see above.
When does the problem NOT occur? When doing the same thing in Dreamseeker.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? I am unsure.
Workarounds:
Targeting the turf at a mob's feet at least prevents the obvious glitch of the missile hanging around or jumping around erratically, but it does not render the missile.
