Jump to content


  • Content Сount

  • Joined

  • Last visited

  • Battles

  • Clan


Community Reputation

10 Neutral

About JAKeller

  • Rank
    Petty Officer
  • Insignia

Profile Information

  • Location
    Virgo Supercluster

Recent Profile Visitors

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

  1. JAKeller

    Update Hotfix - UPDATED (11/2)

    WG, this started yesterday after the server version was updated, so is related the hotfix (though not the CVs). Friday, I had to fight 3 battles with Tier V+ ships before the Daily Challenge began accruing. This morning I fought 5 battles (even collected a 2000 XP container) before anything began accruing. On both occasions, the pattern was the same: the port displayed the reward for the previous day's Daily Challenge 1 and refused to stop displaying it for what appeared to be a random period of time; only then did the reward display disappear and the current day's Daily Challenge taking its place as the 'active' challenge. This appears to be a data error in tracking the transactional status of players in-game. I know that whenever I manage to recover from a CTD (if the crash occurred during a battle), I cannot change or collect anything. I receive a Transaction Error from the server. Please look into this. It's not worth playing a game if no rewards are provided when one is following the rules.
  2. JAKeller

    Update Hotfix - UPDATED (11/2)

    WG - please, Please, PLEASE, PLEASE, PLEASE???!!! Do something about the lockups and freezes for the Mac wrapper. I know CodeWeavers is supposedly working on a 64bit wrapper that will likely solve the problem, but could someone please get them to get it done?! I am sick and tired of losing ships (and the XP and Credits that go with them) because the client freezes in mid-battle (usually with me having taken zero damage), then finding myself dead after attempting to get back in finally after 2-3 tries (comprising typically anywhere from 2.5 to 6 minutes - a virtual eternity for a ship in a battle to be AFK - a derisively disgusting term that doesn't consider that maybe the player was disconnected or locked out instead). I haven't kept careful track of how many ships I've lost this way, but it's in the neighborhood of 30-40 now. That's something between 600k-1000k damage points (minimally) with all the subsequent XP that entails. I don't want to say I deserve to get back all that potential XP and credits, because it's just potential, but to be honest, I and every Mac user in this game who suffers similarly does indeed actually deserve something back. (even if it's in-game currency or XP) It's not hard to perform a simple client health check not only at the beginning of a battle but during (and even when the port loads; that's not always successful either you know). (the bandwidth requirements are minimal; you eat up more bandwidth continuously reporting ship status back and forth between the client and server) Why the continual 'Happy Path' design and coding? I would have fired any of my developers long ago for not following good procedures in their development. This includes process design as well as unit, integration, and recursion testing.
  3. JAKeller

    Update Hotfix - UPDATED (11/2)

    There's an old joke among software architects that the history of software design has been a contest between software designers trying to design better idiot-proof software and the Universe trying to design a better idiot, and so far the Universe is winning. Frankly, WG would be better off just designing something that works. The players will adjust. Constantly trying to 'dumb down' gameplay to bring in newer players with shorter attention spans will only result in short term retention of those newer players who will only stay around only so long unless they get another 'fix'. (to which many of us would affix the phrase 'shiny-shiny') Yes - sadly there are companies which cater to the idea that they're okay with only getting (and not retaining) players, so long as the new players outnumber the ones leaving. The problem is that eventually, you run out of suckers and the new-player influx falls off too.
  4. JAKeller

    Update Hotfix - UPDATED (11/2)

    Stop with the automatic switches to the Dragon port. It breaks and locks the game constantly, and if you're automatically (and I might add without even asking if I WANT the blasted Dragon port) setting my port, it's only going to add to the anger level players have for the game. WE should be allowed to set what port we want - not WG! I've been futzing with the game for a while now just to get it to start this morning, because WG set my port to the Dragon port. Stop it!! Go to your rooms and learn to respect your players.
  5. Not giving you a hard time, Ryan. (or at least that wasn't my intent, and I apologize if my post was interpreted that way) The game files are stored separately from the wrapper. The uninstaller removes all the files: those for the wrapper (the 'application' in the Applications folder), and the files from the game itself (which oddly enough will run as is in a Windows environment). All we really needed to be removed were the wrapper files. A similar result can be obtained by deleting the wrapper (i.e. the launcher) from the Applications folder. When you download the 'game' from the WG site, you get just the wrapper, which downloads the game files if they don't exist (/Users/<username>/Library/Application Support/World of Warships/Bottles/worldofwarships/drive_c/Games/World_of_Warships/) A word of caution, however - I installed the Wargaming Game Center (WGC). That application imports all WG games into it for management and won't let go. I cannot say for certain if the wrapper it running is 2.0.29 or 2.0.28. I've not yet located the configuration file for WGC (as I'm certain that's where the list of imported games is - it may even be a keychain file someplace since the application stores our login credentials as well). Once I do (or if someone else finds it) I'll post here.
  6. Do NOT use this. It will destroy ALL (I repeat ALL) existing game files, forcing you to d/l the entire game again. (20+Gb) Thank you - I now have to d/l files for nearly a day again just to play.
  7. JAKeller

    Update 0.8.0 - Feedback and General Performance

    I had to edit that later. I had meant to say why WEREN'T they tested? We need play-balance in the mid-tiers as well. Even as it is in Coop (with bots getting top tier BBs instead of CVs), the only way your side wins is if you all work together (which isn't a bad thing tbh), sadly demonstrating that at least for the mid-tiers, CVs don't do so well and certainly don't carry their weight in offsetting BBs.
  8. JAKeller

    Update 0.8.0 - Feedback and General Performance

    To be honest, they need to have more layered events. Events for low, mid, and high tiers. I realize that's more work and more planning, but it would make the game more enjoyable for those who either haven't yet gotten or have only 1 or 2 Tier V or higher ships. It would make grinding up a little less tedious. I prefer not using Premium ships, as why grind in them if you can't evolve up from them, especially given how lame most rewards seem to be. (c'mon - you grind out a Daily Challenge to get - 3 signal flags? Ouch)
  9. JAKeller

    Update 0.8.0 - Feedback and General Performance

    Hey, why weren't the mid-tiers tested? It would appear that all (any?) testing that took place did so at Tier X. That's hardly representative of the player base.
  10. JAKeller

    [0.8.0] First CV rework tweaks and changes

    Given how much more dodging DDs (and to a slightly lesser extent CL/CAs) we're going to be seeing with this patch, we should get XP for potential damage (including potential torp damage). That would provide some incentive for dodging, and still manage rewards even for people who spend an entire match just trying not to be deleted.
  11. JAKeller

    Update 0.8.0 - Feedback and General Performance

    One thing I've noticed is WG seems to take a very 'Happy Path' attitude towards testing, development, and announcements. Given that testing is my obsession, I would fire anyone not fully invested in what is called in architecture as pessimistic testing. (i.e. assuming the worse case and design and test around it)
  12. JAKeller

    Update 0.8.0 - Feedback and General Performance

    Unless you're on a Mac. WG has stated repeatedly that Macs have no official (i.e. actual) technical support. All tickets will be closed with that statement, and we are referred to a forum link where we can share, complain at one another, and try to figure out why our games crash/hang so often. We've concluded that the wrapper is 32bit and MacOS went to 64bit a decade ago with increasing intolerance toward 32bit applications, but WG doesn't really listen to us other than to say they've referred the problem (3 years ago) to the company building and managing the wrapper. Now that the rest of the community are finally suffering from the same problems we've been experiencing for a long time, we'll finally get some love too.
  13. JAKeller

    Update 0.8.0 - Feedback and General Performance

    Personally, I find it supremely humorous that now that the rest of you are experiencing the same issues as we Mac users have been seeing for years (with the rest of you saying "get a better computer" or "you should've bought a PC"), suddenly it's a big deal. It always was one. Perhaps now it will be fixed. The internal discussion (the only one we get; WG doesn't provide us with technical support ) in the Mac community is the problem is related to WoWs still being a 32bit application in a 64bit world. MacOS moved on to 64bit a decade ago and have been increasingly intolerant of 32bit. We were just likely the proverbial canary in the coal mine. Now maybe WG will have to update WoWs.
  14. JAKeller

    Update 0.8.0 - Feedback and General Performance

    Sadly, this is the kind of thing Mac users have had to deal with for nearly 3 years now. Welcome to our world.
  15. JAKeller

    Update 0.8.0 - Feedback and General Performance

    You should check the IJN tree from the Isokaze. There are 3 branches stemming from it. I'll have to eventually grind a total of 33,500 XP to complete all the branches from that single ship. Macs have a different problem with this release. We can barely play at all. There are times when you have to try 4-5 times just to get to the port. And we still have the issue where the client either crashes or hangs every couple of matches starting at Tier V and up (getting worse as you go upwards), so imagine how fun it becomes when you hang in battle and have to force quit, restart and hope you don't crash again (don't forget to sacrifice a couple of chickens while you're doing it). This isn't a game any longer. It's become a Self Interactive Technical Session because most of the time it just SITS there.