Feedback:User/Arghore/Test Mounts

From Guild Wars Wiki
Jump to navigationJump to search

Please use the alpha and closed beta to test the addition of mounts to GW2.

It has been said that mounts wont be in the innitial release of GW2, this is fine, if one wants to do mounts good they will need their time to be developed. But seeing the game is currently in it's testing phaze I think it would be a good idea to atleast test ONE mount in the game. Mainly to see what impact it has on the game, the interaction during dynamic events, and to some extend what the addition of mounts mean for the general gaming experience, and to see what would and would not work for mounts in relation to GW2. The testing experience can yield interesting feedback in order to make the actual choice to add or not add mounts, and if so, then how to add them.

My suggestion would be to let the creature department brainstorm about possible mounts, to then pick one, and design and model it. Use this model to add the animations and skill effects. Implement the mount into the game by having an NPC hand them out (use either the interface or the skilbar with a 'charm mount' utility to make the mount active), if easy 'ban' mounts from cities.

To not have to come up with a whole system for mounts i will supply one that follows GW2 game mechanic conventions to use as a template, this is by no means a suggestion of how mounts should be implemented, but it's a way they could be implemented. By using it, the emphasis at Anet can be on testing the interaction of the mount with players and the game, providing insight for the actual implementation mounts (or dismissal).

When the mount is activated (through menu [v] or skill on bar) the mount appears, double click to mount it. The mount is controlled by the skills below. When mounted the player remains the target (aka. mount can not be targetted, and all damage is taken by the player), when the player is killed or when dismounting the mount follows (like pet) and doesn't take part in the game as a target of it's own (this to reduce needed development on the mount). The player looses access to the Profession Special Mechanic when mounted.

Skills:

  • s1. single target damage
  • s2. single target controll
  • s3. AoE damage
  • s4. AoE control
  • s5. AoE Buff
  • h6. Heal, heal the player
  • u7. Trottle, 1 stack of swiftness for 25 seconds [no recharge]
  • u8. Gallop, 2 stacks of swiftness for 15 seconds [5s recharge]
  • u9. Fleeting Gallop, 3 stacks of swiftness for 5 seconds [15s recharge]
  • E10. Dismount

all catagories of s1-s5 to test the various options for skills

I would advice to have a small team of 2-3 people take this suggestion through the development cycle (creature department, animation, skills, back end programming, implementation) and to manage a feedback page on the internal wiki. At all times during this process this team should stress that the effort is for testing one mount only, and by no means does it mean mounts are 'in'. Feedback and suggestions are welcome, but by no means is extensive mount content development encouraged, no extra mounts are needed, nor does there have to be any effort put into lore or other mountsystem development, this can all be done after testing. Some minor tweaks might have to be done to the output of it's 5 skills. Optional testing encouragement, city to city race on friday night, or Cavelry battle in WvW.

Hopefully this testing will show how suited GW2 is for mounts, or not. Using the current alpha and closed beta testing means that mounts can be tested in the test phaze of GW2, by a large crowd, and through this testing a final yes/no can be given based upon actual experience, instead of theory crafting and emotional (dis)favor for mounts. In case of a NO there is extensive material available (possible vid) to show that mounts have been given a fair test and were dismissed because A,B,C. This will increase the acception for a possible No by the community. While on the other hand experience is gained with mounts in GW2 that can help with the development of more mounts and the final implementation, in case of a Yes.