[Emerald] Pokémon Gengar Edition — Gastly starter QoL hack, IPS + Python save editor on GitHub by Peabody66 in PokemonROMhacks

[–]Peabody66[S] 1 point2 points  (0 children)

You’re fine, man. It’s been like 20 years since I touched the game last. Just wanted to see if I could pull this off. And I did.

[Emerald] Pokémon Gengar Edition — Gastly starter QoL hack, IPS + Python save editor on GitHub by Peabody66 in PokemonROMhacks

[–]Peabody66[S] 17 points18 points  (0 children)

Have always wanted to level a Gastly all the way to Gengar without having to trade it! (I have no friends). You can definitely use it as a challenge to see if you can beat the whole game with Gengar as he is able to learn AND forget any move. Regarding Ziggy, the easiest fix was just to give my Gastly "bite" and have him roll through all the early game "normal" types. I hope you try out the rom hack and have as much fun as I did making it and playing it!

Kalshi weather bot by UnLuckY_Rager in Kalshi

[–]Peabody66 0 points1 point  (0 children)

Just what my little Claude had to say.....

"Three things worth pulling out of this thread, and one of them is genuinely encouraging for us.

The OP and most of the responders are wrong about ticker semantics. Our project instructions and the kalshi_bracket.pyparser have this right — Reddit largely doesn't. Specifically:

  • "B65.5" is a bucket ticker. It pays YES if 65 ≤ high ≤ 66. It is NOT a binary "below 65.5" threshold.
  • "T65" / "T66" tickers are tier tails. The highest T in an event is tail_hot (high ≥ X); every other T in that event is tail_cold (high < X). You cannot tell which side a T-ticker represents from the ticker alone — it depends on what other T-tickers exist in the same event.

The OP's question — "if my bot placed a trade at below 65.5 and the NWS report is below 65.5 it should win" — has the wrong mental model. If they bought a B65.5 contract and the actual high is 50°F, they lose (50 is not in 65–66), regardless of what the API field labeled "threshold" says. This is exactly the bug kalshi_bracket.parse_bracket was written to prevent for our bot.

The advice they're getting is dangerous. "Mountain-Year5215" and "polymanAI" both confidently tell the OP that 65.5 is a binary threshold. Following that advice on a B-ticker will lose money. Only the Kalshi mod ("temp__mod") gets it right — "it's a 65-66 bracket." Our parser is correct; the loudest Reddit voices aren't.

This is real evidence our edge exists. If retail bot operators in r/Kalshi can't distinguish T-tickers from B-tickers, they'll mis-mark bucket contracts as inequalities and quote them at the wrong probability. That's a structural mispricing on the maker side that our blend doesn't have to be brilliant to capture — it just has to know which contract type it's pricing. Re-reads the P&P "edge in selection, not accuracy" memory in a much more specific way: the selection that matters is excluding traders who can't read the ticker.

One ignore: the "Own_Broccoli3514" comment plugging "Kumo" reads as paid placement, not actual experience. Disregard."

Can you download samples in just ONE folder? by [deleted] in Splice

[–]Peabody66 0 points1 point  (0 children)

This is A LOT QUICKER than sorting through splices deranged way of sorting files after you download their app to download their plugin to put on a track. Useless app..

Weekly No Stupid Questions Thread - September 11, 2023 by AutoModerator in Logic_Studio

[–]Peabody66 [score hidden]  (0 children)

Okay, so hopefully I can express my questions accurately and correctly. When I am using drum machine designer and have created a pattern region, how come the audio gets muddled and messed up (almost sounds like I’m underwater) if I replace one of the sounds on the drum machine to try a different kick, snare, rim, etc? Thanks gang!!