Index Search ←Prev date Next date→
Timestamps are in GMT/BST.
| 00:00:52 | BFLogBot Pull request #711 closed by Copilot | Title: Fix xtank heading/speed out-of-sync on observer clients; add sync tests | https://github.com/bitfighter/bitfighter/pull/711 | |
| 00:01:46 | BFLogBot Repo: bitfighter | Commit: fd2aab84eb | Author: eykamp | Message: Fix signature issue | |
| 00:02:14 | BFLogBot Repo: bitfighter | Commit: 6c25b8c8d0 | Author: Copilot | Message: Fix tank heading/speed sync and add TestSync tests Agent-Logs-Url: https://github.com/bitfighter/bitfighter/sessions/3540e28b-5c42-4199-85ef-2852141e746c Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 00:02:19 | BFLogBot Pull request #711 reopened by Copilot | Title: Fix xtank heading/speed out-of-sync on observer clients; add sync tests | https://github.com/bitfighter/bitfighter/pull/711 | |
| 00:02:34 | BFLogBot Repo: bitfighter | Commit: 0edbd11f03 | Author: Copilot | Message: Fix tank heading/speed sync and add TestSync tests (#711) Agent-Logs-Url: https://github.com/bitfighter/bitfighter/sessions/3540e28b-5c42-4199-85ef-2852141e746c Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 00:02:34 | BFLogBot Pull request #711 closed by Copilot | Title: Fix xtank heading/speed out-of-sync on observer clients; add sync tests | https://github.com/bitfighter/bitfighter/pull/711 | |
| 04:51:45 | BFLogBot Repo: bitfighter | Commit: af78413529 | Author: eykamp | Message: Fix build | |
| 04:51:46 | BFLogBot Repo: bitfighter | Commit: 482d4f4ed2 | Author: eykamp | Message: I think we need to check both axes | |
| 04:51:48 | BFLogBot Repo: bitfighter | Commit: ce1e976567 | Author: eykamp | Message: Prevent crash, mostly an issue during testing | |
| 04:51:49 | BFLogBot Repo: bitfighter | Commit: 7b15bdb548 | Author: eykamp | Message: Make tests a bit more robust | |
| 04:51:51 | BFLogBot Repo: bitfighter | Commit: 3763c166e4 | Author: eykamp | Message: Protect against null strings | |
| 05:05:35 | BFLogBot Repo: bitfighter | Commit: 2144cdcdbe | Author: eykamp | Message: Protect against null strings | |
| 05:05:37 | BFLogBot Repo: bitfighter | Commit: 19f2f775fa | Author: eykamp | Message: Make tests a bit more robust | |
| 05:05:38 | BFLogBot Repo: bitfighter | Commit: f46d9115ec | Author: eykamp | Message: Protect against nulls (mostly an issue during testing) | |
| 05:07:14 | BFLogBot Repo: bitfighter | Commit: b99c5db20b | Author: eykamp | Message: Better null protection | |
| 06:35:45 | BFLogBot Repo: bitfighter | Commit: a325432987 | Author: google-labs-jules[bot] | Message: Fix buggy PointCompare logic in UIEditor.cpp and add unit test. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 06:35:48 | BFLogBot Pull request #712 opened by eykamp | Title: Fix buggy PointCompare logic in UIEditor | https://github.com/bitfighter/bitfighter/pull/712 | |
| 07:02:34 | BFLogBot Repo: bitfighter | Commit: ab799d4e76 | Author: Copilot | Message: Add LEVELSPEC.md with comprehensive Bitfighter level format documentation Agent-Logs-Url: https://github.com/bitfighter/bitfighter/sessions/c6530b4f-004c-4844-9103-55fb0ca75dd0 Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 12:14:56 | BFLogBot Comment on issue #712 | User: eykamp | Comment: Why did you have to reproduce the logic you are testing in the test itself? It seems better to use the actual code from ... | https://github.com/bitfighter/bitfighter/pull/712#issuecomment-4215730767 | |
| 12:19:56 | BFLogBot Comment on issue #712 | User: google-labs-jules[bot] | Comment: > Why did you have to reproduce the logic you are testing in the test itself? It seems better to use the actual code fro ... | https://github.com/bitfighter/bitfighter/pull/712#issuecomment-4215759707 | |
| 12:22:07 | BFLogBot Repo: bitfighter | Commit: 504042140a | Author: google-labs-jules[bot] | Message: Refactor PointCompare to Point.h and address PR feedback. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 12:30:40 | BFLogBot Pull request #713 opened by Copilot | Title: Add LEVELSPEC.md: machine-readable level format specification | https://github.com/bitfighter/bitfighter/pull/713 | |
| 12:47:04 | BFLogBot Repo: bitfighter | Commit: 0bc89d1d82 | Author: eykamp | Message: Enhance clarity of LEVELSPEC.md descriptions Clarified descriptions for SpawnLock and LoadoutZone, added notes on SpeedZone and SlipZones. | |
| 12:58:53 | BFLogBot Repo: bitfighter | Commit: a1e1c42150 | Author: eykamp | Message: Update level design requirements and guidelines Clarified requirements for core game and soccer levels, emphasizing the need for multiple items and the importance of enclosing play areas. Added notes on level shapes, symmetry, themes, and team counts. | |
| 12:59:37 | BFLogBot Repo: bitfighter | Commit: bc92b8017f | Author: Copilot | Message: Add LEVELSPEC.md: machine-readable level format specification (#713) * Add LEVELSPEC.md with comprehensive Bitfighter level format documentation Agent-Logs-Url: https://github.com/bitfighter/bitfighter/sessions/c6530b4f-004c-4844-9103-55fb0ca75dd0 Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> * Enhance clarity of LEVELSPEC.md descriptions Clarified descript | |
| 12:59:38 | BFLogBot ions for SpawnLock and LoadoutZone, added notes on SpeedZone and SlipZones. * Update level design requirements and guidelines Clarified requirements for core game and soccer levels, emphasizing the need for multiple items and the importance of enclosing play areas. Added notes on level shapes, symmetry, themes, and team counts. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: eykamp | |
| 12:59:40 | BFLogBot <1133323+eykamp@users.noreply.github.com> Co-authored-by: eykamp | |
| 12:59:56 | BFLogBot Pull request #713 closed by Copilot | Title: Add LEVELSPEC.md: machine-readable level format specification | https://github.com/bitfighter/bitfighter/pull/713 | |
| 14:52:36 | BFLogBot Comment on issue #707 | User: eykamp | Comment: What are the ramifications of changing the meaning of > and < for point comparison? It seems distance is a reasonable w ... | https://github.com/bitfighter/bitfighter/pull/707#issuecomment-4216696416 | |
| 14:54:34 | BFLogBot Comment on issue #707 | User: google-labs-jules[bot] | Comment: > What are the ramifications of changing the meaning of > and < for point comparison? It seems distance is a reasonable ... | https://github.com/bitfighter/bitfighter/pull/707#issuecomment-4216712891 | |
| 14:55:13 | BFLogBot Repo: bitfighter | Commit: bafad43872 | Author: google-labs-jules[bot] | Message: Fix PointCompare bug in UIEditor and add tests Addressed feedback by reverting global Point::operator< changes to avoid side effects. The local PointCompare in UIEditor.cpp remains fixed to satisfy strict weak ordering for std::set de-duplication. Added a new unit test file bitfighter_test/TestPointComparison.cpp. Co-authored-by: eykamp <1133323+eykamp@users.norep | |
| 14:55:15 | BFLogBot ly.github.com> | |
| 14:58:23 | BFLogBot Repo: bitfighter | Commit: 0cdd958b0b | Author: google-labs-jules[bot] | Message: Fix multiple bugs in stringUtils utility functions - Fix isHex("") returning true; it now correctly returns false. - Remove 126-character limit in parseString(const char*, Vector | |
| 14:58:25 | BFLogBot h writeLevelString's escaping convention. - Add comprehensive unit tests in bitfighter_test/TestStringUtils.cpp to verify these fixes and prevent regressions. I am an AI agent assisting with codebase maintenance. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 16:32:07 | BFLogBot Pull request #701 closed by eykamp | Title: Fix bug in parseString and add unit tests | https://github.com/bitfighter/bitfighter/pull/701 | |
| 16:32:07 | BFLogBot Repo: bitfighter | Commit: e63e7c3b04 | Author: eykamp | Message: Fix bug in parseString and add unit tests (#701) Looks good. Should be faster. I am an AI agent. I have identified and fixed a bug in the `parseString(const string &line)` function in `zap/stringUtils.cpp`. Changes: - Rewrote `parseString(const string &line)` using a character-by-character approach. - The new implementation correctly handles quoted strings with leading/trailing | |
| 16:32:08 | BFLogBot spaces and empty quoted strings. - Added support for escaped quotes using the `""` sequence, consistent with `writeLevelString`. - Replaced the `stringstream`-based implementation to improve performance and reliability. - Added `#include | |
| 16:32:10 | BFLogBot which skips leading whitespace and splits on any whitespace. This caused quoted strings like `" space start"` or `" "` to be parsed incorrectly. The manual parser ensures that the content within quotes is preserved exactly as intended. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 16:38:31 | BFLogBot Comment on issue #707 | User: eykamp | Comment: Are we now back to reproducing the logic to test for in the test itself? It shouldn't be repeated there. ... | https://github.com/bitfighter/bitfighter/pull/707#issuecomment-4217334171 | |
| 16:41:03 | BFLogBot Comment on issue #707 | User: google-labs-jules[bot] | Comment: > Are we now back to reproducing the logic to test for in the test itself? It shouldn't be repeated there. Good point. ... | https://github.com/bitfighter/bitfighter/pull/707#issuecomment-4217346138 | |
| 16:41:45 | BFLogBot Repo: bitfighter | Commit: db02424c94 | Author: google-labs-jules[bot] | Message: Refactor PointCompare and fix de-duplication bug Fixed a bug where PointCompare was not a valid strict weak ordering. Moved PointCompare to zap/Point.h to make it available for general use and to avoid code duplication in tests. Reverted global changes to Point::operator< to maintain original distance-based comparison and avoid side effects. Co-authored-by: eykamp | |
| 16:41:47 | BFLogBot <1133323+eykamp@users.noreply.github.com> | |
| 16:41:54 | BFLogBot Repo: bitfighter | Commit: 6ae127b47f | Author: eykamp | Message: Better comments Update comments in the parseStringQuotedAdvanced test to clarify expected behavior. | |
| 16:42:47 | BFLogBot Repo: bitfighter | Commit: 2144cdcdbe | Author: eykamp | Message: Protect against null strings | |
| 16:42:48 | BFLogBot Repo: bitfighter | Commit: 19f2f775fa | Author: eykamp | Message: Make tests a bit more robust | |
| 16:42:50 | BFLogBot Repo: bitfighter | Commit: f46d9115ec | Author: eykamp | Message: Protect against nulls (mostly an issue during testing) | |
| 16:42:51 | BFLogBot Repo: bitfighter | Commit: bc92b8017f | Author: Copilot | Message: Add LEVELSPEC.md: machine-readable level format specification (#713) * Add LEVELSPEC.md with comprehensive Bitfighter level format documentation Agent-Logs-Url: https://github.com/bitfighter/bitfighter/sessions/c6530b4f-004c-4844-9103-55fb0ca75dd0 Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> * Enhance clarity of LEVELSPEC.md descriptions Clarified descript | |
| 16:42:53 | BFLogBot ions for SpawnLock and LoadoutZone, added notes on SpeedZone and SlipZones. * Update level design requirements and guidelines Clarified requirements for core game and soccer levels, emphasizing the need for multiple items and the importance of enclosing play areas. Added notes on level shapes, symmetry, themes, and team counts. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: eykamp | |
| 16:42:54 | BFLogBot <1133323+eykamp@users.noreply.github.com> Co-authored-by: eykamp | |
| 16:42:56 | BFLogBot Repo: bitfighter | Commit: e63e7c3b04 | Author: eykamp | Message: Fix bug in parseString and add unit tests (#701) Looks good. Should be faster. I am an AI agent. I have identified and fixed a bug in the `parseString(const string &line)` function in `zap/stringUtils.cpp`. Changes: - Rewrote `parseString(const string &line)` using a character-by-character approach. - The new implementation correctly handles quoted strings with leading/trailing | |
| 16:42:57 | BFLogBot spaces and empty quoted strings. - Added support for escaped quotes using the `""` sequence, consistent with `writeLevelString`. - Replaced the `stringstream`-based implementation to improve performance and reliability. - Added `#include | |
| 16:42:59 | BFLogBot which skips leading whitespace and splits on any whitespace. This caused quoted strings like `" space start"` or `" "` to be parsed incorrectly. The manual parser ensures that the content within quotes is preserved exactly as intended. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 16:43:00 | BFLogBot Repo: bitfighter | Commit: 73a324c38d | Author: eykamp | Message: Merge branch 'master' into fix-stringutils-bugs-ai-13854886282832641370 | |
| 16:44:14 | BFLogBot Comment on issue #706 | User: eykamp | Comment: Can you verify this all still looks good in light of recent merges to main? ... | https://github.com/bitfighter/bitfighter/pull/706#issuecomment-4217361985 | |
| 16:45:34 | BFLogBot Comment on issue #706 | User: google-labs-jules[bot] | Comment: > Can you verify this all still looks good in light of recent merges to main? I have verified the changes by running th ... | https://github.com/bitfighter/bitfighter/pull/706#issuecomment-4217368843 | |
| 16:46:04 | BFLogBot Repo: bitfighter | Commit: 6f10441794 | Author: google-labs-jules[bot] | Message: Verify stringUtils fixes against latest main Confirmed that all unit tests pass and the new robust parsing logic is functioning as expected. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 16:46:55 | BFLogBot Pull request #700 closed by eykamp | Title: Fix PointCompare logic bug in UIEditor.cpp | https://github.com/bitfighter/bitfighter/pull/700 | |
| 16:46:55 | BFLogBot Comment on issue #700 | User: eykamp | Comment: Duplicates another PR ... | https://github.com/bitfighter/bitfighter/pull/700#issuecomment-4217375636 | |
| 16:48:42 | BFLogBot Pull request #706 closed by eykamp | Title: Fix bugs in stringUtils and add unit tests | https://github.com/bitfighter/bitfighter/pull/706 | |
| 16:49:37 | BFLogBot Pull request #712 closed by eykamp | Title: Fix buggy PointCompare logic in UIEditor | https://github.com/bitfighter/bitfighter/pull/712 | |
| 16:50:37 | BFLogBot Pull request #712 reopened by eykamp | Title: Fix buggy PointCompare logic in UIEditor | https://github.com/bitfighter/bitfighter/pull/712 | |
| 16:50:44 | BFLogBot Pull request #712 closed by eykamp | Title: Fix buggy PointCompare logic in UIEditor | https://github.com/bitfighter/bitfighter/pull/712 | |
| 16:50:45 | BFLogBot Repo: bitfighter | Commit: f8283a9706 | Author: eykamp | Message: Fix buggy PointCompare logic in UIEditor (#712) * Fix buggy PointCompare logic in UIEditor.cpp and add unit test. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> * Refactor PointCompare to Point.h and address PR feedback. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> --------- Co-authored-by: google-labs-jules[bot] <161369871+google-labs-ju | |
| 16:50:46 | BFLogBot les[bot]@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 18:41:28 | BFLogBot Repo: bitfighter | Commit: 3c5627983f | Author: google-labs-jules[bot] | Message: Standardize linear interpolation logic in Point and Color classes The `interp` (linear interpolation) function in both `Point` and `Color` classes was implemented using a non-standard formula: `p1 * t + p2 * (1 - t)`. This caused `t=0` to return `p2` and `t=1` to return `p1`, which is the inverse of the standard industry expectation where `t=0` returns the starting | |
| 18:41:30 | BFLogBot point (`p1`) and `t=1` returns the ending point (`p2`). This commit: - Updates `Point::interp` and `Color::interp` to use the standard formula: `p1 * (1 - t) + p2 * t`. - Swaps the arguments at all identified call sites in the codebase to preserve existing visual and logical behavior. - Updates existing unit tests for `Point` and `Color` to verify and lock in the standard behavior. This change ensures the API is intuitive for developers while | |
| 18:41:31 | BFLogBot maintaining system-wide correctness. I am an AI agent. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 18:41:32 | BFLogBot Pull request #714 opened by eykamp | Title: Standardize linear interpolation logic in Point and Color | https://github.com/bitfighter/bitfighter/pull/714 | |
| 18:54:51 | BFLogBot Repo: bitfighter | Commit: 27e50a68e7 | Author: google-labs-jules[bot] | Message: Standardize linear interpolation logic in Point and Color classes The `interp` (linear interpolation) function in both `Point` and `Color` classes was implemented using a non-standard formula: `p1 * t + p2 * (1 - t)`. This caused `t=0` to return `p2` and `t=1` to return `p1`, which is the inverse of the standard industry expectation where `t=0` returns the starting | |
| 18:54:52 | BFLogBot point (`p1`) and `t=1` returns the ending point (`p2`). This commit: - Updates `Point::interp` and `Color::interp` to use the standard formula: `p1 * (1 - t) + p2 * t`. - Swaps the arguments at necessary call sites in the codebase to preserve existing visual and logical behavior. - Updates existing unit tests for `Point` and `Color` to verify and lock in the standard behavior. Extraneous changes to call sites with random or 0.5 interpolation f | |
| 18:54:54 | BFLogBot actors were avoided as they are functionally unaffected by the change. I am an AI agent. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 19:08:48 | BFLogBot Comment on issue #714 | User: eykamp | Comment: Are you sure you found and updated all uses of interp (excluding the one I told you not to do)? ... | https://github.com/bitfighter/bitfighter/pull/714#issuecomment-4218356093 | |
| 19:16:10 | BFLogBot Comment on issue #714 | User: google-labs-jules[bot] | Comment: > Are you sure you found and updated all uses of interp (excluding the one I told you not to do)? I have carefully re-e ... | https://github.com/bitfighter/bitfighter/pull/714#issuecomment-4218402116 | |
| 19:20:09 | BFLogBot Repo: bitfighter | Commit: 75edc6fb06 | Author: google-labs-jules[bot] | Message: Standardize linear interpolation logic in Point and Color classes The `interp` (linear interpolation) function in both `Point` and `Color` classes was implemented using a non-standard formula: `p1 * t + p2 * (1 - t)`. This caused `t=0` to return `p2` and `t=1` to return `p1`, which is the inverse of the standard industry expectation where `t=0` returns the starting | |
| 19:20:11 | BFLogBot point (`p1`) and `t=1` returns the ending point (`p2`). This commit: - Updates `Point::interp` and `Color::interp` to use the standard formula: `p1 * (1 - t) + p2 * t`. - Swaps the arguments at necessary call sites in `zap/gameObjectRender.cpp` and `zap/CoreGame.cpp` to preserve existing visual and logical behavior. - Updates existing unit tests for `Point` and `Color` to verify and lock in the standard behavior. Call sites with random or 0.5 | |
| 19:20:12 | BFLogBot interpolation factors (in `ship.cpp`, `UIInstructions.cpp`, and `sparkManager.cpp`) were left unchanged as they are functionally unaffected by the change. I am an AI agent. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> |
Index Search ←Prev date Next date→
These logs were automatically created by BFLogBot on irc.freenode.net.