# LPH vs UNiTY: the remade-map rule behind an open June contract The old scheduled date has passed. The remaining contract concerns a specific map statistic and its exceptions. Canonical article: https://www.homeincomelab.com/stories/cs2-lph-unity-2026-06-02 Publisher: The Outlook By: The Outlook editorial desk Category: Sports Analysis as of: 2026-10-04T10:30:51.735578Z Decision guide market prices observed: 2026-10-04T09:57:48.323Z Published: 2026-10-04T10:30:51.735578Z ## Quick answer The Counter-Strike: LPH Gaming vs UNiTY esports (BO3) fixture was dated June 2, 2026. An eligible Map 1 odd/even kills contract remains open in the October 4 data at 50% on each side. This is an outstanding-settlement explainer, not a preview of a future match. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) ## Key takeaways - For this Map 1 kill-parity proposition, a remade game replaces the abandoned version for settlement. Combining both versions would produce the wrong count even if the arithmetic itself were correct. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) - Odd is supported only if the recognised combined kill count for Map 1 is an odd integer. For example, a hypothetical total of 101 would be odd and 102 would be even; these are illustrations, not reported match statistics. - A round score, winning team or combined deaths figure cannot safely substitute for the required count. Friendly-fire kills and self-inflicted deaths are excluded, while qualifying overtime kills are included. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) ## An old fixture with an open statistical contract The Counter-Strike: LPH Gaming vs UNiTY esports (BO3) fixture was dated June 2, 2026. An eligible Map 1 odd/even kills contract remains open in the October 4 data at 50% on each side. This is an outstanding-settlement explainer, not a preview of a future match. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) For the exact contract “Map 1: Odd/Even Total Kills?”, our October 4 observation was Odd 50%; Even 50%. These are recorded contract prices, not an official result. The parent event’s cumulative volume was $102,001; that turnover includes other constituent contracts and is not the volume of this selection alone. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) ## The detail that changes the question For this Map 1 kill-parity proposition, a remade game replaces the abandoned version for settlement. Combining both versions would produce the wrong count even if the arithmetic itself were correct. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) ## What would strengthen or weaken the case Odd is supported only if the recognised combined kill count for Map 1 is an odd integer. For example, a hypothetical total of 101 would be odd and 102 would be even; these are illustrations, not reported match statistics. A round score, winning team or combined deaths figure cannot safely substitute for the required count. Friendly-fire kills and self-inflicted deaths are excluded, while qualifying overtime kills are included. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) ## The evidence that will settle it The contract counts both teams’ qualifying kills in Map 1, including overtime, then settles Odd or Even. If the map is remade, only the remade game counts. The designated record is HLTV; credible reporting can be used if it has no final result within two hours. [3](https://polymarket.com/event/cs2-lph-unity-2026-06-02/cs2-lph-unity-2026-06-02-game1-odd-even-total-kills) The seven-day postponement window from June 2 reaches June 9, 2026, which has passed. Cancellation, no kills, an unplayed map or delay beyond that window produces 50–50 under the rules. No settlement cause is inferred from the open API status. [3](https://polymarket.com/event/cs2-lph-unity-2026-06-02/cs2-lph-unity-2026-06-02-game1-odd-even-total-kills) ## A fact worth knowing Counter-Strike 2 is built on Valve’s Source 2 engine. Source: [Valve: Counter-Strike 2 official game description](https://store.steampowered.com/app/730/CounterStrike_2/?CC=US&l=english) ## Weighing the outcome ### Outcome in focus Map 1: Odd total kills ### Supporting case Odd is supported only if the recognised combined kill count for Map 1 is an odd integer. For example, a hypothetical total of 101 would be odd and 102 would be even; these are illustrations, not reported match statistics. ### Challenging case A round score, winning team or combined deaths figure cannot safely substitute for the required count. Friendly-fire kills and self-inflicted deaths are excluded, while qualifying overtime kills are included. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) ### What to watch - The exact Map 1 historical kill record. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) - Whether the map was remade, cancelled or never played. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) - The platform’s recorded resolution and any stated explanation. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) ### What may already be priced in The Odd side of “Map 1: Odd/Even Total Kills?” was 50% in the October 4 snapshot. That price belongs to this exact question; it should not be transferred to a different line, period or match-winner proposition. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) ### Assessment For this Map 1 kill-parity proposition, a remade game replaces the abandoned version for settlement. Combining both versions would produce the wrong count even if the arithmetic itself were correct. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) ## How the market resolves The contract counts both teams’ qualifying kills in Map 1, including overtime, then settles Odd or Even. If the map is remade, only the remade game counts. The designated record is HLTV; credible reporting can be used if it has no final result within two hours. [3](https://polymarket.com/event/cs2-lph-unity-2026-06-02/cs2-lph-unity-2026-06-02-game1-odd-even-total-kills) ## Timing and deadline The seven-day postponement window from June 2 reaches June 9, 2026, which has passed. Cancellation, no kills, an unplayed map or delay beyond that window produces 50–50 under the rules. No settlement cause is inferred from the open API status. [3](https://polymarket.com/event/cs2-lph-unity-2026-06-02/cs2-lph-unity-2026-06-02-game1-odd-even-total-kills) ## Questions and answers ### Does 50% mean this old match is still about to happen? No. It is an observed contract quote; the original fixture date has passed. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) ### Do team kills count in this market? No. Friendly-fire kills and self-inflicted deaths are excluded by the contract. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) ### What if the map was remade? Only the remade version supplies the settlement count. [1](https://polymarket.com/event/cs2-lph-unity-2026-06-02) ## Related market contracts - [Odd/Even Total Kills](https://polymarket.com/event/cs2-lph-unity-2026-06-02/cs2-lph-unity-2026-06-02-game1-odd-even-total-kills) ## Market source [View the event on Polymarket](https://polymarket.com/event/cs2-lph-unity-2026-06-02) For timestamped market prices, see the canonical HTML article. Prices can change independently of this analysis. ## Sources and further reading 1. [Polymarket: Counter-Strike: LPH Gaming vs UNiTY esports (BO3) - United21 Group B](https://polymarket.com/event/cs2-lph-unity-2026-06-02) 2. [Valve: Counter-Strike 2 official game description](https://store.steampowered.com/app/730/CounterStrike_2/?CC=US&l=english) 3. [Exact Polymarket contract: Odd/Even Total Kills](https://polymarket.com/event/cs2-lph-unity-2026-06-02/cs2-lph-unity-2026-06-02-game1-odd-even-total-kills) This is AI-assisted, source-linked explanatory journalism. We distinguish facts from interpretation and revise material errors. [How we work](https://www.homeincomelab.com/methodology) · [Corrections and contact](https://www.homeincomelab.com/contact)