--- Log opened Sat Nov 10 00:00:22 2018 --- Day changed Sat Nov 10 2018 20181110 00:00:22<+wesdiscordbot> what I thought about was removing all units, traits, abiites, specials, and only leave the terrain graphics and most of the macros + the binary path... 20181110 00:00:39<+wesdiscordbot> So that it would fit with a non dark age UMC 20181110 00:01:28<+wesdiscordbot> some futristic era … 20181110 00:03:07<+wesdiscordbot> I feel like a better way to look at much of this would be to consider mainline a set of modules rather than a monolithic unit like it currently is 20181110 00:15:31-!- zookeeper [~lmsnie@wesnoth/developer/zookeeper] has quit [Ping timeout: 246 seconds] 20181110 00:36:19-!- boucman [~rosen@wesnoth/developer/boucman] has quit [Remote host closed the connection] 20181110 00:55:26-!- irker350 [~irker@wesnoth/umc-dev/bot/shikadibot] has quit [Quit: transmission timeout] 20181110 01:29:11-!- celmin|away is now known as celticminstrel 20181110 01:29:19< celticminstrel> Hmm, looking at that wiki page... 20181110 01:29:31< celticminstrel> "[attacks]: not displayed" 20181110 01:29:38< celticminstrel> "[defends]: not displayed" 20181110 01:29:50< celticminstrel> Sounds like something to be fixed (assuming it's still accurate)? 20181110 01:44:51-!- stikonas [~gentoo@wesnoth/translator/stikonas] has quit [Read error: Connection reset by peer] 20181110 02:04:51<+wesdiscordbot> What was this error about again? Mandatory WML child missing yet untested for. Please report. 20181110 02:07:47< celticminstrel> "At some point earlier I looked up a tag in a config but didn't bother to check that it actually existed. Now I've tried to find something in that tag and suddenly realized I don't actually have a tag to look in." 20181110 02:15:29< celticminstrel> See also: https://github.com/wesnoth/wesnoth/pull/3672 20181110 02:18:32<+wesdiscordbot> hmmm... to bad it doesn't tell which tag it is 20181110 02:18:36<+wesdiscordbot> *too 20181110 02:18:45< celticminstrel> It doesn't tell you because it doesn't know. 20181110 02:18:59< celticminstrel> It has no way to know. 20181110 02:19:06< celticminstrel> That's why it's such a terrible error. 20181110 02:19:28< celticminstrel> The PR in theory should greatly improve the situation once completed. 20181110 02:19:29<+wesdiscordbot> "something went wrong" 20181110 02:19:40< celticminstrel> But of course it also risks adding new crashes via null pointer access. 20181110 02:21:11<+wesdiscordbot> is it ready to try out? 20181110 02:21:41< celticminstrel> Not sure. You could try, but I can't promise it won't crash somewhere. 20181110 02:22:13<+wesdiscordbot> I promise it will :p 20181110 02:22:19< celticminstrel> :P 20181110 02:22:26< celticminstrel> The probability is high. 20181110 02:22:57<+wesdiscordbot> I try to figure out how the core loading works... it missed probably pretty much any tag.. and not really the situation other people encountered before 20181110 02:23:25< celticminstrel> Hm? Is core loading broken then? 20181110 02:24:22<+wesdiscordbot> Probably not, I just don't know how to load a custom core 20181110 02:25:15< celticminstrel> AIUI you need to place a core.cfg file in your addon's folder (rather than _main.cfg) which contains a [core] tag. 20181110 02:25:34< celticminstrel> If you have it all set up right, a new "Cores" button should appear in the main menu. 20181110 02:25:59< celticminstrel> (Might still need _main.cfg as well, not sure.) 20181110 02:27:26<+wesdiscordbot> That far I came. Now the question is how to proceed from there. I think it's putting all kind of stuff into the _main.cfg, and I guess I lack things there triggering this error 20181110 02:33:29<+wesdiscordbot> Do cores share macros among them? 20181110 02:34:33< celticminstrel> AIUI, the core essentially replaces data/_main.cfg, so you'd have to explicitly include {core/macros/} to get the macros. 20181110 02:35:01< celticminstrel> I could be wrong about that, though. 20181110 02:36:32<+wesdiscordbot> I just see that happened my _main.cfg was not executed because I load the core, but because the add-on is read 20181110 02:37:10<+wesdiscordbot> resulting in a bunch of redefinition warnings 20181110 02:39:23< celticminstrel> So about the possible impending 1.15.0 release, is that going to be a "stable" release for the start of rolling whatevers, or a "dev" release? 20181110 02:40:27<+wesdiscordbot> I guess that'd be a question for @Vultraz 20181110 02:42:06<+wesdiscordbot> I guess everybody forgot that there was a discussion about that 20181110 02:42:32< celticminstrel> Or didn't know in the first place. 20181110 02:42:58< celticminstrel> All the discussions I remember never came to a definitive conclusion. 20181110 02:44:04<+wesdiscordbot> Because we all have different opinions on the matter 20181110 02:44:23<+wesdiscordbot> And the best part is that everyone gets pissed when someone such as vultraz has to break the tie 20181110 02:44:30< celticminstrel> Heh. 20181110 02:44:47<+wesdiscordbot> I'm not a fan of the idea of rolling releases with the current platform we have 20181110 02:45:17<+wesdiscordbot> It'll just result in a mess where 85% of add-ons don't work correctly and players will blame the development team instead of the content authors 20181110 02:45:45< celticminstrel> If 1.15.0 is going to be a rolling release, we need to make a prerelease like right now to try and avoid that. 20181110 02:45:51<+wesdiscordbot> We had a variation on this with 1.10 because we stuck to using the 1.9 add-ons server 20181110 02:46:13<+wesdiscordbot> So the server was neither replaced nor reset and there were heaps of broken add-ons by the time 1.10.0 was released 20181110 02:47:00<+wesdiscordbot> (I don't remember if it was an intentionalk experiment or a massive oversight) 20181110 02:47:41<+wesdiscordbot> Changed APIs, changed semantics, changed image paths, you name it 20181110 02:48:08<+wesdiscordbot> It doesn't help that the Khalifate were added for a couple of development version and then pulled out before tagging beta 1 20181110 02:48:25<+wesdiscordbot> So some add-ons that depended on it or its resources got broken as well 20181110 02:49:18<+wesdiscordbot> I think the reason the 1.15.0 is announced is that the big paster PR is done, and a 1.15.0 release could be made anytime now... and, i think that's all. What came me to mind is that 1.15.0 doesn't really have soemthing to show of, or something to test, because we backported nearly everything... 2-3 new units and WML tags... 20181110 02:49:26<+wesdiscordbot> how would a rolling release work with trying to make balance changes to the dunefolk? 20181110 02:49:46<+wesdiscordbot> I don't know Pent. How do you make users play development versions? 20181110 02:50:08<+wesdiscordbot> Because we tried everything we could think of for the last 6 years 20181110 02:50:14< celticminstrel> Huh? Was 1.15.0 announced? 20181110 02:50:20<+wesdiscordbot> No 20181110 02:50:32<+wesdiscordbot> The Crazy MP People are the worst because they whine about changes all the time but don't help test 20181110 02:50:33<+wesdiscordbot> the API level thing which was dicussed did take care of how to make new tags available in stable releases, but overlooked balance changes 20181110 02:50:36< celticminstrel> 1.15.0 has some things to show off. 20181110 02:50:39<+wesdiscordbot> When they do help test they just go "ew bugs" and leave 20181110 02:50:42< celticminstrel> But I guess it's not a lot, sure. 20181110 02:51:14<+wesdiscordbot> Trying to come up with a killer feature to make people play dev is a waste of time 20181110 02:51:43<+wesdiscordbot> I did a lot back in the day to advertise the crazy stuff we were doing in 1.11.x and 1.13.x (as long as that lasted, anyway), nobody cares 20181110 02:52:27<+wesdiscordbot> The MP people just gravitate to where there's more people to play games with 20181110 02:52:35<+wesdiscordbot> So it's a chicken-and-egg issue 20181110 02:52:53<+wesdiscordbot> "we need to make more people play dev but in order to do that we need to have more people playing dev" 20181110 02:52:57<+wesdiscordbot> "(and less bugs)" 20181110 02:53:25<+wesdiscordbot> Also do look at things from the perspective of the average player 20181110 02:53:34<+wesdiscordbot> The average player is not anything like us 20181110 02:53:54<+wesdiscordbot> If they encounter a bug in a software application they are not going to report it unless they paid for it 20181110 02:54:10<+wesdiscordbot> They are just going to tell their friends "hey XYZ is shit, don't use it" 20181110 02:54:17<+wesdiscordbot> And that's exactly what people do with development releases 20181110 02:54:51<+wesdiscordbot> We literally had one person on this Discord not too long ago (not gonna name names but the people who follow mod topics should know exactly who I am talking about) who literally told people to not play 1.14 beta/RC/early GA because of all the bugs 20181110 02:56:47<+wesdiscordbot> ...is there an upside left of making 1.15.0? 20181110 02:57:12<+wesdiscordbot> I see no benefit to releasing 1.15.0 now 20181110 02:58:20< celticminstrel> Then when? 20181110 02:59:29<+wesdiscordbot> Yeah either way I'm genuinely curious if master has anything new to bring to the plate right now or it's just intangible refactoring and architectural changes 20181110 02:59:42<+wesdiscordbot> Or in common parlance, "boring nerd crap" 20181110 03:00:03<+wesdiscordbot> I would ask why you’re so anxious to see it 20181110 03:01:41<+wesdiscordbot> it would be good to show that development is still happening. 20181110 03:01:43< celticminstrel> According to the changelog there are quite a few new WML changes. 20181110 03:01:50< celticminstrel> s/changes/features/ 20181110 03:02:06< celticminstrel> The changelog might have things missing though. The new units aren't there, for example. 20181110 03:02:37<+wesdiscordbot> With AR gone, the Help refactor gone, and internal refactorings that may or may not be gone but can be set aside for this discussion, there really isn’t much there 20181110 03:03:41< celticminstrel> Have you even looked at the changelog? 20181110 03:03:54< celticminstrel> There's lots of new WML features. 20181110 03:04:03< celticminstrel> Admittedly that's not very useful for players, but... 20181110 03:04:05<+wesdiscordbot> WML changes fall under boring nerd crap umbrella 20181110 03:04:16<+wesdiscordbot> *the 20181110 03:04:30<+wesdiscordbot> Indeed 20181110 03:04:57<+wesdiscordbot> Here’s an exciting new release with... API features! 20181110 03:05:05<+wesdiscordbot> Content creators make stuff for players 20181110 03:05:22<+wesdiscordbot> If they don't have an audience they'll stick to 1.14 as well 20181110 03:05:47<+wesdiscordbot> What happened to the plans to add a drake campaign to mainline? 20181110 03:05:58<+wesdiscordbot> WML changes are not that useful for author yet, because why should they port their add-on to x.y.0 ... the're still busy porting to 1.14.x 20181110 03:06:05< celticminstrel> I think Sigurd is still working on that. 20181110 03:06:16< celticminstrel> And fair enough sevu. 20181110 03:08:02<+wesdiscordbot> is totally busy porting her add-ons to 1.14 still 20181110 04:04:30<+wesdiscordbot> I figured out the core stuff 20181110 04:05:07<+wesdiscordbot> One can easily segfault the game by not including some vital things… but guess that's fine 20181110 04:05:36<+wesdiscordbot> There's one where I would prefer an error message though... I think I open an issue tomorrow 20181110 04:08:10<+wesdiscordbot> And onethink is not clear to me – in the _server.pbl add-ons specify which core they need. But, wasn't the _server.pbl only for uploading. How does the game know to which core an add-on (or scenario) belongs. 20181110 04:21:51<+wesdiscordbot> @Vultraz Why not release 1.15.0 as a dev release (like 1.13.0) 20181110 04:22:06<+wesdiscordbot> The exciting new features only need to be in place for 1.16.0 20181110 04:41:09< celticminstrel> @sevu - I'd prefer error messages for all of them really. 20181110 04:41:31< celticminstrel> Do cores specify defines? 20181110 04:42:23<+wesdiscordbot> to answer my earlier question: _info.cfg is the place 20181110 04:42:25< celticminstrel> @josteph - TBH I'd be fine with that. It could even be rolled out to Steam on a separate (beta) channel. Maybe that would draw in a few testers. 20181110 05:06:02<+wesdiscordbot> well, if we really want to get testers, we could always shut down the 1.14 MP server for a weekend and have the error message tell people to install 1.15... 20181110 05:07:43<+wesdiscordbot> >.> 20181110 05:07:44<+wesdiscordbot> is 1.15 forward compatible with 1.14 for savegames? for addons? 20181110 05:07:46< celticminstrel> ... 20181110 05:07:53< celticminstrel> Yeah no, don't do that. 20181110 05:08:03<+wesdiscordbot> I wasn't actually serious, guys 20181110 05:08:08< celticminstrel> Fair enough. 20181110 05:08:09<+wesdiscordbot> oh good 20181110 05:08:12<+wesdiscordbot> lol 20181110 05:08:26< celticminstrel> AFAIK there are no compatibility-breaking changes yet in 1.15.0. 20181110 05:08:36< celticminstrel> But I don't necessarily know everything. 20181110 05:08:55< celticminstrel> By that I mean it can probably load 1.14 saves and addons without any issues. 20181110 05:09:07<+wesdiscordbot> there's no guarantee of compatibility between dev and stable releases though 20181110 05:09:15<+wesdiscordbot> or even between minor dev releases 20181110 05:09:22<+wesdiscordbot> you think of 1.15 to 1.16 ? 20181110 05:09:28< celticminstrel> No guarantee, no. 20181110 05:09:55<+wesdiscordbot> of 1.15.0 to 1.15.1 20181110 05:11:48< celticminstrel> I guess "support saner units for some formatting options in [message]" is technically compatibility-breaking, but I doubt many people use those anyway. 20181110 05:11:49<+wesdiscordbot> I think I'm starting to see why people want rolling releases 20181110 05:16:25<+wesdiscordbot> they would be beneficial. the api really isn't set up in a way to make that supportable for UMC though. 20181110 05:16:31< celticminstrel> Rolling releases have their own problems mind you. We need to be much more careful not to commit broken things. 20181110 05:16:48< celticminstrel> Because with rolling releases we probably don't have the prerelease stage to iron out the bugs. 20181110 05:17:13<+wesdiscordbot> I thought we might do something like, a release every month, a change is stable if it has been out for 12 months 20181110 05:17:29<+wesdiscordbot> don't know if that's exactly rolling releases, or just 'frequent' releases. 20181110 05:17:44<+wesdiscordbot> the barriers are OOS and backwards incompatibility, I think? 20181110 05:18:05<+wesdiscordbot> the former kind of a case of the latter, really 20181110 05:18:11< celticminstrel> Well sort of. 20181110 05:19:01<+wesdiscordbot> the difference would be that forward compatible changes would get out sooner 20181110 05:19:07< celticminstrel> sevu: Are all the other details of how to make a core documented anywhere? 20181110 05:20:01<+wesdiscordbot> by the way, what work is planned that would make a 1.16 worthwhile? The drake campaigns are already available on the addon server, for example, so even when they're added to core that wouldn't get people to upgrade. 20181110 05:21:34< celticminstrel> I'm not really sure. 20181110 05:21:58-!- celticminstrel is now known as celmin|sleep 20181110 05:23:35<+wesdiscordbot> is jyrkive still working on opengl? 20181110 05:24:20<+wesdiscordbot> last commit 4 weeks ago https://github.com/wesnoth/wesnoth/commit/16f20d528677ed47225af68df05a5759175dbfcc 20181110 05:24:54<+wesdiscordbot> the branch is still based on old master 20181110 05:25:43<+wesdiscordbot> nothing is documented anywhere :p 20181110 05:26:57<+wesdiscordbot> 1) you need a file called cores.cfg in your add-on – the name must be hardcoded. The core(s) there mave nothing to do with _main.cfg, and are as well loaded when using --noaddons 20181110 05:27:03<+wesdiscordbot> well, does anyone have any ideas what 1.16 should be about? 20181110 05:28:14<+wesdiscordbot> 2) in that file are [core] tags (that's documented). Next step is figuring out to what to set the path value 20181110 05:29:10<+wesdiscordbot> can be e.g. path="~add-ons/slim_core/load.cfg" 20181110 05:29:29<+wesdiscordbot> or path="~add-ons/slim_core/core/" 20181110 05:30:41<+wesdiscordbot> 3) from there on one must load things like it is done in mainline data/_main.cfg 20181110 05:31:18<+wesdiscordbot> That's the part where one actually starts making his core different, some things will segfault though if you leave them out 20181110 05:31:20<+wesdiscordbot> @Pentarctagon (Even if we don't have a particular highlight for 1.16 we should still release it at some point, to release patches that haven't been backported to 1.14) 20181110 05:31:59<+wesdiscordbot> @sevu applause 20181110 08:49:56-!- boucman [~rosen@wesnoth/developer/boucman] has joined #wesnoth-dev 20181110 08:51:16<+wesdiscordbot> agh. all my hard work refactoring the dispatcher to remove boost::mpl is not trivially portable 20181110 08:57:07<+wesdiscordbot> May I ask what's the point of that change? It's not like depending on Boost.MPL is a problem. 20181110 08:57:21<+wesdiscordbot> It simplified the code greatly 20181110 08:58:33<+wesdiscordbot> See commit message https://github.com/wesnoth/wesnoth/commit/0b45363c9589c14984eed393305b3a5ac59b71ec 20181110 08:59:36<+wesdiscordbot> Ah, right. It was this template mess. I see. 20181110 09:00:41<+wesdiscordbot> Compile-time searching without extended constexpr is very difficult, and didn't even improve performance that much according to your tests. Why did mordante even bother? 20181110 09:01:05<+wesdiscordbot> Because mordante overengineered everything. 20181110 09:02:25<+wesdiscordbot> You see it in GUI2's design in general 20181110 09:02:47<+wesdiscordbot> many components like the generator classes could have probably been done a lot simpler 20181110 09:03:33<+wesdiscordbot> It seems like he was trying to create this all-encompassing API that would handle every single usecase from A to Z. 20181110 09:04:09<+wesdiscordbot> http://c2.com/xp/YouArentGonnaNeedIt.html 20181110 09:05:24<+wesdiscordbot> Indeed. 😐 20181110 09:07:08<+wesdiscordbot> Even better, see if someone else has already done it 😛 20181110 09:08:28<+wesdiscordbot> (t'is why I like npm) 20181110 09:09:45<+wesdiscordbot> As long as it's not brought too far... along all the useful packages, NPM also has stupid one-liner packages such as is-positive. 20181110 09:10:10<+wesdiscordbot> https://www.npmjs.com/package/is-positive 20181110 09:10:51<+wesdiscordbot> wat 20181110 09:12:20<+wesdiscordbot> who the hell can't perform a > 0 check themselves 😐 20181110 09:15:57<+wesdiscordbot> There is one NPM developer in particular, Jon Schlinkert, who develops this kind of one-liner packages, and uses them in his own higher-level packages. I believe it's a strategy to boost download numbers. He can brag to potential employers that his packages combined have millions of downloads per week. 20181110 09:16:38<+wesdiscordbot> (I'm not exaggerating. is-number alone reaches almost a million. Even our own server has it as a lower-level dependency, used by one package we need.) 20181110 09:17:40-!- smiley` [~smiley@115.84.141.234] has joined #wesnoth-dev 20181110 09:18:20<+wesdiscordbot> that's like saying I've written millions of lines of code because I pressed Enter that many times :bowman: 20181110 09:28:54-!- zookeeper [~lmsnie@wesnoth/developer/zookeeper] has joined #wesnoth-dev 20181110 10:03:48-!- stikonas [~gentoo@wesnoth/translator/stikonas] has joined #wesnoth-dev 20181110 10:20:11-!- stikonas [~gentoo@wesnoth/translator/stikonas] has quit [Remote host closed the connection] 20181110 10:45:53-!- smiley` [~smiley@115.84.141.234] has quit [Quit: Leaving] 20181110 12:28:14< celmin|sleep> @sevu Which parts segfault if you leave them out? Advanced prefs? 20181110 12:30:16<+wesdiscordbot> we're not reintroducing font scaling 20181110 12:30:31< celmin|sleep> Suddenly Vultraz says something dumb out of the blue. 20181110 12:31:02<+wesdiscordbot> just in case that's what you were referring to 20181110 12:31:20< celmin|sleep> Of course we're reintroducing font scaling. 20181110 12:31:28< celmin|sleep> Anyway that's not what I was referring to. 20181110 12:31:35<+wesdiscordbot> That's not your call. 20181110 12:31:43< celmin|sleep> Nor is it yours TBH. 20181110 12:31:49<+wesdiscordbot> Excuse me? 20181110 12:32:55< celmin|sleep> Anyway, that aside, do you intend to drive off the people who can't see that well and find our text too small? 20181110 12:33:16< celmin|sleep> Font scaling is an accessibility feature that means more people can play the game. Given that, why would you not add it? 20181110 12:33:42<+wesdiscordbot> I removed it because shit breaks when you use it. Scrollbars show up everywhere, text gets cut off, IIRC dialogs sometimes fail to show... 20181110 12:33:43-!- celmin|sleep is now known as celmin|away 20181110 12:33:52<+wesdiscordbot> It can be in series 2. 20181110 12:33:59<+wesdiscordbot> When we have an engine that better supports it. 20181110 12:34:03< celmin|away> Yeah, things break, especially in GUI1. 20181110 12:34:12<+wesdiscordbot> Perhaps I should have said, we're not readding it in series 1. 20181110 12:34:18< celmin|away> But they don't break that badly. 20181110 12:34:33<+wesdiscordbot> It looks horrendous and unprofessional. 20181110 12:34:46< celmin|away> And BTW, if you commit to series 2 (which hasn't happened yet), you no longer have any say over what happens to series 1. 20181110 12:34:58<+wesdiscordbot> Excuse me? 20181110 12:35:12< celmin|away> If you commit to series 2, you no longer have any say over what happens to series 1. 20181110 12:35:35<+wesdiscordbot> Says who? 20181110 12:35:57< celmin|away> Probably every developer who's not enthusiastic about jumping to series 2? 20181110 12:38:12<+wesdiscordbot> Well, series 2 has not, as you say, happened yet. So even by your own metrics I’m still in charge, and I’m saying we’re not going to shit a feature that is a nice thing to have but makes the experience of playing the game an absolute mess. 20181110 12:38:57< celmin|away> Well, I don't feel like arguing with you about it right now. Maybe later. 20181110 12:39:10<+wesdiscordbot> Ok where did that come from 20181110 12:39:15<+wesdiscordbot> I meant to say 20181110 12:39:17<+wesdiscordbot> Ship 20181110 12:39:20< celmin|away> XD 20181110 12:39:21<+wesdiscordbot> 😬 20181110 12:39:29< celmin|away> I was wondering about that. ;p 20181110 12:42:05<+wesdiscordbot> I agree with you it's a good thing to have. But it would be so much easier if we were like CSS and had UI elements defined in ems. Instead everything is defined in px and it just cannot scale well with our current tech. 20181110 12:43:44<+wesdiscordbot> Better to leave out the feature than to let the people who need the feature try to use it and have their game break 20181110 12:44:36< celmin|away> IMO the proper response to that is to make the game not break, rather than removing the feature (unless you're getting a stable release ready). 20181110 12:45:29<+wesdiscordbot> How exactly do you propose converting GUI2 and ThemeWML to font-relative measurements? 20181110 12:45:40< celmin|away> Why do you assume that's what's needed? 20181110 12:45:57< celmin|away> I mean, yes it might do the job, but that doesn't mean it's the only way. 20181110 12:46:11< celmin|away> Anyway, GUI2 isn't really a priority here. ThemeWML is the real problem. 20181110 12:46:21<+wesdiscordbot> No, GUI is also a major problem 20181110 12:46:25< celmin|away> GUI2 gets extra scrollbars and stuff, yes, but it usually still works. 20181110 12:46:51<+wesdiscordbot> Usually 20181110 12:47:43<+wesdiscordbot> And at best it's annoying and at worst it makes us look like amateur UX designers who popped out of the year 2005. 20181110 12:48:05< celmin|away> Better than not working at all. 20181110 12:48:15< celmin|away> That said ISTR there were some cases where parts of the UI didn't even show up? 20181110 12:48:26<+wesdiscordbot> IASTR. 20181110 12:48:31< celmin|away> So it's not like GUI2 is a problem. it's just... less of a problem than ThemeWML. 20181110 12:48:40< celmin|away> "I Also Seem To Recall"? 20181110 12:48:48< celmin|away> ^is not a problem 20181110 12:48:51<+wesdiscordbot> Yes 20181110 12:50:38<+wesdiscordbot> Seriously, why do you always assume when I make a decision it's frivolous? 20181110 12:51:14< celmin|away> Why do you think I'm assuming it's frivolous? 20181110 12:51:36<+wesdiscordbot> Your attitude conveys the fact. 20181110 12:51:43<+wesdiscordbot> Or rather, the impression 20181110 12:51:52< celmin|away> Hmm. 20181110 12:53:28<+wesdiscordbot> Almost every time I say something it's like "yeeaaaaaah no we're not doing that" 20181110 13:36:09-!- irker491 [~irker@wesnoth/umc-dev/bot/shikadibot] has joined #wesnoth-dev 20181110 13:36:09< irker491> wesnoth: newfrenchy83 wesnoth:master dbaf40239330 / data/scenario-test.cfg: Revert #3669 (#3698) https://github.com/wesnoth/wesnoth/commit/dbaf40239330e8934c9a9d274813ec219e577325 20181110 13:38:57-!- stikonas [~gentoo@wesnoth/translator/stikonas] has joined #wesnoth-dev 20181110 14:53:46< irker491> wesnoth/wesnoth:master Jyrki Vesterinen 386c19f0cf Mouse events: remove owning reference to AppVeyor: All builds passed 20181110 17:29:09<+wesdiscordbot> @Vultraz I think the point celmin was (trying) to make is that being in charge of the direction 1.x takes in the future while you've also been saying that the 2.0 prototype will replace 1.x entirely could be in some cases be contradictory. 20181110 17:55:09-!- irker491 [~irker@wesnoth/umc-dev/bot/shikadibot] has quit [Quit: transmission timeout] 20181110 18:04:28<+wesdiscordbot> Reading the way conversations go around here sometimes is really discouraging, I'm not gonna lie 20181110 18:05:15<+wesdiscordbot> In my case if I wanted to read this kind of stuff every single day I'd rather get into politics and get paid for it 20181110 18:06:29<+wesdiscordbot> I miss the old days when all we argued about was how fast we could fix bugs before a given deadline 20181110 18:18:33<+wesdiscordbot> The plan to add a drake campaign is still underway. I'm aiming to have a "fully armed & operational" beta version of WoV on the 1.14 add-on server in early December. 20181110 19:47:58-!- mattsc [~mattsc@wesnoth/developer/mattsc] has quit [Ping timeout: 245 seconds] 20181110 20:18:38-!- irker303 [~irker@wesnoth/umc-dev/bot/shikadibot] has joined #wesnoth-dev 20181110 20:18:38< irker303> wesnoth/wesnoth:master newfrenchy83 dbaf402393 Revert #3669 (#3698) AppVeyor: All builds passed 20181110 21:33:45< irker303> wesnoth: gfgtdf wesnoth:master 3c63b1e6de8a / data/lua/wml/modify_unit.lua: optimize modify_unit https://github.com/wesnoth/wesnoth/commit/3c63b1e6de8ae913f7aa2c6b3d06021f29382787 20181110 21:33:47< irker303> wesnoth: gfgtdf wesnoth:master 66a282a96be2 / src/ (5 files in 2 dirs): do not write unchanged unit attributes https://github.com/wesnoth/wesnoth/commit/66a282a96be288a284d12a71625868cee5b2dc6b 20181110 21:33:49< irker303> wesnoth: gfgtdf wesnoth:master 3bfe5c20410c / src/units/unit.cpp: fix movement loss after expire_modification https://github.com/wesnoth/wesnoth/commit/3bfe5c20410caa6856d98047cb483725506f388a 20181110 21:36:22< irker303> wesnoth: Severin Glöckner wesnoth:1.14 545a838525f0 / po/wesnoth-multiplayer/de.po: German translation: spelling fix https://github.com/wesnoth/wesnoth/commit/545a838525f0e88698ed7f55b65ff9152bdcc378 20181110 21:37:07< irker303> wesnoth: Severin Glöckner wesnoth:master fb8770a3d965 / po/wesnoth-multiplayer/de.po: German translation: spelling fix https://github.com/wesnoth/wesnoth/commit/fb8770a3d965c8bbf45556ab2575147033e160cd 20181110 22:08:13-!- sevu [~sevu@p54854E05.dip0.t-ipconnect.de] has joined #wesnoth-dev 20181110 22:10:23-!- mattsc [~mattsc@wesnoth/developer/mattsc] has joined #wesnoth-dev 20181110 22:31:31-!- zookeeper [~lmsnie@wesnoth/developer/zookeeper] has quit [Ping timeout: 244 seconds] 20181110 23:10:46< sevu> celmin|away, yes, and some more, I wrote them down in 3702 20181110 23:34:48< Ravana_> gfgtdf: https://github.com/wesnoth/wesnoth/commit/3c63b1e6de8ae913f7aa2c6b3d06021f29382787#diff-185af3e0ba161ba3b46295bde1eda483R10 those argument names are not those that are used in function 20181110 23:38:20< Ravana_> since it needs changed there anyways, then https://github.com/wesnoth/wesnoth/commit/3c63b1e6de8ae913f7aa2c6b3d06021f29382787#diff-185af3e0ba161ba3b46295bde1eda483R27 known 20181110 23:39:30<+wesdiscordbot> @Vultraz The reason people disagree with you so much is that you make decisions with no discussion. That's inherently antagonizing even when you're right and even to people who agree with you. --- Log closed Sun Nov 11 00:00:30 2018