| Summary: | Engine configuration is unimplemented | ||
|---|---|---|---|
| Product: | [Applications] knights | Reporter: | a |
| Component: | general | Assignee: | Alexander Semke <alexander.semke> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | kde-games-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 2.6.240780 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
a
2024-10-07 14:23:52 UTC
(In reply to a from comment #0) > Almost all chess engines nowadays come with various options to configure > them, from being able to use more cores, using more memory or less memory. > > It would be nice to be able to be able to configure these options, as I > believe KNights currently runs all engines on default settings I planned to implement as next the support for uci_limitstrength and uci_elo parameters to better control the strength of UCI engines. Do we really need to expose such technical and internal things like the number of threads, etc. via some engine specific settings (there are hundreds of engines out there...) or is it enough just to limit the strength of the engine in a common way as defined by the protocol? |