Projectile Setup Improvement and Starcraft Observations

Today I did some work on implementation of the projectile setup in XML. Before the projectile property, such as speed, trail texture, hit explosion effects etc are hard coded for different type of projectile, such as bullet and missile. But with the new property setup in the item property file, I have greater control over the projectile property. Now I can have different missile type, different guns etc. It make the weapon system more complete. I still need to finish the rest of setup property off, clean up and test. The next step in the weapon system development would be more different type of firing such as spread shots, and new type of weapon like grenade. The screen shot shows the new particles from submachine gun bullets and missiles.
Also I reinstalled Starcraft, play it a little, and test out its campaign editor. As expected, it gave me some new ideas about my stage editor. From my observation so far, it seems my stage constructor is a bit more complex and versatile in some way. For example, my stage can have elevation of different height, while the Starcraft's stage seems to have only 1 higher elevation, 1 middle and 1 lower elevation, and some impassable terrain (like water, ceiling and bottomless pit).
The ideas Starcraft given me is great. From my observation, it seems the sides and top of a tile's texture is randomized. It meant in one tile set, there are different sides and tops, each can be combine with the others, which is unlike mine, which only has 1 type of top and 1 type of side for a tile set. But I think it's actually not too difficult for me to implement multiple sides and tops for a tile set, ie it will fit well in my current system. This implementation will give me more vividness and variety into my stage environment. Another interesting thing I observed is the "ceiling" tile in the installation environment. From my current understanding it's just a impassable obstacle. I actually had the same idea before: tile that indicated as wall so the player can't jump onto it. I wasn't sure if it should be done or how it should be done, but the SC editor might give me some ideas.