Skip to content

Conversation

@HyperJeanJean
Copy link
Contributor

The empire screen show the trade information based on the empire objects, but everything else in the game uses the city objects data, e.g. to determine if a resource can be traded or if it should be shown in the trade advisor. In almost all cases, this is perfectly fine as the city objects data is initialized from the empire objects data.

In Damascus though (and potentially other cases), there is an inconsistency between the two: the empire screen shows that Tarsus could export marble even though it actually can't because the city data says the opposite.

This change is a proposal to actually use the city data instead of the empire data in the empire screen. IMHO given that the empire data is only used to initialize the city data, it makes little to no sense to continue showing the empire data the whole game when the city data is available. This should ensure that the data shown by the empire screen is actually relevant to the player.

Before:
image

image

After:
image

image

As far as I can tell, this does not affect the gameplay but this is a change from the original Caesar 3 anyway so feel free to close it if does not fit into the scope of Julius.

This notably affects Damascus where a city could not export marble even
if the empire screen says so. With that change, that resource import is
now hidden.
@QuakeIV
Copy link

QuakeIV commented Sep 9, 2025

I'm in favor of this personally

@bvschaik bvschaik merged commit 62d0a3f into bvschaik:master Dec 14, 2025
13 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants