Project

General

Profile

Feature #690343

Add "Performance" column to city report

Added by Jacob Nevins 10 months ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Client
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

We have a "History" column, but not "Performance". (No current ruleset uses performance, but custom ones might.)

(This is the first time the term "performance" appears in the UI, I think. I'm finding the terms 'performance' and 'acts' a bit clunky, but haven't thought of anything better. Perhaps recognise that quantifying culture is fairly artificial, and replace 'acts' with 'points'?)

m-30-26-performance-report.patch (2.82 KB) m-30-26-performance-report.patch master, S3_0, S2_6 Jacob Nevins, 2017-08-13 02:29 PM
m-30-26-performance-report-bis.patch (4.92 KB) m-30-26-performance-report-bis.patch Jacob Nevins, 2017-08-14 10:57 PM

History

#1 Updated by Jacob Nevins 10 months ago

#2 Updated by Marko Lindqvist 10 months ago

Not that I oppose the patch, but there's a difference between History and Performance that former is know to be correct since it comes from the server while Performance is client's guess.

#3 Updated by Jacob Nevins 10 months ago

That's true. (The city dialog's popup probably ought to have an arrangement like the Corruption one does, to report any discrepancy.)

#4 Updated by Jacob Nevins 10 months ago

New patch, which uses the correct value in the city report and also reports any discrepancy in the city dialog.

Here's the example effect I used to test it.

; Example of an effect the client might not know about       
[effect_writing_culture]                                     
type    = "Performance"                                      
value  = 2                                                   
reqs   =                                                     
    { "type", "name", "range"                                
      "Tech", "Writing", "Alliance"                          
    }                                                       

#5 Updated by Jacob Nevins 9 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF