Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

  Click here to go to the first Developer post in this thread.  

Thread: Wiki Wish List vs. BTS

  1. #11
    Quote Originally Posted by (TheRocket @ April 15 2007,23:42)
    Why not include a community wishlist, with wishes the community can complete /add (like weapons etc) and just wish engine specific wishes on the bts?
    I read the whole wishlist and some wishes could easily be made by the community, when they get the tools

    Thats my wish!
    a good one

  2.   This is the last Developer post in this thread.   #12
    well ...

    but by that logic You can say "community would program whole new engine"
    in OSS style and don't bother with ArmA at all right?

    i know bit overstated irony

    yet most of wishlist ideas are in hope it will be "default" part of game w/o need dl xyz ...




  3. #13
    Aim is basically to avoid 1000 times expressing the same wishes, rather adding/commenting issues/wishes/feature requests at a specific place in a controlled way. For some features I would even like to trigger the creation of real design documents with focus on player needs so that development of BI can use this as an input for functionality evaluation and UI design.

    I read in 100 places almost identical suggestion, mainly high level and always addressing just small chunks of a very complex issue.

    Like with the inventory management I want to generate with the help of the community a design paper which should be agreed when it reached a certain quality.

    If it is then used by BI to make paper birds is a risk we have to take, but this paper is then ready to use for ANY company since the demands do not change dramatically.

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •