#72 The calculations for finding possible hexes to move to in battle do not seem to take into account the nature of 2-hex creatures. In the picture below, the Silver Pegasi should not be able to move in front of the Arch Devils.
EDIT: Maybe this is the same as #08? In any case, it should hold for all 2-hex creatures.
No, the server will send a message that the unit cannot be moved there. I could attach a map but the problem is easily reproducible, just create an army like in the picture and attack a group of Arch Devils and they will start out by going for the Grand Elves just like in the picture every time.
I think it’s not a problem with not recognizing that creature is two hex wide but a problem with not blocking side colums of hexes when it should be done. I think it’s not hard to fix.
#73 Crash at the start of the battle - I’m nearly sure that I (or somebody) has reported this crash but I couldn’t find it. I don’t know if it shouldn’t be fixed. If it is new, please assign the next number.
I gave it a log number because with crashes you never know: even if it looks similar, it might have a different cause. Plus the fact that the previous reports were not kept in the logs, could mean that the devs made already some changes which should have prevented it to reoccur.
Anyway, just in case it’s related and previous descriptions are helping, here are the other reports:
Zamolxis, good job
How was it possible that I didn’t find this crashes neither yours nor mine ?
I thought it was caused by smpeg.dll, so replacement of this file didn’t help or there are also some other reasons.
Ok, I finally managed to attack recently implemented Creature Bank.
There is a whole lot of bugs:
-Creatures are random type and quantity, at least compared to Crypt config - but it can be my fault as well.
-Griffins can’t reach certain areas.
-Unicorns are placed incorrectly.
-Defenders’ formation is not as it was supposed to be.
-Round begins two times.
A big feature, positions of all obstacles need to be individually arranged. I think I could prepare a config and let somebody do that.
fixed
duplicate to all two-hex creatures problems
implemented
elementals are fixed, nomads will be fixed soon (it can be fixed even without recompiling VCMI as all creatures’ abilities info is stored in cr_abils file)
You mean estimation of damage that will be dealt during attack? If yes, it’s done for creatures (spells need soem further changes).
It’s fixed now ;). But the issues with spell immunities aren’t over, in the original H3 creatures with immunities weren’t 100% resistant. They couldn’t be targeted and with mass spells they were simply ignored. Personally though, I think it looks prettier with the resistance effect.
Also there should be a message when all creatures that could be affected by a spell are immune to it.
Not exactly (perhaps “calculation” was the wrong word used). The estimations are actually a feature that I understand it may take some time to implement.
But before estimations, I believe it’s easier and more useful to implement the known values of the inflicted damage (post-strike), or of the to-be-inflicted damage for spells.
More exactly, for battle logs I was referring to the info displayed at the bottom after the creature has been hit (by another or by spell), giving info about both the Health damage as well as number of creatures perished:
These would make it easier for testers to compare the VCMI damage with the H3 one, to check if the formulas seem correct (for example it would have helped us to easier spot that bug we’ve had with spell damage tripled - instead of just vaguely reporting “spell damage seems too high”)
Actually damage really inflicted by creatures are displayed in the console (you have to scroll up to see it). Furthermore, I’ve already implemented calculation of expected damage (although it does not take into account some creature abilities like champion’s charge). I’ll try to implement the same for spells (inflicted and estimated damage).
I’m almost sure that current formula of damage calculation is not the same as in Hereos 3, I’m going to reorganize it.
It’d be great, but it won’t be as easy as puzzle map or walls. I’ll add new entry in obstacles’ config for shift in position and increase the amount of obstacles in the battlefield but you’d have to run many battles using VCMI, recognize which obstacles are present (there is a list of all of them in documentation of ERM) and put in the config how much to the left / right / top / bottom the obstacle should be moved. Some other information in the config may also be wrong such as terrains the obstacle may be placed on. I’ll talk about it with Tow and post more details.
AFAIK this is already present. In obstacles.txt we already have:
[id] [Def name] [blockmap] [allowed terrains]
This info looks to be correct. But I’ll check it as well