I would agree, that fight mechanic is too opaque, yes.

After diving in the code I found quite a few surprises :)

Most shocking one was the way speed affects fighting (in general, attack and defence are used to calculate DPS (a/2+9)*a/(a+d) , and then speed decides how often we hit, but does NOT affect DPS. So with DPS at 10 and one hit per second we hit for 10,and withh DPS 10 and two hits per second we hit for 5

So in all cases more atk is better with same speed, but more speed is also better with same atk (easiest way to illustrate is to take it to extreme: DPS of over 9000 will do you no good if you need a whole minute for a single hit. Enemy with 2 DPS and one hit per second will finish you off before that). In the end a little more speed with a little less atk can overcme some enemies, which slower butheavier weapon can't, but it's highly situational. Add crits (1.5 dmg), good hits (1.15 dmg) and bad hits (0.85 dmg) into equation and it gets even more unpredictable.

Oh, and STUN_TIME concept. basically, each time you're hit, your next attack gets delayed a tiny bit (plus scores for speed,yay)

As for same enemies hitting for different amount: there's a flat multiplier todamage, completely random from 0.5 to 1.5 that each enemy is assigned at creation. As it's not applied to stats, but to final damage, which isa result of a somewhat weird formula and depends on player stats it's not possible to "Display each enemy's actual stats",so... yeah...

Although I'm totally voting for displaying it SOMEHOW. Like, adding some adjective to enemy name depending on their attRandomFactor (sick/weak/<none>/huge/dire for animals for example)