Changes between Version 1 and Version 2 of Ticket #52, comment 33


Ignore:
Timestamp:
Jun 19, 2014, 4:12:43 PM (10 years ago)
Author:
Yves

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #52, comment 33

    v1 v2  
    77||Filtering on gamesetup screen||Players may want to identify: maps with special missions (1), historical accurate missions (2) and maps with completely changed gameplay (3). The difference between scenario and skirmish maps is currently only if the setup is fixed or not (players, victory conditions starting resources etc.). For both triggers can make sense and for both it would be interesting for the player to be able to indentify maps with triggers and special behaviour easily (scenarios will probably use triggers in most cases in the future though). Suggestion: Add a "mission" keyword to skirmish maps, scenario maps and random maps (1). Add the keywords "Historical" for scenario maps (2). Use the map description to show how much gameplay changes due to the triggers (3) because the definiton is too blurry for a filter/keyword.  I'm not sure if having different keywords for scenarios and skirmish maps is currently supported. "Historical" only really makes sense with a fixed map setup IMO, so it doesn't fit well for skirmish maps or random maps.||General||TODO||
    88||Multiplayer/Singleplayer compatibility||Some missions are meant for multiplayer and others not. This starts getting a real issue with triggers. Some mission scripts might be completely untested and broken for multiplayer games, others just aren't meant for that conceptually. The same applies the other way around (missions meant for multiplayer not working well in singleplayer), especially because the AI might not understand special victory conditions and behave completely stupid from that point of view. Other missions might work well for both multiplayer and singleplayer missions. Suggestion: IMO this should not be solved with map keywords (at least not how they work currently). Incompatible maps should not be shown at all on the gamesetup screen. I think we need to add another property to the map JSON data that defines if the map is compatible with singleplayer and multiplayer. This needs to be checked on the gamesetup screen and only supported maps should be displayed.||General||TODO||
    9 ||clone the data to be sure it's only modified locally||This way of cloning only works for non-object properties like strings or numbers (check the example below).||Trigger System||TODO||
     9||clone the data to be sure it's only modified locally (comment in Trigger.js)||This way of cloning only works for non-object properties like strings or numbers (check the example below).||Trigger System||TODO||
    1010
    1111