0000747: Creature Banks - In H3, the upgraded stack was in the bottom-left corner of the screen, in VCMI it's placed center-right

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000747

VCMI

Mechanics - Objects

public

2011-05-31 23:17

2022-04-06 13:31

Reporter

Zamolxis

Assigned To

Warmonger

Priority

low

Severity

feature

Reproducibility

always

Status

closed

Resolution

won't fix

Platform

OS Version

Product Version

0.84

Target Version

Fixed in Version

Summary

0000747: Creature Banks - In H3, the upgraded stack was in the bottom-left corner of the screen, in VCMI it's placed center-right

Description

Honestly, I'm beginning to prefer where we have the upgraded stack in VCMI. It somehow makes more sense to have the upgraded stack located somewhere central.

In fact, I believe H3 had the upgraded stack there *because* of the basic principle according to which "the stack of neutrals which should have a random chance of being upgraded, should be the middle one". This looked good for normal battles with Adventure Map monsters, where the middle stack was central-placed. But perhaps the principle was then just badly applied at creature banks where, according to the order of action, the bottom-left stack is the 3rd out of 5, hence the middle one.

So my vote goes for keeping the logic as it is today in VCMI, but the topic is of course open for discussion in the comments area below.

Tags

No tags attached.

Attached Files

Relationships

related to

0000407

closed

Warmonger

Creature Banks - Sometimes all 5 defending stacks are upgraded

Notes
(0002091) yupsi (developer) 2011-10-16 20:47 edited on: 2011-10-16 20:48	I think it's just the question of supporting gameplay purism. There are some HoMM3 (not even WoG) RPG-like maps where every little peasant counts and every battle must be perfected. In teh end, I'd keep new behaviour as a default one and make it into an option only if someone really requests for it.

(0008271) Povelitel (updater) 2022-04-06 13:31	Retained OH3 design

Issue History
Date Modified	Username	Field	Change
2011-05-31 23:17	Zamolxis	New Issue
2011-05-31 23:17	Zamolxis	Status	new => assigned
2011-05-31 23:17	Zamolxis	Assigned To	=> Tow
2011-05-31 23:17	Zamolxis	Issue generated from: 0000407
2011-05-31 23:17	Zamolxis	Relationship added	related to 0000407
2011-06-01 05:02	Warmonger	Assigned To	Tow => Warmonger
2011-10-16 20:47	yupsi	Note Added: 0002091
2011-10-16 20:47	yupsi	Note Edited: 0002091	View Revisions
2011-10-16 20:48	yupsi	Note Edited: 0002091	View Revisions
2022-04-06 13:31	Povelitel	Note Added: 0008271
2022-04-06 13:31	Povelitel	Status	assigned => closed
2022-04-06 13:31	Povelitel	Resolution	open => won't fix

Site | Forums | Wiki | Slack | GitHub