[warzone2100-dev] [Warzone 2100 Trac] #1375: Make kicks have more force
#1375: Make kicks have more force +--- Reporter: Zarel | Owner: Type: patch | Status: new Priority: major | Milestone: 2.3 Component: Engine: Networking |Version: svn/2.3 Keywords: netcode kick| Operating_system: All/Non-Specific Blockedby: | Blocking: +--- It seems some cheaters are using modified game binaries to ignore kick messages. Well, here's a patch that makes kicks have a bit more force. A player will get kicked whether he/she agrees to it or not. Feedback welcome. I'll commit in a few days (well, at least 20 hours) unless there are objections. -- Ticket URL: http://developer.wz2100.net/ticket/1375 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Beta 7
On Fri, Jan 8, 2010 at 3:48 AM, Per Inge Mathisen per.mathi...@gmail.com wrote: I wrote: I think we need a better way to inform the user of why he cannot join games (because there is an autoload mod in his folders) before this is committed. There was no response to this, nor any new patch that addresses this point. We had nightmares with the previous autoload feature because some users had no idea what mods they had loaded, and when they got errors they blamed us. We do not need that noise. ...the current system is just as bad because users still have no idea what mods they need to have loaded, and all the game says is you were kicked because data doesn't match in stderr.txt. Easy mod support is not that important. There may be vocal forum users that want it, but they are rarely a good representative sample of our users. In my experience, the overwhelming majority of users will never touch a mod and just play the core game. Forum activity has gone down significantly, and I miss many formerly active members. Good mod support is key to an active community, and I fear our current mod loading situation may have something to do with it. I would not have released Rebalance Mod and eventually become a developer if not for the ease of autoload folders. No, testing of new features is what _trunk_ is for. We do not need to push testing on to end users when we could have found the bugs ourselves by having other developers running the game. Because we all know how often developers do that. (cough campaign cough) On the subject of campaign, I think the main parts that need testing are away missions, recalling reinforcements, campaign-to-campaign transitions, and the map size expansions (and reductions in some gamma stages). If users provided a set of savegames for those scenarios, I bet it wouldn't be too difficult to test to ensure a base minimum of playability. -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Beta 7
On Fri, Jan 8, 2010 at 10:03 AM, Christian Ohm chr@gmx.net wrote: Which would be easier if the savegame format wouldn't be that easy to break. I've started the campaign several times, but didn't get any farther than a few missions before someone broke the savegames again, so had to start over... ...really? I thought we haven't changed campaign savegames since like 2.1-era. -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Beta 7
On Friday, 8 January 2010 at 10:22, Guangcong Luo wrote: I thought we haven't changed campaign savegames since like 2.1-era. Tells you how fast I play. And probably the fact that it broke annoyed me so that I started the next try shortly before the next breakage. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Beta 7
Am Freitag, 8. Januar 2010 01:27:51 schrieb Stephen Swaney: On Thu, Jan 07, 2010 at 05:54:10PM -0600, Guangcong Luo wrote: On Thu, Jan 7, 2010 at 5:03 PM, Per Inge Mathisen per.mathi...@gmail.com wrote: Other than that, I would strongly recommend not pushing any further features into the release branch. The whole point of consecutive beta releases is to squeeze out the last remaining bugs in preparation for an actual released version. Every time you add a new feature, you create the possibility of new bugs. (see the last couple betas for an example) Adding a new feature essentially resets the Beta counter back to one. Not a good way to make progress. +1 --devu signature.asc Description: This is a digitally signed message part. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Beta 7
Hello! Am Freitag, 8. Januar 2010 01:32:29 schrieb Guangcong Luo: On Thu, Jan 7, 2010 at 6:27 PM, Stephen Swaney sswa...@centurytel.net wrote: The whole point of consecutive beta releases is to squeeze out the last remaining bugs in preparation for an actual released version. Every time you add a new feature, you create the possibility of new bugs. (see the last couple betas for an example) Adding a new feature essentially resets the Beta counter back to one. Not a good way to make progress. Fine, I'll write a simpler version of my mod loading patch for the 2.3 release. _Something_ about it needs to change. I consider the current mod loading system a bug in its own right. If you are so eager to integrate new features: Get 2.3 tested and stable quickly, integrate your features into trunk meanwhile and then start pusing out 2.4. --devu signature.asc Description: This is a digitally signed message part. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Beta 7
On Fri, Jan 08, 2010 at 03:59:17AM -0600, Guangcong Luo wrote: On Fri, Jan 8, 2010 at 3:48 AM, Per Inge Mathisen per.mathi...@gmail.com wrote: Easy mod support is not that important. There may be vocal forum users that want it, but they are rarely a good representative sample of our users. In my experience, the overwhelming majority of users will never touch a mod and just play the core game. Forum activity has gone down significantly, and I miss many formerly active members. I can think of at least 3 people who have stopped participating in the last couple months due to what they perceived as hostility on the forums. No mention of autoloading. Good mod support is key to an active community, and I fear our current mod loading situation may have something to do with it. I would not have released Rebalance Mod and eventually become a developer if not for the ease of autoload folders. Mod support is a nice thing to have, but a working game that does not crash is even more important. It should be embarrassing that we are up to Beta 7. The techniques for producing working software are not rocket science. All it requires is a little bit of process and some personal discipline. -- Stephen Swaney sswa...@centurytel.net ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] [Warzone 2100 Trac] #1376: nexus turrent Assert
#1376: nexus turrent Assert --+- Reporter: Ai_Tak |Type: bug Status: new|Priority: major Milestone: unspecified| Component: Engine: other Version: 2.3 beta 5 (unsupported!) |Keywords: nexus Operating_system: All/Non-Specific | Blockedby: Blocking: | --+- I took over a few AI structures near some of their oil wells, they sent a truck to build more defenses, the truck was building something before it was destroyed (rather than taken over). Nexus attacks were then focused on the partially complete structure. I'm not sure if it still accruing power or if the build process was actually started (I thought accruing before building had been eliminated...) If it wasn't finished accruing, then it would have disappeared eventually. It did disappear after a short time, but I'm not sure what caused it. The game crashed the instant it disappeared. stderr.txt: error |04:06:42: [justBeenHitByEW] justBeenHitByEW: unknown object type error |04:06:42: [justBeenHitByEW] Assert in Warzone: ../../../src/projectile.c:1941 (!unknown object type), last script event: '16 (CALL_STRUCT_DESTROYED)' -- Ticket URL: http://developer.wz2100.net/ticket/1376 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] [Warzone 2100 Trac] #1377: Challenge timer not loaded from savegame
#1377: Challenge timer not loaded from savegame ---+ Reporter: Per| Owner: Type: bug| Status: new Priority: minor | Milestone: 2.3 Component: Engine: other |Version: svn/2.3 Keywords: | Operating_system: All/Non-Specific Blockedby: | Blocking: ---+ When saving and loading a challenge, the timer is not restored. -- Ticket URL: http://developer.wz2100.net/ticket/1377 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] [Warzone 2100 Trac] #1378: Mouse cursor get stuck in top-left corner of desktop after alt+tab
#1378: Mouse cursor get stuck in top-left corner of desktop after alt+tab --+- Reporter: Terminator |Type: bug Status: new|Priority: major Milestone: 2.3| Component: other Version: 2.3 beta 6 |Keywords: cursor stuck Operating_system: Microsoft Windows | Blockedby: Blocking: | --+- Mouse cursor get stuck in the top-left corner of desktop after alt+tab from fullscreen mode with Colored Cursor=ON in windows xp sp3. -- Ticket URL: http://developer.wz2100.net/ticket/1378 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] [Warzone 2100 Trac] #1379: Can't load third sector, crashes after video
#1379: Can't load third sector, crashes after video +--- Reporter: goofy1...@… |Type: bug Status: new |Priority: major Milestone: unspecified | Component: Campaign Version: 2.3 beta 6 |Keywords: Operating_system: Mac OS | Blockedby: Blocking: | +--- Interval Since Last Report: 516435 sec Crashes Since Last Report: 103 Per-App Interval Since Last Report: 20960 sec Per-App Crashes Since Last Report: 10 Anonymous UUID: 69ED3EC9-CE9E-4D60-B9C8-5DA61D0CBFBE Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x, 0x Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: abort() called Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x95bb3732 __kill + 10 1 libSystem.B.dylib 0x95bb3724 kill$UNIX2003 + 32 2 libSystem.B.dylib 0x95c4698d raise + 26 3 libSystem.B.dylib 0x95c5ca44 abort + 93 4 net.wz2100.Warzone 0x0017e15d __eprintf + 77 5 net.wz2100.Warzone 0x001405a9 visRemoveVisibility + 384 6 net.wz2100.Warzone 0x000ea298 objmemDestroy + 214 7 net.wz2100.Warzone 0x000ea3a9 objmemUpdate + 35 8 net.wz2100.Warzone 0x000bd81d gameLoop + 1883 9 net.wz2100.Warzone 0x000be8b9 mainLoop + 362 10 net.wz2100.Warzone 0x000bf52f SDL_main + 2575 11 net.wz2100.Warzone 0x0017d8d7 -[SDLMain applicationDidFinishLaunching:] + 76 12 com.apple.Foundation0x90eff270 _nsnote_callback + 345 13 com.apple.CoreFoundation0x951879a9 __CFXNotificationPost + 905 14 com.apple.CoreFoundation0x951873da _CFXNotificationPostNotification + 186 15 com.apple.Foundation0x90ef4094 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128 16 com.apple.Foundation0x90f01471 -[NSNotificationCenter postNotificationName:object:] + 56 17 com.apple.AppKit0x962e673a -[NSApplication _postDidFinishNotification] + 125 18 com.apple.AppKit0x962e664a -[NSApplication _sendFinishLaunchingNotification] + 74 19 com.apple.AppKit0x9643d595 -[NSApplication(NSAppleEventHandling) _handleAEOpen:] + 274 20 com.apple.AppKit0x9643d1b5 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 101 21 com.apple.Foundation0x90f34404 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 511 22 com.apple.Foundation0x90f341c8 _NSAppleEventManagerGenericHandler + 228 23 com.apple.AE0x992d0f3a aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 166 24 com.apple.AE0x992d0e39 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 43 25 com.apple.AE0x992d0d46 aeProcessAppleEvent + 197 26 com.apple.HIToolbox 0x953852a1 AEProcessAppleEvent + 50 27 com.apple.AppKit0x962b6d02 _DPSNextEvent + 1420 28 com.apple.AppKit0x962b6306 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156 29 com.apple.AppKit0x9627849f -[NSApplication run] + 821 30 net.wz2100.Warzone 0x0017e0d8 main + 1702 31 net.wz2100.Warzone 0x2e1a _start + 216 32 net.wz2100.Warzone 0x2d41 start + 41 Thread 1: Dispatch queue: com.apple.libdispatch-manager 0 libSystem.B.dylib 0x95b790ea kevent + 10 1 libSystem.B.dylib 0x95b79804 _dispatch_mgr_invoke + 215 2 libSystem.B.dylib 0x95b78cc3 _dispatch_queue_invoke + 163 3 libSystem.B.dylib 0x95b78a68 _dispatch_worker_thread2 + 234 4 libSystem.B.dylib 0x95b784f1 _pthread_wqthread + 390 5 libSystem.B.dylib 0x95b78336 start_wqthread + 30 Thread 2: 0 libSystem.B.dylib 0x95b529ee mach_wait_until + 10 1 libSystem.B.dylib 0x95bda9e5 nanosleep + 345 2 SDL 0x00ede5c3 SDL_Delay + 467 3 SDL 0x00ecfecd SDL_Linked_Version + 397 4 SDL 0x00ede1f1 SDL_SemWait + 49 5 libSystem.B.dylib 0x95b7ffbd _pthread_start + 345 6 libSystem.B.dylib
[warzone2100-dev] [Warzone 2100 Trac] #1380: game crash third campain
#1380: game crash third campain --+- Reporter: fascikla...@… |Type: bug Status: new|Priority: critical Milestone: unspecified| Component: Campaign Version: 2.3 beta 6 |Keywords: Game crash Operating_system: Microsoft Windows | Blockedby: Blocking: | --+- Game crashes after video introduction to thid campain, imediatly after video crashes every time. i have save game so check it. -- Ticket URL: http://developer.wz2100.net/ticket/1380 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] [Warzone 2100 Trac] #1381: Joining a game crashes Warzone, but it remains open
#1381: Joining a game crashes Warzone, but it remains open --+- Reporter: warzonelego|Type: bug Status: new|Priority: major Milestone: unspecified| Component: Engine: Networking Version: 2.3 beta 6 |Keywords: Operating_system: Microsoft Windows | Blockedby: Blocking: | --+- Reproducing: 1. Join a 2.3 beta 6 game 2. BANG! Sometimes this doesn't happen. -- Ticket URL: http://developer.wz2100.net/ticket/1381 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Beta 7
Stephen Swaney wrote: The whole point of consecutive beta releases is to squeeze out the last remaining bugs in preparation for an actual released version. Every time you add a new feature, you create the possibility of new bugs. (see the last couple betas for an example) Adding a new feature essentially resets the Beta counter back to one. Not a good way to make progress. +1 - Kreuvf signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
