[warzone2100-dev] [Warzone 2100 Trac] #978: warzone crash due to asserting of non existing path
#978: warzone crash due to asserting of non existing path +--- Reporter: anonymous|Type: defect Status: new |Priority: minor Milestone: unspecified | Component: other Version: 2.2.3|Keywords: Operating_system: Mac OS | Blockedby: Blocking: | +--- sine my username is not zarel this seems to be a bug (maybe someone used an absolute path for testing?): 04.10.09 17:28:01 [0x0-0xd70d7].net.wz2100.Warzone[1822] error |05:28:01: [interpRunScript] Assert in Warzone: /Users/zarel/Warzone/warzone2100-2.2.3/macosx/../lib/script/interpreter.c:946 (!error while executing a script), last script event: 'enm2bStartTrig (CODE)' Cheers, Thorsten -- Ticket URL: http://developer.wz2100.net/ticket/978 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Resurrection Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] [Warzone 2100 Trac] #605: You are asking too much power assert failure
#605: You are asking too much power assert failure +--- Reporter: Per | Owner: gerard_ Type: defect | Status: closed Priority: blocker | Milestone: 2.3 Component: Engine: Resource Management | Version: svn/trunk Resolution: fixed|Keywords: power Operating_system: All/Non-Specific | Blockedby: Blocking: | +--- Changes (by gitsvngateway): * status: new = closed * resolution: = fixed Comment: (In [8204]) Remove the you are asking too much power assert, as it is sometimes legitimate to ask for a lot of power (after lagging for a few seconds in multiplayer for example). Fixes bug 605 and fixes bug 401. From: Gerard Krol gera...@gna.org -- Ticket URL: http://developer.wz2100.net/ticket/605#comment:8 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Resurrection Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Version scheme (again)
After a quick discussion on IRC, I would like to propose a different versioning. I'd like to see a trunk alpha soon. However, since trunk does not yet contain the big incompatibilities that we foresaw for 3.0 (new savegame format, lua port), we should wait with the major version bump. So we should call the next big release 2.4. Then we reserve the 2.3 number space for a possible 2.2+incompatible net changes version in the future. Once we've done some MP test games among the developers, I would like to branch off and start making the first release from trunk as 2.4-alpha1. Opinions? - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Version scheme (again)
On Sun, Oct 4, 2009 at 3:07 PM, Per Inge Mathisen per.mathi...@gmail.com wrote: After a quick discussion on IRC, I would like to propose a different versioning. I'd like to see a trunk alpha soon. However, since trunk does not yet contain the big incompatibilities that we foresaw for 3.0 (new savegame format, lua port), we should wait with the major version bump. So we should call the next big release 2.4. Then we reserve the 2.3 number space for a possible 2.2+incompatible net changes version in the future. I'm fine with this. Once we've done some MP test games among the developers, I would like to branch off and start making the first release from trunk as 2.4-alpha1. Isn't trunk still really unstable? Have we fixed the commanders bug yet? -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Version scheme (again)
On 10/4/09, Per Inge Mathisen per.xx...@gmail.com wrote: After a quick discussion on IRC, I would like to propose a different versioning. I'd like to see a trunk alpha soon. However, since trunk does not yet contain the big incompatibilities that we foresaw for 3.0 (new savegame format, lua port), we should wait with the major version bump. So we should call the next big release 2.4. Then we reserve the 2.3 number space for a possible 2.2+incompatible net changes version in the future. Once we've done some MP test games among the developers, I would like to branch off and start making the first release from trunk as 2.4-alpha1. Opinions? Works for me (tm) Oh how I look forward to uploading 100+MB with my slow bandwidth :P ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] [Warzone 2100 Trac] #979: Please insert disc 1 or 2!
#979: Please insert disc 1 or 2! --+- Reporter: cpnm...@… |Type: defect Status: new|Priority: major Milestone: unspecified| Component: other Version: unspecified|Keywords: Operating_system: All/Non-Specific | Blockedby: Blocking: | --+- When I click on any menu option I get the above message. Previous version worked fine! I'm running on XP -- Ticket URL: http://developer.wz2100.net/ticket/979 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Resurrection Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] [Warzone 2100 Trac] #930: lua branch very out of date
#930: lua branch very out of date +--- Reporter: Kosh| Owner: gerard_ Type: task| Status: assigned Priority: major | Milestone: unspecified Component: Engine: Scripting / AI |Version: unspecified Keywords: lua | Operating_system: All/Non-Specific Blockedby: 139 | Blocking: +--- Changes (by gerard_): * owner: = gerard_ * status: new = assigned Comment: Hello Kosh, Thanks for your interest in the lua branch (lua2). I've spent quite some time on it and do not intend to let it die. As I've just started with my first full-time job after a busy summer, I haven't spent a lot of time on it lately. I have just merged in the changes from trunk. The reason the code is not yet in trunk is that it is not completely finished. Skirmish with the default ai is playable but the campaign and AIVOLUTION have not yet been tested thoroughly enough. I'd welcome any help with coding/testing. The mailing list is a good place for these kinds of discussions but I think it would be best to meet on IRC. (#warzone2100-dev on freenode) I think there will be a 50% chance of finding me on a given evening for the next two weeks. I'm usually there from 8-22 CET. Regards, Gerard -- Ticket URL: http://developer.wz2100.net/ticket/930#comment:4 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Resurrection Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] 2.2.4 (or 2.3.0) is planned to be released next weekend
Hey all, the current plan is to release 2.2.4 (or 2.3.0--which ever version # wins) next weekend, most likely Saturday night/ Sunday morning. If you have fixes/changes, then please get them in now, or wait for the next release. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] 2.2.4 (or 2.3.0) is planned to be released next weekend
On Sun, Oct 4, 2009 at 5:44 PM, bugs buggy buginato...@gmail.com wrote: Hey all, the current plan is to release 2.2.4 (or 2.3.0--which ever version # wins) next weekend, most likely Saturday night/ Sunday morning. If you have fixes/changes, then please get them in now, or wait for the next release. D: D: D: BLOCK We are not rushing out a netcode-imcompatible release that soon, no no no! -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] 2.2.4 (or 2.3.0) is planned to be released next weekend
On 10/4/09, Zarel zarexx...@gmail.com wrote: On Sun, Oct 4, 2009 at 5:44 PM, bugs buggy buginato...@gmail.com wrote: Hey all, the current plan is to release 2.2.4 (or 2.3.0--which ever version # wins) next weekend, most likely Saturday night/ Sunday morning. If you have fixes/changes, then please get them in now, or wait for the next release. D: D: D: BLOCK We are not rushing out a netcode-imcompatible release that soon, no no no! Why? Look at the code, it isn't that complex in what it does, and now that it is in both trunk branch/2.2, we can have plenty of testing before the release of the next version next week... Hear that testers? We need your help :) In case everyone is confused on how this works, if host starts a game with ntw mod, they would do --mod_mp ntw (if from source) or --mod_mp ntw.wz then that loads the ntw mod. Now when they host, all players *must* also have --mod_mp ntw or --mod_mp ntw.wz (depending if they are running from source or not) and then, once in game, it checks the data, and kicks everyone who doesn't have matching data. If host just starts a normal game with no mods, and a player is using a mod, the data check will see this, and kick the player(s). Like I said, this isn't really that complicated, and it was in Pumpkin's original codebase + a few changes so it runs on all platforms. Anyway, I will be back next week. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] 2.2.4 (or 2.3.0) is planned to be released next weekend
On 10/4/09, bugs buggy buginxxx...@gmail.com wrote: ... now that it is in both trunk branch/2.2, we can have plenty of testing before the release of the next version next week... Hear that testers? We need your help :) I uploaded both 2.2 trunk versions (.exe ONLY) as of this e-mail to the forums here: http://forums.wz2100.net/viewtopic.php?f=6t=3895start=0 Feel free to tell people to test it. Anyway, I will be back next week. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
