| 00:19.35 | *** join/#bzflag infobot (ibot@208.53.50.136) |
| 00:19.35 | *** topic/#bzflag is https://BZFlag.org || http://ohloh.net/p/bzflag || https://bzflag.org/help || Channel Logs: http://infobot.rikers.org/%23bzflag/ || 2.4.14 released! https://forums.bzflag.org/viewtopic.php?f=62&t=19953 |
| 00:19.36 | *** mode/#bzflag [+v infobot] by ChanServ |
| 01:25.02 | *** join/#bzflag McSpider (~McSpider@li1055-178.members.linode.com) |
| 01:49.00 | allejo | i'm probably asking for too much but, are there any docs with how replays store their information? or point me in the general direction |
| 02:12.59 | blast007 | src/bzfs/RecordReplay.cxx |
| 02:13.55 | blast007 | I think the general idea is that there's a header that has info about the recording, then a dump of flag information, world data, and then the network messages are written out |
| 02:33.15 | allejo | pokes around |
| 13:26.22 | *** join/#bzflag joevano (~joevano@bzflag/developer/JoeVano) |
| 13:26.23 | *** mode/#bzflag [+v joevano] by ChanServ |
| 18:22.10 | *** join/#bzflag ChanServ (ChanServ@services.) |
| 18:22.10 | *** mode/#bzflag [+o ChanServ] by wilhelm.freenode.net |
| 22:12.12 | *** join/#bzflag spldart (~james@bzflag/contributor/spldart) |
| 22:12.12 | *** mode/#bzflag [+v spldart] by ChanServ |
| 23:03.45 | *** join/#bzflag ChanServ (ChanServ@services.) |
| 23:03.45 | *** mode/#bzflag [+o ChanServ] by wilhelm.freenode.net |