--- Log opened Mon Mar 11 00:00:34 2019 20190311 04:49:01-!- celticminstrel is now known as celmin|sleep 20190311 08:33:12-!- zookeeper [~lmsnie@wesnoth/developer/zookeeper] has joined #wesnoth 20190311 12:10:20-!- Haudegen [~quassel@212-186-77-29.static.upcbusiness.at] has joined #wesnoth 20190311 12:41:40-!- celmin|sleep is now known as celmin|away 20190311 16:36:46-!- Ravana [~Ravana@wesnoth/mp-mod/ravana] has quit [Read error: Connection reset by peer] 20190311 16:49:11-!- Haudegen [~quassel@212-186-77-29.static.upcbusiness.at] has quit [Remote host closed the connection] 20190311 17:50:56-!- Haudegen [~quassel@178.115.237.87.static.drei.at] has joined #wesnoth 20190311 18:45:33<+wesdiscordbot> What reason are there for a replay to break? 20190311 18:57:38-!- Ravana [~Ravana@wesnoth/mp-mod/ravana] has joined #wesnoth 20190311 19:07:17<+wesdiscordbot> break how? 20190311 19:25:51<+wesdiscordbot> make WML errors? 20190311 19:28:11<+wesdiscordbot> Error details: found corrupt movement in replay. 20190311 19:28:21<+wesdiscordbot> I have no idea why it would find something like that. 20190311 19:29:35<+wesdiscordbot> (But that's 1.12.6, mind you. I have no reason to believe the same thing happens in 1.14.6) 20190311 19:31:24<+wesdiscordbot> https://github.com/wesnoth/wesnoth/blob/1.12.6/src/actions/move.cpp#L905 20190311 19:31:24<+wesdiscordbot> A dev could probably check the code but I'd wager it has something to do with a unit performing a movement that's no longer valid 20190311 19:31:36<+wesdiscordbot> Such as if movement costs for the terrains involved changed etc 20190311 19:32:06<+wesdiscordbot> But yeah, if it's 1.12 then uh 20190311 19:32:11<+wesdiscordbot> 1.12 is dead since May 1st 2018 20190311 19:32:47<+wesdiscordbot> Can you reproduce the error in 1.14 ? 20190311 19:33:35<+wesdiscordbot> You mean, by watching the replay with 1.14? 20190311 19:34:08<+wesdiscordbot> No 20190311 19:34:21<+wesdiscordbot> By starting the scenario anew in 1.14, then loading that replay in 1.14 20190311 19:35:00<+wesdiscordbot> A 1.12 replay is not expected to load in 1.14 20190311 19:37:09<+wesdiscordbot> So, you want me to load the 1.12 scenario start file in 1.14, play the scenario and watch the replay? 🤔 I'm not sure if I understand you. 😅 20190311 19:37:33-!- gallaecio [~quassel@252.150.165.83.dynamic.reverse-mundo-r.com] has joined #wesnoth 20190311 19:37:37<+wesdiscordbot> No, let me try again. 20190311 19:37:45<+wesdiscordbot> I want you to start the campaign on 1.14 20190311 19:37:51<+wesdiscordbot> Use :change_level to jump to the right scenario 20190311 19:38:02<+wesdiscordbot> Play it as you did in 1.12 in the turn the error happens on 20190311 19:38:06<+wesdiscordbot> Save 20190311 19:38:11<+wesdiscordbot> View the replay in 1.14 20190311 19:38:18<+wesdiscordbot> Tell us if the error still happens 20190311 19:39:05<+wesdiscordbot> In that case: it doesn't. At least not on the same turns. (I'm 8 turns past that. 14 turns left till the scenario is over.) 20190311 19:39:50<+wesdiscordbot> Okay. So whatever it was may have been fixed by now. 20190311 19:39:59<+wesdiscordbot> It may have been a bug in the campaign, by the way. 20190311 20:06:23-!- madmax28 [~madmax28@2001-4dd6-fc48-0-ba27-ebff-febc-e0cb.ipv6dyn.netcologne.de] has joined #wesnoth 20190311 20:08:44-!- madmax28_ [~madmax28@xdsl-87-78-223-70.nc.de] has quit [Ping timeout: 250 seconds] 20190311 20:50:20-!- cyphase [~cyphase@unaffiliated/cyphase] has quit [Ping timeout: 250 seconds] 20190311 21:07:38-!- cyphase [~cyphase@unaffiliated/cyphase] has joined #wesnoth 20190311 21:35:29-!- Haudegen [~quassel@178.115.237.87.static.drei.at] has quit [Read error: Connection reset by peer] 20190311 22:03:40-!- Haudegen [~quassel@178.115.237.87.static.drei.at] has joined #wesnoth 20190311 22:16:52-!- gallaecio [~quassel@252.150.165.83.dynamic.reverse-mundo-r.com] has quit [Remote host closed the connection] 20190311 22:38:25-!- mthe878 [~mthe@unaffiliated/mthe] has joined #wesnoth 20190311 23:42:16-!- Haudegen [~quassel@178.115.237.87.static.drei.at] has quit [Read error: Connection reset by peer] --- Log closed Tue Mar 12 00:00:37 2019