| Rev | Author | Branch | Log Message | Date | SHA |
|---|---|---|---|---|---|
| r24093 | 1.7 | Force rebuild |
10 May, 2026 | ||
| r24092 | 1.7 | Force rebuild |
10 May, 2026 | ||
| r24091 | 1.7 | Force rebuild |
10 May, 2026 | ||
| r24090 | 1.7 | Use fail-safe ReadBit overload in join packet parser |
9 May, 2026 | ||
| 1.7 | Addendum to 614638d: Reject backtick in IsNickValid to match server-side CheckNickProvided |
9 May, 2026 | |||
| r24088 | 1.7 | Force rebuild |
9 May, 2026 | ||
| r24087 | 1.7 | Reliability fixes for nickname valid-checks on client and server Fix 1: Backtick validation gap (client) Added strchr(szNick, '') != nullptrcheck to the client's CheckNickProvided, matching the server's version in Shared/Utils.cpp. Previously, a nickname containing a backtick passed all client-side checks, was serialized correctly, and then got rejected server-side with INVALID_NICKNAME. ... |
9 May, 2026 | ||
| r24086 | 1.7 | Force rebuild |
8 May, 2026 | ||
| 1.7 | Filter WER crash dialogs to fail-fast exceptions only CheckForWerCrash picks up any .dmp file in the private dumps folder and shows a "Security Exception" crash dialog on the next launch. The problem is it doesn't check what kind of exception the dump actually contains - so a C++ exception (like a CEGUI texture load failure, 0xE06D7363) that got dumped by WER would show up as a delayed crash dialog on the next MTA launch, even though the game kept running fine as it wasn't a fatal exception at the time it happened. Now it checks the exception code in the dump and skips anything that isn't a real fail-fast (0xC0000409 / 0xC0000374). This stops irrelevant crash dialogs from appearing on the next launch when no actual crash happened. |
8 May, 2026 | |||
| 1.7 | Crash handler polish (#4867) #### Summary Architectural cleanup and hardening of the Crash Handler. ... |
30 April, 2026 | |||
| 1.7 | Crash handler fixes (#4866) #### Summary • Skip `OutputDebugStringA` when no debugger is attached. ... |
30 April, 2026 | |||
| r24082 | 1.7 | Force rebuild |
8 May, 2026 | ||
| r24081 | 1.7 | Force rebuild |
7 May, 2026 | ||
| r24080 | 1.7 | Update README.md Force rebuild |
5 May, 2026 |