[Wesnoth-bugs] [bug #14503] Player often can't see his own shadows and nightgaunts

Follow-up Comment #27, bug #14503 (project wesnoth): Okay, PR #987 submitted for the global invisible units alpha change you suggested. ___ Reply to this item at:

[Wesnoth-bugs] [bug #25653] Wesnoth 1.13.7 fails to compile on Gentoo Linux: nullptr was not declared, among other errors

Follow-up Comment #11, bug #25653 (project wesnoth): OK well then Gentoo must have a defective GCC 5.4.0. Works fine with all other packages (which says a lot given that I have over 1,500 packages installed, and with Gentoo Linux all packages are compiled from source) though so I doubt it's

[Wesnoth-bugs] [bug #25653] Wesnoth 1.13.7 fails to compile on Gentoo Linux: nullptr was not declared, among other errors

Follow-up Comment #10, bug #25653 (project wesnoth): For what it's worth, I can compile fine with gcc 5.4.0 with both scons and cmake on my Mint 18.1. Full version string is: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609 that said, make does report a couple warnings:

[Wesnoth-bugs] [bug #14503] Player often can't see his own shadows and nightgaunts

Follow-up Comment #26, bug #14503 (project wesnoth): Okay, great! You posted the relevant lines in this thread on March 20. I just changed the two instances of 0.5 to 0.6. ___ Reply to this item at:

[Wesnoth-bugs] [bug #14503] Player often can't see his own shadows and nightgaunts

Follow-up Comment #25, bug #14503 (project wesnoth): If/when Nightgaunt becomes animated, I imagine the artist would follow the pattern from Shadow. If not, I'll make sure it does! What exactly did you change in drawer.cpp? Since it's a more widely-used attribute, we could try it as a separate

[Wesnoth-bugs] [bug #25619] using invalid unit types in debug mode

Update of bug #25619 (project wesnoth): Category: Feature Request => Bug ___ Reply to this item at: ___ Message

[Wesnoth-bugs] [bug #14503] Player often can't see his own shadows and nightgaunts

Follow-up Comment #24, bug #14503 (project wesnoth): All right. I just didn't want to potentially have to go through this again with the nightgaunt. I can't think of any problem this could cause, and 1.13 is a development version after all. It could easily be reverted if someone found an issue

[Wesnoth-bugs] [bug #14503] Player often can't see his own shadows and nightgaunts

Follow-up Comment #23, bug #14503 (project wesnoth): I started PR #984 for this. I left Nightgaunt alone as the artist would set the alpha levels if/when the animation frames are added. I also imagine changing invisible units' alpha levels from 0.5 to 0.6 probably isn't a bad idea. But I don't

[Wesnoth-bugs] [bug #25658] Webpage - checksum and link checksum file

URL: Summary: Webpage - checksum and link checksum file Project: Battle for Wesnoth Submitted by: damark Submitted on: Fr 14 Apr 2017 12:31:43 UTC Category: Bug Severity: 3 -

[Wesnoth-bugs] [bug #25619] using invalid unit types in debug mode

Update of bug #25619 (project wesnoth): Status:None => Fixed Assigned to:None => vultraz ___ Follow-up Comment #3: Implemented:

[Wesnoth-bugs] [bug #25650] memleak when broken addon is installed

Follow-up Comment #1, bug #25650 (project wesnoth): So, I looked into this, and it seems like the preprocessor uses a very odd and complicated form of memory management. There are a ton of new allocations all over the place, so this will not be simple to solve...

[Wesnoth-bugs] [bug #25504] heap use after free in new addon manager (downloading addon)

Update of bug #25504 (project wesnoth): Status: Ready For Test => Fixed ___ Reply to this item at: ___ Message

[Wesnoth-bugs] [bug #25504] heap use after free in new addon manager (downloading addon)

Follow-up Comment #7, bug #25504 (project wesnoth): LGTM. Thanks! ___ Reply to this item at: ___ Message sent via/by Gna! http://gna.org/

[Wesnoth-bugs] [bug #25656] Assertion Failed error with incorrect controller attribute

Update of bug #25656 (project wesnoth): Status: Ready For Test => Fixed ___ Reply to this item at: ___ Message

[Wesnoth-bugs] [bug #25655] [story] use of [switch] no longer works

Update of bug #25655 (project wesnoth): Status: Ready For Test => Fixed ___ Reply to this item at: ___ Message