0000168: Tavern heroes are not randomly generated (except for the 1st hero generated in the left slot at the beginning of every week)

MantisBT - VCMI

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0000168

VCMI

Mechanics - Town structures

public

2009-10-15 22:45

2009-12-22 15:57

Reporter

Zamolxis

Assigned To

Warmonger

Priority

normal

Severity

minor

Reproducibility

always

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

0.74

Target Version

Fixed in Version

0.75

Summary

0000168: Tavern heroes are not randomly generated (except for the 1st hero generated in the left slot at the beginning of every week)

Description

LEFT TAVERN SLOT - CORRECT BEHAVIOR (apparently): The left Tavern slot seems to generate correctly a hero at the beginning of every week (associated with the alignment, apparently randomly selected, more testing needed to confirm).

LEFT TAVERN SLOT - INCORRECT BEHAVIOR: After the correctly generated hero at the beginning of every week, what follows are heroes selected in descending order of their alignments (first all Conflux heroes, then Fortress, etc).

RIGHT TAVERN SLOT - INCORRECT BEHAVIOR 1: Always Sir Mullich (reported also a 0000076)

RIGHT TAVERN SLOT - INCORRECT BEHAVIOR 2: Same as for the left slot, after Sir Mullich is bought, we get only heroes ordered by alignment (descending)

RIGHT TAVERN SLOT - INCORRECT BEHAVIOR 3: Does not generate a new hero at the beginning of every week

(Of course, many of the above can be tightly related)

Steps To Reproduce

Additional Information

This report was created after more detailed investigation on the bug reported on the forum by Boulie as 0.73c#35: http://forum.vcmi.eu/viewtopic.php?p=3673#3673 [^] - "Bug with heroes in tavern... In tavern on the right there is Sir.Mullich and if you buy only heroes from the left side there are all the time elementalist and planeswalkers. Isn't it correctly implemented? I didn't noticed that before."

As Boulie mentioned on the forum, I don't think we had any of these issues before (during 0.72/0.73).