--- Log opened Sun Aug 26 00:00:25 2018 20180826 00:24:57-!- Tobbi [~Tobbi@supertux/tobbi] has joined #wesnoth 20180826 00:33:44-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection] 20180826 00:33:50-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth 20180826 00:46:10-!- Tobbi [~Tobbi@supertux/tobbi] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 20180826 00:58:32-!- Haudegen [~quassel@178.115.237.87.static.drei.at] has quit [Remote host closed the connection] 20180826 01:04:01-!- HeyCitizen [~HeyCitize@sttrpq3809w-lp130-05-69-156-204-156.dsl.bell.ca] has quit [Quit: ZNC 1.7.1 - https://znc.in] 20180826 01:05:19-!- HeyCitizen [~HeyCitize@sttrpq3809w-lp130-05-69-156-204-156.dsl.bell.ca] has joined #wesnoth 20180826 01:08:43-!- HeyCitizen_ [HeyCitizen@gateway/vpn/privateinternetaccess/heycitizen] has joined #wesnoth 20180826 01:09:51-!- HeyCitizen [~HeyCitize@sttrpq3809w-lp130-05-69-156-204-156.dsl.bell.ca] has quit [Ping timeout: 244 seconds] 20180826 01:19:15-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection] 20180826 01:19:21-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth 20180826 03:01:33-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection] 20180826 03:01:42-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth 20180826 03:28:46-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection] 20180826 03:28:53-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth 20180826 03:48:48-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection] 20180826 03:48:54-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth 20180826 06:31:48-!- celticminstrel is now known as celmin|sleep 20180826 07:45:33-!- Johannes13 [~Johannes1@unaffiliated/johannes13] has joined #wesnoth 20180826 07:48:30-!- DasBrain [~Johannes1@unaffiliated/johannes13] has quit [Ping timeout: 264 seconds] 20180826 08:13:35-!- mthe878 [~mthe@unaffiliated/mthe] has joined #wesnoth 20180826 09:16:30-!- Tobbi [~Tobbi@supertux/tobbi] has joined #wesnoth 20180826 09:28:57-!- mthe878 [~mthe@unaffiliated/mthe] has quit [Ping timeout: 244 seconds] 20180826 09:38:11-!- Haudegen [~quassel@178.115.237.87.static.drei.at] has joined #wesnoth 20180826 10:11:15-!- ToBeCloud [uid51591@wikimedia/ToBeFree] has joined #wesnoth 20180826 10:53:07-!- TheJJ [~rofl@ipbcc06208.dynamic.kabel-deutschland.de] has quit [Read error: Connection reset by peer] 20180826 10:55:01-!- TheJJ [~rofl@ipbcc06208.dynamic.kabel-deutschland.de] has joined #wesnoth 20180826 13:00:37-!- claymore [~claymore@unaffiliated/claymore] has joined #wesnoth 20180826 14:01:17-!- zookeeper [~lmsnie@wesnoth/developer/zookeeper] has joined #wesnoth 20180826 15:07:33-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection] 20180826 15:07:39-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth 20180826 15:22:38-!- Tobbi [~Tobbi@supertux/tobbi] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 20180826 15:55:01-!- Ravana_ [~Ravana@unaffiliated/ravana/x-2327071] has quit [] 20180826 15:59:05-!- telmich [~deadghost@gpm/telmich] has joined #wesnoth 20180826 15:59:11< telmich> good evening 20180826 15:59:33< telmich> I was wondering what to do if you don't see a signpost in a campaign where you are supposed to leave via signpost? 20180826 16:00:22< telmich> I've the problem in LoW - Saurian Treasure 20180826 16:00:22-!- ToBeCloud [uid51591@wikimedia/ToBeFree] has quit [Quit: Connection closed for inactivity] 20180826 16:00:56<+wesdiscordbot> I'd suggest either try moving to the place anyway, or going through the files to figure out what the problem is. 20180826 16:01:25<+wesdiscordbot> Sorry if I'm not the most helpful, I don't have much knowledge of bugs or troubleshooting in Wesnoth. 20180826 16:04:11-!- Ravana_ [~Ravana@unaffiliated/ravana/x-2327071] has joined #wesnoth 20180826 16:17:09<+wesdiscordbot> telmich: the signpost should be in the forest in the southwest, have you looked there? 20180826 16:20:16-!- Ravana_ [~Ravana@unaffiliated/ravana/x-2327071] has quit [] 20180826 16:25:29-!- Ravana_ [~Ravana@unaffiliated/ravana/x-2327071] has joined #wesnoth 20180826 17:06:49<+wesdiscordbot> @shadowm (I hope I'm not spamming.) 20180826 17:07:12<+wesdiscordbot> wha 20180826 17:09:24<+wesdiscordbot> Would you mind if I start playing the AtS on your github? 20180826 17:09:52<+wesdiscordbot> Probably yes, you'll run into unseen and unfixed bugs. 20180826 17:10:56<+wesdiscordbot> Unseen means no-one knows about them yet or that I won't see them? ._. 20180826 17:11:20<+wesdiscordbot> I'll put them on github of course if I notice some. 20180826 17:11:54<+wesdiscordbot> Former 20180826 17:12:04<+wesdiscordbot> You said you haven't played AtS before, that's why it's a bad idea. 20180826 17:12:31<+wesdiscordbot> It'll be hard for you in some cases to tell if you've stumbled upon a bug so you might not even notice them. 20180826 17:13:14<+wesdiscordbot> I know the devs broke something in a very late scenario in a seemingly innocuous fashion but I can't promise there isn't worse stuff lurking out there. 20180826 17:14:07<+wesdiscordbot> I haven't played further than half of the 2nd episode. 20180826 17:15:08<+wesdiscordbot> And as I want to make true of my suggestion (playing it parallel on 1.12. as well), that won't be a problem. ...well that stuff in the very late scenario might be a problem. I'll see it once I get there. xD 20180826 17:15:57<+wesdiscordbot> You'll mostly see a lot of error messages in basically the last gameplay scenario that hopefully don't actually impact anything. 20180826 17:16:31<+wesdiscordbot> But it's not the only scenario that relies on certain assumptions about the WML events engine that held true for 1.10 and 1.12 but don't for 1.14. 20180826 17:17:19<+wesdiscordbot> So I wouldn't be surprised if somewhere else it actually causes things to go all kinds of wrong. 20180826 17:18:04<+wesdiscordbot> Well, if it does, then you'll at least know about it. :) Can't fix things you don't know about, right? ^^ 20180826 17:18:05<+wesdiscordbot> Without going into a full-fledged rant, this is why developing content for Wesnoth is frustrating. 20180826 17:18:56<+wesdiscordbot> And also, none of the gameplay changes are in yet. 20180826 17:19:08<+wesdiscordbot> Because the engine is still being developed yet? 20180826 17:19:14<+wesdiscordbot> And E1 still uses the old Quenoth. 20180826 17:19:21<+wesdiscordbot> The engine was complete in version 1.0 in 2005. 20180826 17:19:47<+wesdiscordbot> It's just been extended, redone, and extended and redone multiple times because people can't ever leave it alone. 20180826 17:19:59<+wesdiscordbot> Sure, good things come out of the process. 20180826 17:20:05<+wesdiscordbot> AtS wouldn't be doable with the Wesnoth 1.0 engine. 20180826 17:20:30<+wesdiscordbot> It was done for 1.10 and some specific parts for 1.12. 20180826 17:20:38-!- Haudegen [~quassel@178.115.237.87.static.drei.at] has quit [Remote host closed the connection] 20180826 17:21:16<+wesdiscordbot> But when undocumented breakage happens and you're maintaining a colossal add-on it becomes really frustrating. 20180826 17:21:40<+wesdiscordbot> Especially since the mainline developers tend to have a mainline developers first mentality. 20180826 17:22:05<+wesdiscordbot> I agree that undocumented subtle changes such as the event order change should be avoided like the plague. 20180826 17:22:44<+wesdiscordbot> Okay. Do you have some kind of list of scenarios/events that will be different anyway once release, so I shouldn't bother reporting them as broken? Is the main problem therefore undocumented changes? :( 20180826 17:22:45<+wesdiscordbot> If it means not refactoring engine code, so be it. Refactoring is definitely not a strong enough reason to cause that kind of hard-to-notice API changes. 20180826 17:23:04<+wesdiscordbot> The main problem is unintentional changes. 20180826 17:23:14<+wesdiscordbot> They usually are unintentional, anyway. 20180826 17:23:22<+wesdiscordbot> Yeah, and there isn't much we can do to avoid them. 😦 20180826 17:23:41<+wesdiscordbot> ...one can accidentally change how things work? 20180826 17:23:46<+wesdiscordbot> Sometimes people legit change things on purpose and forget to document them. 20180826 17:23:51<+wesdiscordbot> Yes, you can. :p 20180826 17:23:59<+wesdiscordbot> It's not hard to do. 20180826 17:24:13<+wesdiscordbot> Especially in such a complex codebase. 20180826 17:24:36<+wesdiscordbot> The way things interact and stuff, I guess? 20180826 17:24:41<+wesdiscordbot> YES 20180826 17:24:46<+wesdiscordbot> Oops, didn't mean to type in caps. 20180826 17:25:29<+wesdiscordbot> I guess we don't have enough people to rigorously test changes to notice that, right? :/ 20180826 17:26:11<+wesdiscordbot> There was also that time I changed behavior for units with negative HP because I didn't know accurately enough what actually is the API developers are allowed to rely on and what isn't. 20180826 17:26:27<+wesdiscordbot> hi 20180826 17:26:47<+wesdiscordbot> I thought I had changed the undocumented stuff that we can change at will, but then it turned out that the behavior had actually been documented in the wiki and thus was a part of the API. 20180826 17:27:00<+wesdiscordbot> @jyrkive If it makes you feel better, I don't even know what API is, so... 20180826 17:29:35<+wesdiscordbot> This is probably a good as-of-yet-unfixed example: https://github.com/project-ethea/Invasion_from_the_Unknown/issues/26 The only reason this is/was an issue in 1.14 is because the process for initializing the events/Lua engine changed considerably between 1.12 and 1.14, and at the same time, the loading process for the game gained parallelization by offloading part of the work onto a different thread than the display 20180826 17:29:35<+wesdiscordbot> rendering thread (the original startup thread) in the name of allowing the game to have an animated loading screen. I believe the non-deterministic facet of the issue is fixed in 1.14.4 through a slightly crude hack (I'm not sure since I haven't touched Wesnoth since shortly after it was introduced), but I've read gfgtdf advising people against using GUI calls in preload/prestart events and [lua] (which is processed before preload 20180826 17:29:36<+wesdiscordbot> in 1.14 as opposed to being part of preload like it seemingly was in 1.12), so there may still be issues involving the event engine side of the process. 20180826 17:30:07<+wesdiscordbot> The fix on the add-on's side in this case is trivial: do not use GUI calls in preload/prestart/global [lua]. 20180826 17:30:31<+wesdiscordbot> So you now need to wait for the game map to come up when you didn't need before. 20180826 17:32:47<+wesdiscordbot> Is this a good change? No (although it affects rather niche use cases and most people will never come across this bug). Does the breakage have a good justification? Maybe, this is highly debatable (issues with the threaded loading process have been the source of dozens of commits throughout 1.13.x and 1.14.x). 20180826 17:33:16<+wesdiscordbot> But it's a good example of the kind of things that happen by accident in a huge codebase that doesn't stop changing owners. 20180826 17:34:12<+wesdiscordbot> Isn't the change being good/bad tied to the justification of the breakage? 20180826 17:34:32<+wesdiscordbot> Not really. 20180826 17:35:47<+wesdiscordbot> Again, it's highly debatable. One particular developer feels the benefits brought upon us (1. being able to quit Wesnoth during the loading screen; and 2. being able to display an animation on the screen so people know Wesnoth didn't hang up if it takes too long to complete the operation) by the underlying architectural changes far outweigh the fallout thereof. 20180826 17:36:19<+wesdiscordbot> No word on the event engine side of things because the dev that did those isn't active anymore. 20180826 17:36:37<+wesdiscordbot> Or at least part of those changes. 20180826 17:37:25<+wesdiscordbot> A lot of different people touched the event engine throughout 1.13.x and that might as well be part of the issue. 20180826 17:38:11<+wesdiscordbot> To this day I still haven't managed to get hold of anyone able to explain to me what the "kernels" concept is and how it is relevant for anyone (even though it's referenced in the latest security patch). 20180826 17:38:28-!- Narrat [~Narrat@p5DCC6616.dip0.t-ipconnect.de] has joined #wesnoth 20180826 17:39:57<+wesdiscordbot> I wouldn't call it "referencing". 20180826 17:39:59<+wesdiscordbot> https://github.com/wesnoth/wesnoth/commit/2554c166dd45bfdee8ee24431224bd25e52bab12 20180826 17:40:24<+wesdiscordbot> The word "kernel" does tehcnically appear in the commit message: "There is also an occurance in the application_lua_kernel that was not fixed because i assumed that umc cannot contian application lua scipts.". 20180826 17:40:45<+wesdiscordbot> But use of that word simply means that the occurrence is in that C++ class. 20180826 17:41:07<+wesdiscordbot> There's two or three "kernels", whatever they are. 20180826 17:41:27<+wesdiscordbot> The fact that this is somehow relevant for that patch implies their existence is more than just an implementation detail. 20180826 17:42:16<+wesdiscordbot> AFAIK, the difference is that plugins use the application kernel whereas untrusted Lua code (mainline as well as UMC) uses the game kernel. 20180826 17:42:35<+wesdiscordbot> Thus, code in application kernel doesn't need to care about security. 20180826 17:42:46<+wesdiscordbot> But what is a "plugin"? 20180826 17:43:29<+wesdiscordbot> Plugins can be run with the --plugin=my_plugin.lua command line argument. 20180826 17:43:51<+wesdiscordbot> A plugin automatically drives Wesnoth in place of a real human player. 20180826 17:44:08<+wesdiscordbot> Three plugins are used for the automatic MP test that runs in Travis CI after every commit. 20180826 17:44:13<+wesdiscordbot> https://github.com/wesnoth/wesnoth/blob/master/utils/travis/mp_test_executor.sh 20180826 17:44:44<+wesdiscordbot> I have also written a fourth plugin in case it's useful to simulate MP lobby activity (e.g. for performance testing). 20180826 17:45:18< celmin|sleep> [Aug 26@1:30:08pm] wesdiscordbot: The fix on the add-on's side in this case is trivial: do not use GUI calls in preload/prestart/global [lua]. 20180826 17:45:19< celmin|sleep> Sigh. I distinctly recall fixing this and then someone went and broke it again. 20180826 17:45:22<+wesdiscordbot> That's a rather unfortunate name for a piece of automation in this game. 20180826 17:45:48< celmin|sleep> I think it was actually gfgtdf when he implemented the threaded loading screen, but not sure. 20180826 17:45:50<+wesdiscordbot> A lot of people in the community have called add-ons "plugins" over the years. 20180826 17:46:03< celmin|sleep> There are indeed three Lua kernels. 20180826 17:46:05<+wesdiscordbot> Agreed. It's not a good name. 20180826 17:46:15< celmin|sleep> For most things that doesn't actually matter. 20180826 17:46:42< celmin|sleep> On the LuaAPI page I chose the term "context" rather than "kernels". 20180826 17:47:07< celmin|sleep> 99% of Lua code runs in the game context. Map generators run in a map generator context. Plugins run in the application context as a coroutine. 20180826 17:47:44<+wesdiscordbot> So I'm guessing that means map generators do not have access to the same APIs as events? 20180826 17:47:50< celmin|sleep> Some API features are only available in certain contexts, yes. 20180826 17:47:53<+wesdiscordbot> (And viceversa= 20180826 17:48:18<+wesdiscordbot> I guess that makes more sense when you call it "context" rather than "kernel". 20180826 17:48:34< celmin|sleep> I don't think there's much that's exclusive to mapgen or application context. 20180826 17:48:49< celmin|sleep> There is the wesnoth.preferences table that's only available in the application context, I guess. 20180826 17:49:02<+wesdiscordbot> celmin|sleep: Do you think I should document in the LuaAPI page that loadstring() isn't available in 1.15? 20180826 17:49:14<+wesdiscordbot> (Note that it's not documented in the Lua manual either.) 20180826 17:49:15< celmin|sleep> I don't think there's any documentation of the application context actually. 20180826 17:49:46< celmin|sleep> @jyrkive I guess it wouldn't hurt to explicitly mention that it's not available? 20180826 17:49:48<+wesdiscordbot> (More specifically, Lua manual doesn't document that loadstring() exists.) 20180826 17:50:05< celmin|sleep> BTW you can just call me "celmin", no need to type out the full nick. 20180826 17:50:28< celmin|sleep> (I'm assuming that wasn't tab-complete, since you're on Discord.) 20180826 17:52:16<+wesdiscordbot> Added: https://wiki.wesnoth.org/index.php?title=LuaAPI&curid=6436&diff=59933&oldid=59746 20180826 17:53:24< celmin|sleep> I should really get around to finishing that page and its subpages... 20180826 17:53:31< celmin|sleep> Well, mainly its subpages. 20180826 17:54:04< celmin|sleep> IIRC there was a relevant PR to finish first though... 20180826 17:55:22<+wesdiscordbot> My thanks to all of you for all of this information. I'd never have heard it without you. It was interesting. ^^ 20180826 18:05:58-!- Tobbi [~Tobbi@supertux/tobbi] has joined #wesnoth 20180826 18:14:09<+wesdiscordbot> celmin: not a PR, but maybe this is what you were thinking of? https://github.com/wesnoth/wesnoth/issues/2653 20180826 18:34:21-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection] 20180826 18:34:28-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth 20180826 18:39:31-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection] 20180826 18:39:37-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth 20180826 19:12:51-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has quit [Remote host closed the connection] 20180826 19:13:00-!- janebot [~Gambot@unaffiliated/gambit/bot/gambot] has joined #wesnoth 20180826 19:56:10< celmin|sleep> @Pentarctagon - No, I was thinking of #2635 20180826 19:56:27<+wesdiscordbot> @shadowm The way the Warning at the beginning of the campaign is displayed is definitely a huge improvement. 😮 20180826 19:58:28<+wesdiscordbot> Did all of you notice this one? https://github.com/wesnoth/wesnoth/pull/3176 20180826 20:02:20<+wesdiscordbot> Or rather how text is displayed in those prescenario things. 20180826 20:02:50< celmin|sleep> ??? 20180826 20:04:21<+wesdiscordbot> ..? 20180826 20:04:40<+wesdiscordbot> I do not quite understand your question, Articulating might help. xD 20180826 20:08:06<+wesdiscordbot> Playing 1.12 and 1.14 at the same time certainly helps me appreciate the change of font and spacing between the lines, pretty much in every part of the game. 20180826 20:13:39<+wesdiscordbot> I have to say, I've spent now more than five minutes marveling at the small changes to maptiles from 1.12 to 1.14. It's awesome. Subtle. And awesome. 20180826 20:15:54<+wesdiscordbot> Did I already mention the font change? It's awesome. 20180826 20:16:22<+wesdiscordbot> Windows builds for versions before 1.13.6 or so have had a bug for a decade where empty lines were collapsed, causing paragraphs to get squished together. 20180826 20:16:46<+wesdiscordbot> So that's probably going to be a very obvious difference between 1.12 and 1.14. 20180826 20:19:02<+wesdiscordbot> There was also a font change, and/or the font size was increased. 20180826 20:20:58<+wesdiscordbot> Btw, why does that village in the first scenario have no guards towards the east? 20180826 20:24:29<+wesdiscordbot> It must be pretty safe in that direction 20180826 20:24:32<+wesdiscordbot> xD 20180826 20:24:56<+wesdiscordbot> deteriorated in AtS doesn't mean the same as in IftU. 20180826 20:25:15<+wesdiscordbot> Or at least not as the 1.14 IftU 20180826 20:25:16<+wesdiscordbot> I'm aware. 20180826 20:25:32<+wesdiscordbot> ...do you plan on changing that? D: 20180826 20:25:51<+wesdiscordbot> No. 20180826 20:26:52<+wesdiscordbot> ...that's certainly confusing. And I guess that means you don't plan on enabling any kind of unit carryover from IftU to AtS. ._. 20180826 20:27:00<+wesdiscordbot> At least no Malin Keshar. 20180826 20:28:07<+wesdiscordbot> It doesn't really have any bearing on that. 20180826 20:29:41<+wesdiscordbot> But if you let Mal Keshar carry over from IftU to AtS, wouldn't he retain the IftU meaning of deterioated instead of using the AtS one? 20180826 20:30:27<+wesdiscordbot> More like melon cashier 20180826 20:30:36<+wesdiscordbot> I can completely change how all that stuff works if I decide to implement heroes carryover. 20180826 20:32:38<+wesdiscordbot> The actual important question to me is why you want/are fine with two different 'deterioating' on the same unit? 20180826 20:33:38-!- behalebabo [~behalebab@unaffiliated/behalebabo] has joined #wesnoth 20180826 20:40:58<+wesdiscordbot> why does that matter o_o 20180826 20:42:11<+wesdiscordbot> He gets nerfed by the events of the last boss battle in IftU. 20180826 20:42:22<+wesdiscordbot> Then he recovers slightly but not completely after a while. 20180826 20:43:25<+wesdiscordbot> The Chaos Cardinal is not a unit in IftU btw. 20180826 20:46:45<+wesdiscordbot> The one in AtS is somewhat worse than the one in IftU though. ._. So that doesn't look like recovering to me. :/ (-10% hp vs -5% hp and +50% XP to advance) Yes he is! 😄 He is in Shadows of Time. 20180826 20:47:54<+wesdiscordbot> And Voice of the Armageddon. 20180826 20:48:15<+wesdiscordbot> Well apparently I didn't move that to Naia gdi 20180826 20:48:54<+wesdiscordbot> ...let's check whether I was looking in the right version folder. 20180826 20:49:24< celmin|sleep> I was the one who didn't understand your question. >_> 20180826 20:49:36<+wesdiscordbot> I didn't, but the same still holds true for 1.14. 20180826 20:50:30<+wesdiscordbot> celmin: Whether you saw this Pull Request. Because I like it. 😄 20180826 20:50:54< celmin|sleep> I thought there was more to the question than just that, but okay. 20180826 20:51:18<+wesdiscordbot> celmin: Sorry, but I'm sometimes very direct. 😄 20180826 20:55:04< celmin|sleep> Whyyyy do I feel so tired 20180826 20:55:41<+wesdiscordbot> Because you are awake instead of asleep. 20180826 20:55:45<+wesdiscordbot> Duh. 20180826 21:05:39<+wesdiscordbot> hmm one time i had an episode where i felt super super tired for a week that i couldnt even go to school so i ended up missing like 4 days of school but at least managing to go one day that week 20180826 21:05:56<+wesdiscordbot> i wasnt really sure what it is but i think it was an illness because one of my family members had the same thing happen right afterwards 20180826 21:06:30<+wesdiscordbot> i was just lying in bed for like 20 hours out of the whole day 20180826 21:25:29< celmin|sleep> o.o 20180826 21:26:35<+wesdiscordbot> OMG I just realized that your name has |sleep XDD that's quite funny :) :P 20180826 21:33:53< Ravana_> that means I can remove the comment that says empty lines must have space 20180826 21:36:01-!- claymore [~claymore@unaffiliated/claymore] has quit [Quit: Leaving] 20180826 21:40:44< Ravana_> https://github.com/ProditorMagnus/Ageless-for-1-14/commit/0c049285bff1915216bfe930acb6f83f1b3e46ec 20180826 21:57:35-!- zookeeper [~lmsnie@wesnoth/developer/zookeeper] has quit [Ping timeout: 272 seconds] 20180826 22:01:34-!- Narrat [~Narrat@p5DCC6616.dip0.t-ipconnect.de] has quit [Quit: They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.] 20180826 22:03:25-!- Narrat [~Narrat@p5DCC6616.dip0.t-ipconnect.de] has joined #wesnoth 20180826 22:14:09-!- sevu [~sevu@p54855A75.dip0.t-ipconnect.de] has joined #wesnoth 20180826 22:22:58-!- behalebabo [~behalebab@unaffiliated/behalebabo] has quit [Ping timeout: 252 seconds] 20180826 22:23:14-!- Tobbi [~Tobbi@supertux/tobbi] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 20180826 22:27:29-!- behalebabo [~behalebab@unaffiliated/behalebabo] has joined #wesnoth 20180826 22:30:41-!- sevu [~sevu@p54855A75.dip0.t-ipconnect.de] has quit [Remote host closed the connection] 20180826 23:29:44<+wesdiscordbot> Holy fuck 20180826 23:29:49<+wesdiscordbot> Did you see the Madden shooting? 20180826 23:29:59-!- Narrat [~Narrat@p5DCC6616.dip0.t-ipconnect.de] has quit [Quit: They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.] 20180826 23:48:11-!- celmin|sleep [~celmin@unaffiliated/celticminstrel] has quit [Quit: KABOOM! It seems that I have exploded. Please wait while I reinstall the universe.] 20180826 23:50:10<+wesdiscordbot> Yes. 😦 20180826 23:59:45<+wesdiscordbot> Horrible. --- Log closed Mon Aug 27 00:00:26 2018