Jump to content

gchpaco

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

13 Good
  1. You aimed Sands at two guys. The first one you missed. Because 95% chance to hit, the streakbreaker forced a hit on the second guy.
  2. I can't speak for KiTTY or Keen here, who have much larger peaks than I observe that I cannot explain. But for me, that may be part of it. I'm seeing lines like this for Conductive Aura (from elec control) 2020-05-10 02:19:56 MISSED Centurion!! Your Conductive Aura power had a 53.69% chance to hit, you rolled a 97.52. 2020-05-10 02:19:57 You hit Centurion with your Conductive Aura for 20.51 points of their endurance. 2020-05-10 22:58:25 You hit Centurion with your Conductive Aura for 72.61 points of their endurance. 2020-05-10 22:58:25 You hit Centurion with your Conductive Aura for 72.61 points of their endurance. 2020-05-10 22:58:25 You hit Immunes Surgeon with your Conductive Aura for 51.92 points of their endurance. For Lightning Field on an elec/elec blaster: 2020-05-11 01:22:00 You hit Conscript with your Lightning Field for 2.94 points of their endurance. 2020-05-11 01:22:01 Lightning Field missed! 2020-05-11 01:22:01 MISSED Guardian!! Your Lightning Field power had a 95.00% chance to hit, you rolled a 99.98. 2020-05-11 01:22:02 You hit Conscript with your Lightning Field for 26.59 points of Energy damage. 2020-05-11 01:22:02 You hit Conscript with your Lightning Field for 2.94 points of their endurance. 2020-05-11 01:22:10 You hit Conscript with your Lightning Field for 25.32 points of Energy damage. 2020-05-11 01:22:10 You hit Conscript with your Lightning Field for 2.94 points of their endurance. 2020-05-11 01:22:12 You hit Conscript with your Lightning Field for 25.66 points of Energy damage. 2020-05-11 01:22:12 You hit Conscript with your Lightning Field for 2.94 points of their endurance. 2020-05-11 01:22:14 You hit Conscript with your Lightning Field for 25.66 points of Energy damage. 2020-05-11 01:22:14 You hit Conscript with your Lightning Field for 2.94 points of their endurance. 2020-05-11 01:22:17 Lightning Field missed! 2020-05-11 01:22:17 MISSED Conscript!! Your Lightning Field power had a 95.00% chance to hit, you rolled a 99.57. 2020-05-11 01:22:30 You hit Conscript with your Lightning Field for 31.18 points of Energy damage. Aside: there's definitely something weird going on there, but it does seem to report both hits and misses, but only chance rolls on misses. That may be a manifestation of the problem. So we need to filter out aura powers.
  3. Streakbreaker lines show in the log as lines like 2020-05-10 02:17:17 HIT Centurion! Your Ball Lightning power was forced to hit by streakbreaker. which doesn't cause an RNG value to be selected and so isn't picked out.
  4. Keen notes that this command worked better for him for export to a Google spreadsheet. grep 'rolled a ' chatlog\ 20* | sed -E 's/.*rolled a ([0-9]+[.][0-9]*).*/\1/' | awk -F. '{ print $1 }' | sort | uniq -c | awk '{print $2 "," $1 }'
  5. So some discussion concerning the CoX RNG had me dig out my chat logs and look for everything that was "rolled a" and check the RNG seeding. With 208,000 samples (as I didn't consistently log chat), I saw the attached results, when every number's decimal portion is truncated (so 19.2 -> 19, 0.02 -> 0, and 100.0 which happens sometimes -> 100; that's why the 100 bucket is so odd). There appears to be a subtle but definitely present bias in the City RNG toward high values. The graph of the 1% buckets: And I've attached the excel worksheet with my data. I generated it with grep 'rolled a ' chatlog\ 20* | sed -E 's/.*rolled a ([0-9]+[.][0-9]*).*/\1/' | awk -F. '{ print $1 }' | sort | uniq -c But this isn't especially difficult to do and I expect any similar piece of code would suffice. RNG.xlsx
  6. FWIW I have a dominator that I went permadom on, and I agree that there was a huge gulf between having it and not having it. It made the dominator really awkward to play before I got it, and it's the only hard binary like that in the game at present. Your suggestion is acceptable to me; the thing about permadom is it also fixes end issues on dominators and is their mez protection, so not having it is awkward as hell.
  7. One map location we've wanted that isn't in AE is the Crossroads of Destiny, that Oranbega in the Sky map in Scirocco's second arc.
  8. So disclaimer: this has been on my defender, who's elec/elec. I've been enjoying the set a lot! But there's a few points worth noting. the chain based buffs are awesome but are also extremely loud and tend to smother other audio; in large teams this can result in basically the entire sound channel being taken up by zapzapzap sounds. This is maybe a bit overwhelming, and could stand to be muted a little in volume. I think this might be the first time a set like this has existed in City, which may account for why it's so loud--the engine simply hasn't seen this sort of thing used before. the galvanic sentinel is a bit underwhelming as a pet, but that's fine; it's there mostly as a soloing tool. I'd like it if we could summon it for more or less indefinite lengths, like controller pets, though. As it stands I'm usually so busy I forget to resummon it. (the same is true for voltaic sentinel in elec blast, and is much more acute there) Faraday Cage is really, really good, which is fine; did you intend it to be possible to summon it while mezzed? the animations have been discussed elsewhere as being traumatizing for some folks. The Kinetics buff animations have been noted as being better for this.
  9. I'm using a 2016 15" MacBook Pro. I got Island Rum to download CoH successfully (it doesn't handle paths with spaces in the name well, evidently, but I did get it to work by using a different path with no spaces, which I continue to use) but now when I try to start City, I get the blue LOADING... in the center of the screen, and then I get a full screen version of it in some incredibly gross resolution, like 640x480 or something, and it just hangs. Command+Tabbing out I get to a Wine error screen saying Show Details revealed it to be an illegal instruction exception with a fairly consistent offset; always at 0x93819b18 for me. I did run it through TestRun through the Wineskin app bundled, and got the following logs, which are attached. I've tried both with `-fullscreen 0` and without at the suggestion of a friend, and am pretty much at my wits end. Backtrace.txt is the Wine backtrace. LastRunWine.log LastRunX11.log backtrace.txt
×
×
  • Create New...