Search results

  1. lighthouse64

    Proposal Addressing Smogon's 10+ Year old Usage Stat Problems

    TL;DR -- Here's what's wrong The tiering cutoff definition allows for a pokemon to be both truly OU and not designated OU because the percentage cutoff is based off unweighted usage stats, but percentages themselves are calculated using weighted stats (i.e. the cutoff calculation method is...
  2. lighthouse64

    Gen 4's HP Bar Speed is Very Competitively Relevant

    Posting this in Ruins of Alph because I don’t have permissions for Policy Review and would also like the ability to get responses. TL;DR The gen 4 blissey meme is competitively relevant, but Pokemon Showdown does nothing to handle it. Watch my video to learn why. For those of you who don’t...
  3. lighthouse64

    Chinchow Battle Analyzer - A comprehensive replay analyzer and reverse stat calculator

    Hey there! If you have seen me on the forums, you've probably seen my bug posts or related comments. All of those came from when I was working on this: A comprehensive library that is able to parse, logically, analyze, and reverse stat calculate replay logs to allow for better battle analysis...
  4. lighthouse64

    Rejected - Inactive Improve the way HP denominators are handled by the client

    As it currently stands, the client is hardcoded to give out certain info when an hp denominator is 48 or 100. For 48, it will act like the hp taken is from a vgc match, and for 100, it will act like the hp comes from a standard showdown game with the HP Percent mod. While this is normally not...
  5. lighthouse64

    Approved Future Sight Should not indicate its target when initially being used

    I am using the following replay for reference: https://replay.pokemonshowdown.com/gen8doublesou-1266352148.log While tinkering around with future sigh in double battles with pokemon showdown, I noticed that future sight publicly indicates the position that it will hit when being activated...
Top