maiyannah on community.highlandarrow.com
This remote profile is registered on another site; see maiyannah's original profile page on community.highlandarrow.com.
-
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 23:20:44 EST
maiyannah
@purplehippo Ultimately the problem is human nature. Some people happily and readily learn and I don't mind those at all. Others want to act like their the best when they don't know shit. Wikis aren't really the cause of either, but they do enable the latter. -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 23:09:01 EST
maiyannah
@purplehippo Most game players are not really able to think laterally very well at all, which is funny since that's the skill you need most to excel at well-designed games. -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 22:56:56 EST
maiyannah
@purplehippo I find it so gratifying to help out people new to a game, personally. -
Halani Du Claire (halani)'s status on Wednesday, 16-Nov-2016 22:53:34 EST
Halani Du Claire
https://i.imgur.com/VT1UZyG.png -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 22:50:33 EST
maiyannah
New comment by maiyannah -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 22:48:34 EST
maiyannah
I always get those ones when I cant just carry for them, but hey, at least they went through the motions of learning the mechanics of CO in action. -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 22:47:53 EST
maiyannah
Team of five, only one other player is experienced, leaves immediately cause of "le scrubs", second one leaves a little later demoralized, still got through the Alert though. I actually find it so counterproductive when someone sneers at new players like that because thats how you get more experienced people in the queues - stick with em, teach em the mechanics. … -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 22:20:10 EST
maiyannah
I just want to stress that actually properly logging information in postActiv now will blow up logs for a production instance pretty fast if you leave LOG_DEBUG on. -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 22:04:35 EST
maiyannah
Phew. That was a productive stretch at least. -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 22:04:18 EST
maiyannah
Since LogFilter was moved to /modules/ in !postActiv's distribution now, you will want to make sure that the copy in /plugins/ gets deleted, so you do not have duplication. Git is not great about detecting this and you will run into problems if you have it in both places. -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 22:03:07 EST
maiyannah
Right, that concludes one round of making the log messages in !postActiv much more informative - all the information that postActiv's ServerException exceptions pass on will now be available in the postActiv log, which by default is in syslog With this change, I recommend that you use the LogFilter plugin to filter out LOG_DEBUG level messages if you don't need them… -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 21:45:44 EST
maiyannah
The bit I'm going to finish with tonight, is moving LogFilter into modules, because while it is modular and does operate on it's own, I think it should be part of the normal distribution, not a plugin.
I am also going to advise enabling it to choke down LOG_DEBUG in a production environment, in the INSTALL file -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 21:42:15 EST
maiyannah
Okay, all the other ones are ClientException based I think, so going to call it there for now, that was a good little spot of work but quite productive, especially since it will expose a lot more information about errors.
Making more informative messages will be the next piece of that puzzle, but I definitely made some good headway here. -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 21:38:09 EST
maiyannah
I was wrong, folding a few more in. -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 21:27:36 EST
maiyannah
Going to give a final once-over of the /lib/ dir but I *think* I've gotten all the ServerException children unified now. -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 21:26:47 EST
maiyannah
I think @verius will be happy that consolidating all the tiny loose ServerException child classes into a single file has cut like 20 or 30 tiny files out of the repo. -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 21:04:50 EST
maiyannah
@takeshitakenji Just trying to keep stuff to relevant log severity so people can filter accordingly. But LOG_DEBUG is EXTREMELY verbose now, as opposed to how everything was suppressed before.
Logs will become very large if you don't have them on logrotate.d -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 20:53:03 EST
maiyannah
A caveat to exposing all this information is you will WANT to use the logfilter plugin to filter out LOG_DEBUG in a production environment. postActiv will tell all things, now, at least once this is done. Anything that isn't a proper error will be in LOG_DEBUG, and that means it will be EXTREMELY VERBOSE. Which is a good thing when we're trying to debug these obs… -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 20:51:36 EST
maiyannah
A few minor gotchas here and there with things not inheriting from what they maybe should but otherwise this is progressing well. -
maiyannah (maiyannah)'s status on Wednesday, 16-Nov-2016 20:44:40 EST
maiyannah
Oh, NOW it wants to complain about adding the severity variable. Go figure. I know why though, I forgot there was the way to forward a previous exception, which the $severity parameter would have been taking the position of.