Jump to content


Community Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

20 Excellent

1 Follower

About Dunedan

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just to clear things up: plautus' rules for this game were: no bolts, no catapults and no slingers. There was no rule about not entering the opponents base or something like that. That's again one of the cases where including the ingame chat log in the replay would be beneficial, as I proposed a while ago: https://trac.wildfiregames.com/ticket/5070
  2. I joined one of plautus rated 1vs1 deathmatch games. All settings, including my civ, were his choices. Nevertheless he quit the game as soon as he recognized that he's going to loose. @user1 @Hannibal_Barca commands.txt metadata.json
  3. Look at the victory condition messages at the top. First line glitches away if there are too many of them. @s0600204 maybe?
  4. Roman spear cav shows sword animation when hunting.
  5. > The clients might send any kind of garbage and we get JSON errors repeated. Usually we solve this problem by removing the broken game, but it's probably better to add conditions all over the place in the long run. Clients should never show such errors in case they receive garbage in my opinion, as that's a sign of insufficient input validation (input as in data received) which can also be an wide open door for vulnerabilities, especially as it's input received via network. And we already had such a problem at least once. So I'm definitely in favor of adding proper input validation.
  6. Tried some stuff with mixed a22 and a23 code/lobby. Seems like it basically works properly. So opening a22 lobby in a23 shows all games greyed out as it would do for incompatible mods as well I guess. There are some small bugs though. While the mixed a22/a23 case isn't relevant I guess they are valid when listing mods as well: Selecting a running a22-game in an a23-lobby causes the following error message to be shown: WARNING: JavaScript warning: gui/common/gamedescription.js line 466 reference to undefined property playerData.AIBehavior Trying to join a a22-game in an a23-lobby c
  7. Found a little graphics glitch. Notice how the text isn't properly rendered.
  8. Awesome. Same as the dimension of the picture, so 1278x1368. That's half of my screen in width and the full height of my screen minus status bar and window decoration. That's the setup I usually use in gamesetup before I switch to full screen when the game starts.
  9. I just wanted to make a little thread with some small bugs, glitches and annoyances which are currently present in SVN and thus likely relevant for A23. Let's start with two issues: in gamesetup when the window is higher than wide, the settings take too much space, thus leaving to little space for the chat (see attached screenshot) the "Babylonian Scythed Chariot" the persians have available got a new "walking" sound (maybe other units as well). While that sounds fine for single units it sounds horrible if there are more than a dozen units walking at once.
  10. And another one: Slawek_PL commands.txt metadata.json
  11. As Medranozzz was in the lobby crying about having a too high rating, so he needs another account: Maybe he shouldn't quit rated games. Turns out my history of replays contained one. commands.txt metadata.json
  12. And another rated game quitter: Nacres commands.txt metadata.json
  13. And we have another rated game quitter: bigshot Looked like somebody with a equivalent score to me, but further inspection afterwards revealed that he has a suspiciously high win rate. Funny though the settings he chose for the game and how he played it. @Hannibal_Barca @user1 commands.txt metadata.json
  • Create New...