[warzone2100-dev] Launchpad bugs

2010-07-27 Thread Per Inge Mathisen
Hello list, I am seeing a lot of bug coming from launchpad to this list now. They are posted each with a unique email address (like 500...@bugs.launchpad.net), that are rejected since they are not subscribers. How should we handle these? (The admin panel shows 40 launchpad bug report emails awaiti

[warzone2100-dev] Release 2.3.2a or 2.3.2.1 or 2.3.3?

2010-07-27 Thread Guangcong Luo
Hey, guys. Two fairly bad bugs kind of went into 2.3.2 and no one found them. :( They are: 1. When a fully upgraded object takes burn damage, it's instantly killed (underflow in damage calculation). 2. Starting a game in T2 or T3 mode doesn't work - the game just starts in T1 mode. I've fixed bo

Re: [warzone2100-dev] Launchpad bugs

2010-07-27 Thread dak180
On Jul 27, 2010, at 3:01 AM, Per Inge Mathisen wrote: > Hello list, > > I am seeing a lot of bug coming from launchpad to this list now. They > are posted each with a unique email address (like > 500...@bugs.launchpad.net), that are rejected since they are not > subscribers. How should we handle

[warzone2100-dev] [Warzone 2100 Trac] #2022: crash in host room while chatting

2010-07-27 Thread Warzone 2100 Trac
#2022: crash in host room while chatting --+- Reporter: Terminator |Type: bug Status: new|Priority: major Milestone: unspecified| Component: other

[warzone2100-dev] [Warzone 2100 Trac] #2023: crash in host room while chatting

2010-07-27 Thread Warzone 2100 Trac
#2023: crash in host room while chatting --+- Reporter: Terminator |Type: bug Status: new|Priority: major Milestone: unspecified| Component: other

[warzone2100-dev] [Warzone 2100 Trac] #2024: crash during game

2010-07-27 Thread Warzone 2100 Trac
#2024: crash during game --+- Reporter: mp...@…|Type: bug Status: new|Priority: major Milestone: 2.3.2 | Component: other Version:

[warzone2100-dev] [Warzone 2100 Trac] #2026: crash in host room while chatting

2010-07-27 Thread Warzone 2100 Trac
#2026: crash in host room while chatting --+- Reporter: Terminator |Type: bug Status: new|Priority: major Milestone: unspecified| Component: other

[warzone2100-dev] [Warzone 2100 Trac] #2025: crash in host room while chatting

2010-07-27 Thread Warzone 2100 Trac
#2025: crash in host room while chatting --+- Reporter: Terminator |Type: bug Status: new|Priority: major Milestone: unspecified| Component: other

Re: [warzone2100-dev] Release 2.3.2a or 2.3.2.1 or 2.3.3?

2010-07-27 Thread Christian Ohm
On Tuesday, 27 July 2010 at 3:20, Guangcong Luo wrote: > 2. Starting a game in T2 or T3 mode doesn't work - the game just > starts in T1 mode. r11305 breaks loading maps in T1. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listi

Re: [warzone2100-dev] Release 2.3.2a or 2.3.2.1 or 2.3.3?

2010-07-27 Thread Per Inge Mathisen
Let's keep our cool for a bit and see if more bloopers surface before we rush to re-release anything. Then we can push out 2.3.3 next weekend, hopefully this time with some actual testing done. Although I cannot promise anything in that department -- Starcraft 2 just came out. - Per __

Re: [warzone2100-dev] Release 2.3.2a or 2.3.2.1 or 2.3.3?

2010-07-27 Thread Per Inge Mathisen
On Tue, Jul 27, 2010 at 3:22 PM, Per Inge Mathisen wrote: > next weekend I mean this weekend. - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev

[warzone2100-dev] [Warzone 2100 Trac] #2027: Pathfinding around obstacles not working - Trunk

2010-07-27 Thread Warzone 2100 Trac
#2027: Pathfinding around obstacles not working - Trunk ---+ Reporter: j0shdrunk0nwar |Type: bug Status: new |Priority: major Milestone: unspecified | C

Re: [warzone2100-dev] Our next release plan?

2010-07-27 Thread Kreuvf
Guangcong Luo wrote: > Most of the other problems with power flow I've been talking about the > past few days are fairly minor in comparison. I could probably get > used to them. But the one reason I listed above? That's not something > I could get used to, since I'd never be able to do the mental

Re: [warzone2100-dev] Our next release plan?

2010-07-27 Thread Per Inge Mathisen
On Mon, Jul 26, 2010 at 9:37 PM, Guangcong Luo wrote: > You'll notice on the forums quite a few people disagreed with the trunk power > system. I saw only quite a few people saw no reason to change anything, none of whom said they had actually tested trunk. That is only the to be expected level o

[warzone2100-dev] [Warzone 2100 Trac] #2028: Map opening problems in skirmish/2.3.2 (regression?)

2010-07-27 Thread Warzone 2100 Trac
#2028: Map opening problems in skirmish/2.3.2 (regression?) +--- Reporter: hao |Type: bug Status: new |Priority: major Milestone: unspecified | Component: other

[warzone2100-dev] ticket #2009 - Request for thoughts/feedback

2010-07-27 Thread Safety0ff
Hey all, I made some patches to fix the CFURLRef leaks under Mac and I'd like to know which solution you want used. My first patch (dir.diff) adds a function and moves some code in a new .h/.c file pair (makes main.c a little tidier). The added function removes duplicate code and accompanying

Re: [warzone2100-dev] Release 2.3.2a or 2.3.2.1 or 2.3.3?

2010-07-27 Thread Guangcong Luo
On Tue, Jul 27, 2010 at 7:36 AM, Christian Ohm wrote: > On Tuesday, 27 July 2010 at  3:20, Guangcong Luo wrote: >> 2. Starting a game in T2 or T3 mode doesn't work - the game just >> starts in T1 mode. > > r11305 breaks loading maps in T1. To be fair, it only breaks loading maps in T1 for some ma

Re: [warzone2100-dev] Release 2.3.2a or 2.3.2.1 or 2.3.3?

2010-07-27 Thread Stephen Swaney
On Tue, Jul 27, 2010 at 02:51:44PM -0500, Guangcong Luo wrote: > > To be fair, it only breaks loading maps in T1 for some maps, and Rush, > the map I usually test with, worked just fine. Anyway, I've fixed that > too, now. Just one more example of why programmers are the worst people to test thei

Re: [warzone2100-dev] Release 2.3.2a or 2.3.2.1 or 2.3.3?

2010-07-27 Thread Max Baldwin
At least they can write codeTesting should be done on SVN Branch 2.3? On Tue, Jul 27, 2010 at 15:23, Stephen Swaney wrote: > On Tue, Jul 27, 2010 at 02:51:44PM -0500, Guangcong Luo wrote: > > > > To be fair, it only breaks loading maps in T1 for some maps, and Rush, > > the map I usually

Re: [warzone2100-dev] Release 2.3.2a or 2.3.2.1 or 2.3.3?

2010-07-27 Thread Guangcong Luo
On Tue, Jul 27, 2010 at 3:23 PM, Stephen Swaney wrote: > Just one more example of why programmers are the worst people to test their > own code. Erm, well, that's true, but what's your point? -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org htt

[warzone2100-dev] [Warzone 2100 Trac] #2029: Crash in multisync.c:218, pickADroid()

2010-07-27 Thread Warzone 2100 Trac
#2029: Crash in multisync.c:218, pickADroid() -+-- Reporter: Fastdeath |Type: bug Status: new |Priority: major Milestone: unspecified

Re: [warzone2100-dev] Release 2.3.2a or 2.3.2.1 or 2.3.3?

2010-07-27 Thread buginator
On 7/27/10, Per Inge Mathisen <> wrote: > Let's keep our cool for a bit and see if more bloopers surface before > we rush to re-release anything. > > Then we can push out 2.3.3 next weekend, hopefully this time with some > actual testing done. Although I cannot promise anything in that > depart

Re: [warzone2100-dev] Release 2.3.2a or 2.3.2.1 or 2.3.3?

2010-07-27 Thread Guangcong Luo
On Tue, Jul 27, 2010 at 6:31 PM, buginator wrote: > On 7/27/10, Per Inge Mathisen <> wrote: >>  Then we can push out 2.3.3 next weekend, hopefully this time with some >>  actual testing done. Although I cannot promise anything in that >>  department -- Starcraft 2 just came out. > > Per, I expect

[warzone2100-dev] 2.3.2a (or whatever) timeout period for sockets

2010-07-27 Thread buginator
Currently, we wait 2500ms for some sockets, and wait forever for other sockets (which you may have noticed when the game "froze" on you), so the question is, for reading the sockets, do we wait 2500ms as well, or make it more or less ? Remember, the higher the value, the longer the game waits for

Re: [warzone2100-dev] 2.3.2a (or whatever) timeout period for sockets

2010-07-27 Thread Guangcong Luo
On Tue, Jul 27, 2010 at 10:41 PM, buginator wrote: > Currently, we wait 2500ms for some sockets, and wait forever for other > sockets (which you may have noticed when the game "froze" on you), so > the question is, for reading the sockets, do we wait 2500ms as well, > or make it more or less ? > >

Re: [warzone2100-dev] 2.3.2a (or whatever) timeout period for sockets

2010-07-27 Thread buginator
On 7/27/10, Guangcong Luo <> wrote: > On Tue, Jul 27, 2010 at 10:41 PM, buginator <> wrote: > > Currently, we wait 2500ms for some sockets, and wait forever for other > > sockets (which you may have noticed when the game "froze" on you), so > > the question is, for reading the sockets, do we wai

Re: [warzone2100-dev] 2.3.2a (or whatever) timeout period for sockets

2010-07-27 Thread Guangcong Luo
On Tue, Jul 27, 2010 at 10:46 PM, buginator wrote: > Not for 2.3.x > That would require tons more work / testing. Okay, then. 2.5 seconds seems fine. -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-de