Opened 8 years ago

Closed 8 years ago

Last modified 7 years ago

#4232 closed defect (fixed)

Temple of Vesta and Wonder Temples don't have the same techs and production queues

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

Description

The temple of vesta doesn't have the roman civ specific tech (vision range upgrade) to research. It could perhaps inherit rome_temple. Reported by javiergodas.

Some wonders are temples and received the wonder aura in r18024. These temples should also be able to train the same production queue and techs one would assume (might be nasty to implement, as one can't inherit to building types).

Attachments (2)

vesta.diff (816 bytes ) - added by fatherbushido 8 years ago.
vesta_v2.diff (1001 bytes ) - added by elexis 8 years ago.
Sure this one isn't better?

Download all attachments as: .zip

Change History (14)

comment:1 by fatherbushido, 8 years ago

I don't know if it's a good idea to produce the generic stuff in this temple (in the same way, we don't produce the same things in barracks and in gymnasium or sysitton). Perhaps allowing the healers production is ok but I m not convinced by the techs.

comment:2 by elexis, 8 years ago

  • Barracks need a tech to research champions, since barracks are cheaper than fortresses. That doesn't apply to the wonder. The implementation here would require us to either copy either the wonder or template entries to that template or implement inheriting from multiple templates, which seems like a too big task for this issue alone. So I guess we simply can't implement it without poisoning the templates.
  • The temple of vesta having everything the roman temple got, but not having that one civ unique tech seems too odd to me and should be fixed IMO.

comment:3 by fatherbushido, 8 years ago

For 2) you mean move the sybilline books tech from generic temple to the Vesta temple ? As it's a specific techs, it's can be good to move it to a specific building (needs to check if it's kinda related with vesta ?)

comment:4 by elexis, 8 years ago

From a gameplay pov that sounds good, but I couldn't find any connection from the temple of vesta to the sybilline books.

by fatherbushido, 8 years ago

Attachment: vesta.diff added

comment:5 by fatherbushido, 8 years ago

In fact I didn't understand. You meant vesta temple is a temple (it inherits) and can produce all the temple can excepting that special tech.

comment:6 by elexis, 8 years ago

Any reason not to inherit rome_temple?

comment:7 by fatherbushido, 8 years ago

You have to write the same entries (but different) so I find it less clean. But both are equal imo.

by elexis, 8 years ago

Attachment: vesta_v2.diff added

Sure this one isn't better?

comment:8 by fatherbushido, 8 years ago

dunno, i found it less clean as all the entries are replacement. but that s perhaps not objective

comment:9 by elexis, 8 years ago

So I could commit it and say reviewed by fatherbushido (not stating that you liked the patch)? X)

Everytime something is changed in rome_temple, it will have to be changed in the vesta one too, so it sounds error prone and messy to add this one entry. Most of the vesta entries are replacements, but none of them are added to cover something up. It seems unlikely that properties are added to the one temple that shouldn't also go to the vesta one.

comment:10 by fatherbushido, 8 years ago

ok

comment:11 by elexis, 8 years ago

Owner: set to elexis
Resolution: fixed
Status: newclosed

In 18753:

Offer the same techs and production queue at the Temple of Vesta as are available to the general roman temple (in particular Sibylline Books tech).
Reviewed by fatherbushido, fixes #4232.

comment:12 by elexis, 7 years ago

In 18911:

Revert r18753 as it revealed an OOS on rejoin in the engine code, refs #4232 #4316.

Note: See TracTickets for help on using tickets.