--- Log opened Mon Jun 17 00:00:53 2019 20190617 03:43:41-!- celticminstrel [~celmin@unaffiliated/celticminstrel] has quit [Quit: And lo! The computer falls into a deep sleep, to awake again some other day!] 20190617 10:46:25-!- zookeeper [~lmsnie@wesnoth/developer/zookeeper] has joined #wesnoth-umc-dev 20190617 11:49:40-!- celticminstrel [~celmin@unaffiliated/celticminstrel] has joined #wesnoth-umc-dev 20190617 13:01:26-!- celticminstrel is now known as celmin|away 20190617 21:10:56-!- zookeeper [~lmsnie@wesnoth/developer/zookeeper] has quit [Ping timeout: 248 seconds] 20190617 21:37:11<+wesdiscordbot> question: if someone makes an add-on that changes unit stats and then updates that add-on to change stats again, will there be OOS errors if old replays of a game played on the old version are loaded up with the new version? 20190617 21:42:45<+wesdiscordbot> yes 20190617 21:43:23<+wesdiscordbot> In short, replays ans MP are the same – in the replay, your computer plays the game again 20190617 21:46:13-!- sevu [~sevu@p5B28FD5E.dip0.t-ipconnect.de] has joined #wesnoth-umc-dev 20190617 21:47:19< sevu> though, I'm not so sure how bad it is, if it causes... celmin|away, you you know more? 20190617 21:50:00<+wesdiscordbot> at the moment our solution is to have Version 1 on the server and then if unit changes are made then there will be a totally new addon called Version 2 etc 20190617 21:50:04<+wesdiscordbot> no way around that eh? 20190617 21:50:24< sevu> I think it causes OOS in the moment when the stat change does make a difference in some other are, e.g. if you have now more damage than at the time of the replay and thus kill the unit, while in the replay the unit would want to do something on the next turn 20190617 21:52:12< sevu> I assume the OOS doesn't happen at the end of a fight where you made more/less damage, but if this results in something else not happening like it is planned by the replay to happen. 20190617 22:00:09-!- sevu [~sevu@p5B28FD5E.dip0.t-ipconnect.de] has quit [Remote host closed the connection] 20190617 22:09:29-!- ChanServ [ChanServ@services.] has quit [shutting down] 20190617 22:14:10-!- ChanServ [ChanServ@services.] has joined #wesnoth-umc-dev 20190617 22:14:10-!- ServerMode/#wesnoth-umc-dev [+o ChanServ] by tolkien.freenode.net 20190617 23:43:36<+wesdiscordbot> would it work to have the version numbers on the unit IDs instead? Mage1, Mage2, etc. so even if Mage1 isn't in any recruit list anymore, it would still be available for replays. --- Log closed Tue Jun 18 00:00:55 2019