Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#4184 closed defect (fixed)

Misleading mapsize description

Reported by: elexis Owned by:
Priority: Should Have Milestone: Alpha 21
Component: UI & Simulation Keywords:
Cc: Patch:

Description

As reported in comment:2:ticket:4141:

The "mapsize" option for random map scripts in the gamesetup is wrong and misleading.

The title recommends a number of players which doesn't actually correlate to the effective mapsize. A "normal" map seems to be the perfect size for 3-8 player matches. A "small" or "medium" mapsize seem to be the best options for 1v1 matches.

If one picks a mapsize smaller than normal, the own territory will border to enemy territory from the beginning and at most one CC can be built in neutral territory.

If one picks a mapsize greater than normal, the performance will reduce drastically and one needs a long time to reach the enemy city, having a negative impact on the playability (boring waiting times, too much territory to control, bad for sending reinforcements).

The current options (see map_sizes.json) are:

{
{
	"Name": "Tiny",
	"LongName": "Tiny",
	"Tiles": 128
},
{
	"Name": "Small",
	"LongName": "Small (2 players)",
	"Tiles": 192
},
{
	"Name": "Medium",
	"LongName": "Medium (3 players)",
	"Tiles": 256,
	"Default": true
},
{
	"Name": "Normal",
	"LongName": "Normal (4 players)",
	"Tiles": 320
},
{
	"Name": "Large",
	"LongName": "Large (6 players)",
	"Tiles": 384
},
{
	"Name": "Very Large",
	"LongName": "Very Large (8 players)",
	"Tiles": 448
},
{
	"Name": "Giant",
	"LongName": "Giant",
	"Tiles": 512
}

Options to address this is either correcting or removing LongName altogether.

Change History (1)

comment:1 Changed 3 years ago by elexis

Keywords: simple removed
Milestone: BacklogAlpha 21
Resolution: fixed
Status: newclosed

Fixed by r18854.

Last edited 3 years ago by elexis (previous) (diff)
Note: See TracTickets for help on using tickets.