This reminds me of the time I had my laptop open on the tilt-down tray and the very large man in the seat in front just repositioned his girth (not even reclining the seat) but it flexed the seat back enough that my laptop screen was momentarily caught between the tray below and recessed lip above and was almost crushed.
- the internet connection is excellent (even in most tunnels) so you can work, have video meetings, etc, not to mention play chess online
It's one of those old programs where 95% of the moves are pretty strong. But if you just do nothing and sit back it will occasionally make a random blunder and then you grind it out. I figured it's how they were able to weaken a chess engine back in the day; can't adjust the overall strength, so add random blunders.
I'm only about 2000 on lichess but I beat it pretty much every time, especially once I realized there is no reason to try anything sharp.
As a result, if you tried this on older planes, it might have been “easier”
When the iPhone 5S came out, I tried it on a whim to check the UI scaling etc... the beginner difficulty on a 9x9 board deleted me. It was grabbing something like 64x more samples per go, the lowest difficulty on the 5S (instant responses) never lost a single game vs the highest difficulty 3GS (15 second turns)
iPhones had a lot of moments like that. Silly bullshit like "what if every pixel was a cell in a collection view" would go from "oh it can barely do 128" to "more responsive than that was, with 2 million" in a few gens.
I was maintainer of the Chess app from the early 2000s to about 2015. We first noticed in 2004 that level 1 (which was then "Computer thinks for 1 second per move) was getting stronger with each hardware generation (and in fact stronger than myself).
So we introduced 3 new levels, with the Computer thinking 1, 2, or 3 moves ahead. This solved the problem of the engine getting stronger (though the jump from "3 moves ahead" to "1 second" got worse and worse).
A few years after I had handed off the project, somebody decided to meddle with the level setting code (I was not privy to that decision). The time based levels were entirely replaced with depth based levels (which eliminates the strength inflation problem, but unfortunately was not accompanied by UI changes). But for some reason, parsing of the depth setting was broken as well, so the engine now always plays at depth 40 (stronger than ever).
This should be an easy fix, if Apple gets around to make it (Chess was always a side project for the maintainers). I filed feedback report 21609379.
It seems that somebody else had already discovered this and fixed it in a fork of the open source project: https://github.com/aglee/Chess/commit/dfb16b3f32e5a6633d2119...
Unfortunately they never released a remastered version of it. They seem to have made some clone of it called “reforged” whatever the fuck that means.
There is a thriving community with a couple different choices for servers to play on. So I'm sure there's a fix for your mouse speed issue.
Check Twitch for people streaming it: https://www.twitch.tv/directory/category/warcraft-iii
Grubby, one of the early esports stars, still streams it regularly and hosts his own for fun tournaments with other streamers.
You probably knew this, but wanted to make sure others knew that the reason they ended the franchise is not because there was no market, but instead it was pure unadulterated greed that led to that situation. In an alternate reality they would have actually done the remake justice and there would be a lively competitive scene
> SOLAR_FIELDS
Panoramic Greetings!
The Dolphin emulator has run into similar things; usually doing things "too fast" just gets you more FPS but sometimes it causes the game to go insane.
I suppose, technically, that's one way to make the Scimitar feel more responsive...
It would also be of limited use, as the engine is purely CPU based; it is single threaded and does not even use SIMD AFAIK, let alone GPU features or the neural engines.
In tom7’s Elo World, he does this (“dilutes” strong Chess AIs with a certain percentage of random moves) to smooth the gradient since otherwise it would be impossible to evaluate his terrible chess bots against something like Stockfish since they’d just lose every time. https://youtu.be/DpXy041BIlA?si=z7g1a_TX_QoPYN9b
That puts you in the top 7% of players on the site. I have a hard time believing you could get to that rating without knowing that.
2. I played a chess bot on Delta on easy and it was really bad, felt like random moves. I beat it trivially and I am actually bad at chess, ~1000 on chess.com. I wonder if this one is different?
The way you set difficulty for turn based game ai is that you limit how far ahead the algorithm searches. If you set the lookahead based on compute time your difficulties will be way out of line if someone upgrades the CPU.
When Big Sur rolled out around 2020, Apple introduced a bug which disabled the difficulty slider: no matter what it was set to, it was hard or impossible to beat. In macOS Sequoia, the Chess app got updated again, and supposedly they fixed the difficulty slider, but in the interval silicon improved so much that the old restraints (like think for only a second) mean little. The lowest levels play like a grand master.
or whatever makes sense if “iterations” isn’t a thing, I know nothing about chess algorithms
Limiting the search depth is much more deterministic. At lower levels, it has hilarious results, and is pretty good at emulating beginning players (who know the rules, but have a limited skill of calculating moves ahead).
One problem with fixed search depth is that I think most good engines prefer to use dynamic search depth (where they sense that some positions need to be searched a bit deeper to reach a quiescent point), so they will be handicapped with a fix depth.
The search is by depth of further moves, and “better” is a function of heuristics (explicit or learned) on the resulting board positions, because most of the time you can’t be sure a move will inevitably result in a win or a loss.
So any particular move evaluation might take more or less time before the algorithm gives up on it—or chooses it as the new winner. To throw a consistent amount of compute at each move, the simple thing to do is give the engine consistent amounts of time per move.
Blizzard did a similar thing in World of Warcraft during the beta. After playing for a while, your character would get "exhausted" and start earning half experience for killing mobs. The only way to stop being exhausted would be to log off or spend a LONG time in an inn. At some point, they flipped the script. They made the "exhausted" state the default, and while offline or in an inn, you would gain a "rested" experience buffer, where you would earn double experience.
The mechanic worked exactly the same, but by giving it different terms, players felt rewarded for stepping away from the game occasionally, rather than punished for playing too long. They also marketed it as a way of giving players a way to "catch up" after spending a day or two offline.
Years ago I remember flying with Delta and wondering why the delta bot could beat me in a handful of moves on EASY. Absolutely insane.
https://en.wikipedia.org/wiki/Tzar%3A_The_Burden_of_the_Crow...