You can subscribe to this list here.
2012 |
Jan
|
Feb
(37) |
Mar
(140) |
Apr
(73) |
May
(89) |
Jun
(78) |
Jul
(66) |
Aug
(75) |
Sep
(24) |
Oct
(48) |
Nov
(49) |
Dec
(36) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2013 |
Jan
(82) |
Feb
(48) |
Mar
(30) |
Apr
(10) |
May
(24) |
Jun
(7) |
Jul
(8) |
Aug
(23) |
Sep
(23) |
Oct
(26) |
Nov
(32) |
Dec
(36) |
2014 |
Jan
(14) |
Feb
(10) |
Mar
(9) |
Apr
(8) |
May
(6) |
Jun
(2) |
Jul
(3) |
Aug
|
Sep
(4) |
Oct
(37) |
Nov
(43) |
Dec
(64) |
2015 |
Jan
(16) |
Feb
(14) |
Mar
(12) |
Apr
(12) |
May
(4) |
Jun
(4) |
Jul
(16) |
Aug
(12) |
Sep
(2) |
Oct
(3) |
Nov
(7) |
Dec
(16) |
2016 |
Jan
(41) |
Feb
(17) |
Mar
(8) |
Apr
(16) |
May
(86) |
Jun
(16) |
Jul
(62) |
Aug
(70) |
Sep
(40) |
Oct
(16) |
Nov
(21) |
Dec
(42) |
2017 |
Jan
(19) |
Feb
(6) |
Mar
(29) |
Apr
(29) |
May
(16) |
Jun
(11) |
Jul
(18) |
Aug
|
Sep
(88) |
Oct
(39) |
Nov
(18) |
Dec
(36) |
2018 |
Jan
(82) |
Feb
(79) |
Mar
(26) |
Apr
(54) |
May
(31) |
Jun
(23) |
Jul
(16) |
Aug
(15) |
Sep
(11) |
Oct
(23) |
Nov
(13) |
Dec
(6) |
2019 |
Jan
(12) |
Feb
(40) |
Mar
(20) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Warzone 2. T. <in...@de...> - 2018-10-20 12:57:16
|
#4836: No weapon when destroy a factory -------------------------------------+------------------------- Reporter: corvax | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: other | Version: 3.2.3 Operating System: Windows 10 64bit | -------------------------------------+------------------------- Hi During a session game "No place to hide" in Challenged mode when a factory is destroy there are no weapons to collect. In previous versions there were so I hope is a bug. Congratulation for the game that change a lot since the PSX1 version. Have a nice day -- Ticket URL: <http://developer.wz2100.net/ticket/4836> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-10-10 16:44:21
|
#4835: Mods not getting loaded -------------------------------------+------------------------- Reporter: OpenSourceGames | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: other | Version: unspecified Resolution: | Keywords: Operating System: All/Non-Specific | -------------------------------------+------------------------- Changes (by OpenSourceGames): Attachment "err.png" added http://developer.wz2100.net/raw-attachment/ticket/4835/err.png error message -- Ticket URL: <http://developer.wz2100.net/ticket/4835> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-10-10 16:16:10
|
#4835: Mods not getting loaded -------------------------------------+------------------------- Reporter: OpenSourceGames | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: other | Version: unspecified Operating System: All/Non-Specific | -------------------------------------+------------------------- warzone2100-3.2.3_portable win64 To reproduce: 1. make mods/autoload contain: ARmod_beta3.wz sequences.wz 2. Start new campaign game and save the game 3. Restart WZ and load that game Error message: Warzone has detected a problem A non fatal error has occured. [rebuildSearchPath:446] The required mod could not be loaded: ARmod_beta3.wzsequences.wz, Warzone will try to load the game without it. Seems to be a delimiter error or something like that. -- Ticket URL: <http://developer.wz2100.net/ticket/4835> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-10-04 21:13:21
|
#4834: Nullbot ignores starting units that cannot build -------------------------------------+------------------------- Reporter: Forgon | Owner: NoQ Type: bug | Status: new Priority: normal | Milestone: unspecified Component: NullBot (AI) | Version: git/master Resolution: | Keywords: Blocked By: | Blocking: Operating System: All/Non-Specific | -------------------------------------+------------------------- Changes (by Forgon): Attachment "nullbot_starting_tanks_active.png" added http://developer.wz2100.net/raw-attachment/ticket/4834/nullbot_starting_tanks_active.png starting tanks are active on DA-europe after applying this patch -- Ticket URL: <http://developer.wz2100.net/ticket/4834> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-10-04 21:13:03
|
#4834: Nullbot ignores starting units that cannot build -------------------------------------+------------------------- Reporter: Forgon | Owner: NoQ Type: bug | Status: new Priority: normal | Milestone: unspecified Component: NullBot (AI) | Version: git/master Resolution: | Keywords: Blocked By: | Blocking: Operating System: All/Non-Specific | -------------------------------------+------------------------- Changes (by Forgon): Attachment "nullbot_starting_tanks_idle.png" added http://developer.wz2100.net/raw-attachment/ticket/4834/nullbot_starting_tanks_idle.png starting tanks are idle on DA-europe before applying this patch -- Ticket URL: <http://developer.wz2100.net/ticket/4834> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-10-04 21:12:39
|
#4834: Nullbot ignores starting units that cannot build -------------------------------------+------------------------- Reporter: Forgon | Owner: NoQ Type: bug | Status: new Priority: normal | Milestone: unspecified Component: NullBot (AI) | Version: git/master Resolution: | Keywords: Blocked By: | Blocking: Operating System: All/Non-Specific | -------------------------------------+------------------------- Changes (by Forgon): Attachment "nullbot_starting_units.patch" added http://developer.wz2100.net/raw-attachment/ticket/4834/nullbot_starting_units.patch patch file created with `git format-patch` -- Ticket URL: <http://developer.wz2100.net/ticket/4834> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-10-04 21:12:20
|
#4834: Nullbot ignores starting units that cannot build --------------------------+------------------------------------- Reporter: Forgon | Owner: NoQ Type: bug | Status: new Priority: normal | Milestone: unspecified Component: NullBot (AI) | Version: git/master Keywords: | Blocked By: Blocking: | Operating System: All/Non-Specific --------------------------+------------------------------------- Nullbot ignored starting units that cannot build. The attached patch fixes the problem. -- Ticket URL: <http://developer.wz2100.net/ticket/4834> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-10-04 21:10:52
|
#4833: when starting new Gamma campaign, in Gamma 1 transporter drops 7/10 units are selected randomly -------------------------------------+------------------------- Reporter: Forgon | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: other | Version: unspecified Resolution: | Keywords: Blocked By: | Blocking: Operating System: All/Non-Specific | -------------------------------------+------------------------- Changes (by Forgon): Attachment "gamma1_transporter_drop.png" added http://developer.wz2100.net/raw-attachment/ticket/4833/gamma1_transporter_drop.png first drop of units by transporter in Gamma 1 after applying this patch -- Ticket URL: <http://developer.wz2100.net/ticket/4833> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-10-04 21:10:35
|
#4833: when starting new Gamma campaign, in Gamma 1 transporter drops 7/10 units are selected randomly -------------------------------------+------------------------- Reporter: Forgon | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: other | Version: unspecified Resolution: | Keywords: Blocked By: | Blocking: Operating System: All/Non-Specific | -------------------------------------+------------------------- Changes (by Forgon): Attachment "gamma_1.zip" added http://developer.wz2100.net/raw-attachment/ticket/4833/gamma_1.zip savegame for Gamma 1 which starts immediately after the first transporter drop -- Ticket URL: <http://developer.wz2100.net/ticket/4833> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-10-04 21:10:14
|
#4833: when starting new Gamma campaign, in Gamma 1 transporter drops 7/10 units are selected randomly -------------------------------------+------------------------- Reporter: Forgon | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: other | Version: unspecified Resolution: | Keywords: Blocked By: | Blocking: Operating System: All/Non-Specific | -------------------------------------+------------------------- Changes (by Forgon): Attachment "gamma_1_transporter_drops.patch" added http://developer.wz2100.net/raw-attachment/ticket/4833/gamma_1_transporter_drops.patch patch file created with `git format-patch` -- Ticket URL: <http://developer.wz2100.net/ticket/4833> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-10-04 21:09:58
|
#4833: when starting new Gamma campaign, in Gamma 1 transporter drops 7/10 units are selected randomly --------------------+------------------------------------- Reporter: Forgon | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: other | Version: unspecified Keywords: | Blocked By: Blocking: | Operating System: All/Non-Specific --------------------+------------------------------------- Campaign mission Gamma 1 can be launched as part of a new Gamma campaign (either via 'Single Player->New Campaign->Gamma Campaign' in the main menu or with the commandline option '--game=CAM_3A') rather than by continuing the Beta campaign. In the former case, players will receive specific reinforcements, dropped by the transporter in batches of 10. These units are described in the function 'sendPlayerTransporter()' at [https://github.com/Warzone2100/warzone2100/blob/master/data/base/script/campaign/cam3-a.js#L99 './data/base/script/campaign/cam3-a.js:99']. They differ only in their turrets, which must be one of the following types: * Assault Gun * Hyper Velocity Cannon * Cyclone AA Turret * Truck How many units of each type are to be produced for each transporter drop has varied since ` commit 08248b814dfcb40033e890d0250b4815b4d10bfd Author: KJeff01 <kje...@gm...> Date: Wed May 31 00:24:41 2017 -0500 Convert cam3-a{.vlo,.slo} to cam3-a.js Updates to campaign library and templates included. Update POTFILES.in ' The only requirement was that at least one truck had to be present. This however changed, so that at least one unit of each type is required since ` commit cb19c7672fe915b95795e3af33c63c9d567faccc Author: KJeff01 <kje...@gm...> Date: Thu Jun 1 20:58:40 2017 -0500 Finish cam3-A and add dynamic difficulty Finishes campaign 3-A script. Updates research to get everything correctly in Gamma. Fix enemy VTOL units being stuck in campaign. The enemy players actually are given research benefits instead of nothing. Add insane difficulty option for campaign. Make campaign more dynamic with difficulty. Certain values such as timers, power, and transport times now change with campaign difficulty. Fix enemy base elimination sounds Apply the changes made to the old campaign research files in b1cb129247bca05fb35e50b15e8bedee2d6f4a8a to the new file. Fix enemy research in campaign. The same research item could be continuously researched over and over again and could possibly be used for unfair advantages. ' That means that for each of the 4 turret types, between 1 and 7 units can be dropped. Since Gamma 1 is a challenging mission, the composition of the initial drop can be decisive for its success or failure, especially when most of its units are trucks. I therefore propose to instead always drop the following units: * 4 Assault Guns * 2 Hyper Velocity Cannons * 2 Cyclone AA Turrets * 2 Trucks Thus, every drop will look as in the attached picture [raw- attachment:gamma_1_transporter_drop.png]. -- Ticket URL: <http://developer.wz2100.net/ticket/4833> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-10-04 20:51:17
|
#4832: allow flamers and AA units to fire while moving in campaign games -------------------------------------------------+------------------------- Reporter: Forgon | Owner: Type: patch (an actual patch, not | Status: new a request for one) | Milestone: unspecified Priority: normal | Version: git/master Component: Campaign | Keywords: Resolution: | Blocking: Blocked By: | Operating System: All/Non-Specific | -------------------------------------------------+------------------------- Changes (by Forgon): Attachment "fire_on_move_campaign.patch" added http://developer.wz2100.net/raw-attachment/ticket/4832/fire_on_move_campaign.patch patch file created with `git format-patch` -- Ticket URL: <http://developer.wz2100.net/ticket/4832> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-10-04 20:50:33
|
#4832: allow flamers and AA units to fire while moving in campaign games -------------------------------------------------+------------------------- Reporter: Forgon | Owner: Type: patch (an actual patch, not | Status: new a request for one) | Milestone: unspecified Priority: normal | Version: git/master Component: Campaign | Keywords: Resolution: | Blocking: Blocked By: | Operating System: All/Non-Specific | -------------------------------------------------+------------------------- Changes (by Forgon): Attachment "fire_on_move_campaign.patch" added http://developer.wz2100.net/raw-attachment/ticket/4832/fire_on_move_campaign.patch patch file created with `git format-patch` -- Ticket URL: <http://developer.wz2100.net/ticket/4832> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-10-04 20:49:39
|
#4832: allow flamers and AA units to fire while moving in campaign games -------------------------------------------------+------------------------- Reporter: Forgon | Owner: Type: patch (an actual patch, not a | Status: new request for one) | Milestone: Priority: normal | unspecified Component: Campaign | Version: Keywords: | git/master Blocking: | Blocked By: | Operating System: All | /Non-Specific -------------------------------------------------+------------------------- When this game was released in 1999, flamers and some AA units could not fire on the move. This behaviour changed from 2008 onward, but only for multiplayer games. Campaign games have been unaffected. First the Flamer turret was allowed to fire on the move, then, in addition, Inferno and Plasmite Flamer: ` commit cc6e90ce0d9d5af3be4b0faca6fa29d4a118f844 Author: Roman C <tr...@gn...> Date: Thu Feb 14 21:40:44 2008 +0000 Weapon balance: -light flamers are now allowed to shoot while moving git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@3780 !4a71c877 -e1ca-e34f-864e-!861f7616d084 ' ` commit 5ec11ada0791b82f7e628a1415c4dd07a644cd2d Author: Roman C <tr...@gn...> Date: Sun Apr 13 14:02:33 2008 +0000 Flamer Balance: -all flamers can fire while moving git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@4579 !4a71c877 -e1ca-e34f-864e-!861f7616d084 ' The Cyclone AA Turret was replaced with the AA Flak Cannon in multiplayer: ` commit abc4db390b2500b56d975dbf33b2927de28727f6 Author: Guangcong Luo <za...@wz...> Date: Thu Sep 2 04:33:19 2010 +0000 Rebalance 0.8.1: - Removed Cyclone turret - Added: AA Flak Cannon (and Emplacement and Hardpoint) - Flak Cannon is a medium-reload splash weapon - Prerequisites: HPV - Added: Sunburst AA Rocket Array (and Site) - Sunburst is a slow-reload salvo weapon - Prerequisites: Lancer - Lancer damage toned down a bit - Heavy Laser damage increased a bit git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@11569 !4a71c877-e1ca-e34f-864e-!861f7616d084 ' Finally, in multiplayer all AA units were allowed to fire on the move, in a commit which, oddly, exists twice: ` commit 1c090d7bff3823a66dd96739a730e99aafb9076c Author: Guangcong Luo <za...@wz...> Date: Thu May 7 10:25:19 2009 +0000 Rebalance 0.5.0: * Heavy VTOL bombs made lighter, light VTOL bombs made heavier. * VTOL bomb accuracy upgrades changed to damage upgrades. * Angel Missile stronger, Archangel Missile weaker, both fewer prereqs. * Damage upgrades now also upgrade splash and burn damage. * Needle Gun slightly stronger. Still not actually better than HPV. * Rails now penetrating weapons. In practice, this shouldn't make much difference. * Factory, Cyborg factory, and VTOL factory upgrades combined; now only 4 upgrades instead of 6-9 each. * Repair facility upgrades condensed, now only 3 upgrades instead of 6. * Artillery weapons do less damage to tanks, but more to walls. * MG damage back down to original levels. The extra APDSB MG Bullets in the early game does plenty to compensate. * VTOL HP actually makes sense now. * Cannon HP increased a bit more. * Stormy nerfed. * All AA weapons have full fire-on-move. For exact numbers, refer to http://guide.wz2100.net/new/ or wait for the detailed changelog after all rebalancing is done. git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@7353 !4a71c877-e1ca-e34f-864e-!861f7616d084 ` ` commit 49fc746bf351c066d96a81ead4d7633ff1602224 Author: Guangcong Luo <za...@wz...> Date: Thu May 7 10:25:19 2009 +0000 Rebalance 0.5.0: * Heavy VTOL bombs made lighter, light VTOL bombs made heavier. * VTOL bomb accuracy upgrades changed to damage upgrades. * Angel Missile stronger, Archangel Missile weaker, both fewer prereqs. * Damage upgrades now also upgrade splash and burn damage. * Needle Gun slightly stronger. Still not actually better than HPV. * Rails now penetrating weapons. In practice, this shouldn't make much difference. * Factory, Cyborg factory, and VTOL factory upgrades combined; now only 4 upgrades instead of 6-9 each. * Repair facility upgrades condensed, now only 3 upgrades instead of 6. * Artillery weapons do less damage to tanks, but more to walls. * MG damage back down to original levels. The extra APDSB MG Bullets in the early game does plenty to compensate. * VTOL HP actually makes sense now. * Cannon HP increased a bit more. * Stormy nerfed. * All AA weapons have full fire-on-move. For exact numbers, refer to http://guide.wz2100.net/new/ or wait for the detailed changelog after all rebalancing is done. git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@7353 !4a71c877-e1ca-e34f-864e-!861f7616d084 ' Eugen, now mentioned as campaign tester in the file './AUTHORS', suggested that flamers should be allowed to fire on the move in campaign games (read [http://forums.wz2100.net/viewtopic.php?f=1&t=12714&p=142828#p142828 this forum post]). This will surely spare players some frustration when their units get clogged up or begin to dance due to the horrible pathfinding. The attached patch allows flamers and all AA units to fire on the move in the campaign. This affects the following turrets: * Flamer * Inferno * Cyclone Flak Turret (exists only in the campaign) * Vindicator SAM Note that the scavengers' flamer used by their Firebus must still stop to fire, just like in multiplayer. -- Ticket URL: <http://developer.wz2100.net/ticket/4832> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-09-28 17:19:26
|
#4831: Map select GUI overlap ----------------------------+------------------------------------- Reporter: Berserk Cyborg | Owner: Type: bug | Status: new Priority: trivial | Milestone: unspecified Component: other | Version: 3.2 and master Keywords: | Blocked By: Blocking: | Operating System: All/Non-Specific ----------------------------+------------------------------------- When one presses on the globe icon to choose a skirmish map, the blue box that holds all the maps to select from is shifted down a few pixels which overlaps onto the top portion of the chat box area. -- Ticket URL: <http://developer.wz2100.net/ticket/4831> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-09-24 11:27:44
|
#4830: warcam started at distance < 0 breaks zoom when stopped -------------------------------------+------------------------- Reporter: Forgon | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: other | Version: unspecified Resolution: | Keywords: Blocked By: | Blocking: Operating System: All/Non-Specific | -------------------------------------+------------------------- Changes (by Forgon): Attachment "warcam_zoom.patch" added http://developer.wz2100.net/raw-attachment/ticket/4830/warcam_zoom.patch patch file created with `git format-patch` -- Ticket URL: <http://developer.wz2100.net/ticket/4830> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-09-24 11:27:33
|
#4830: warcam started at distance < 0 breaks zoom when stopped -------------------------------------+------------------------- Reporter: Forgon | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: other | Version: unspecified Resolution: | Keywords: Blocked By: | Blocking: Operating System: All/Non-Specific | -------------------------------------+------------------------- Changes (by Forgon): Attachment "warcam_zoom_bug.png" added http://developer.wz2100.net/raw-attachment/ticket/4830/warcam_zoom_bug.png warcam stopped after start at distance -250, leading to a zoom value of 2^32^-256 -- Ticket URL: <http://developer.wz2100.net/ticket/4830> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-09-24 11:26:48
|
#4830: warcam started at distance < 0 breaks zoom when stopped --------------------+------------------------------------- Reporter: Forgon | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: other | Version: unspecified Keywords: | Blocked By: Blocking: | Operating System: All/Non-Specific --------------------+------------------------------------- Starting the warcam in debug mode at a distance < 0 and stopping it afterwards set the zoom to a value of approximately 2^32^ minus the negative distance (see attached image [raw-attachment:warcam_zoom_bug.png]). This was a type error: The distance, a float, was stored in an uint32_t (or UDWORD, as defined in [https://github.com/Warzone2100/warzone2100/blob/master/lib/framework/types.h#L103 './lib/framework/types.h:103]'). The problem had been introduced in ` commit 1c580714051c3baeadea53e4c3dd494a8c10e443 Author: per <pe...@wz...> Date: Tue Jan 15 22:36:51 2013 +0100 Remove zoom limits in debug mode. ' The attached patch fixes the problem. -- Ticket URL: <http://developer.wz2100.net/ticket/4830> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-09-17 16:35:46
|
#4829: Loading save on limbo mission assert -------------------------------------+---------------------------- Reporter: Berserk Cyborg | Owner: Type: bug | Status: new Priority: trivial | Milestone: unspecified Component: other | Version: 3.2 and master Resolution: | Keywords: Blocked By: | Blocking: Operating System: All/Non-Specific | -------------------------------------+---------------------------- Changes (by Berserk Cyborg): Attachment "assertSave.zip" added http://developer.wz2100.net/raw-attachment/ticket/4829/assertSave.zip -- Ticket URL: <http://developer.wz2100.net/ticket/4829> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-09-17 16:35:37
|
#4829: Loading save on limbo mission assert ----------------------------+------------------------------------- Reporter: Berserk Cyborg | Owner: Type: bug | Status: new Priority: trivial | Milestone: unspecified Component: other | Version: 3.2 and master Keywords: | Blocked By: Blocking: | Operating System: All/Non-Specific ----------------------------+------------------------------------- The one "limbo" mission (cam3-c) can spam an assert if loading a save before reaching the Gamma base trigger that calls restoreLimboMissionData(). {{{ info |11:07:52: [findAssemblyPointPosition:4815] unable to find a valid location! info |11:07:52: [findAssemblyPointPosition:4815] Assert in Warzone: structure.cpp:4815 (!"unable to find a valid location"), last script event: '<none>' }}} Did not seem to affect anything so it appears harmless for now (has the visibility issue shown in #4828 too). -- Ticket URL: <http://developer.wz2100.net/ticket/4829> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-09-17 16:24:58
|
#4828: Visible tiles on campaign saves with allies -------------------------------------+---------------------------- Reporter: Berserk Cyborg | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: Engine: other | Version: 3.2 and master Resolution: | Keywords: Blocked By: | Blocking: Operating System: All/Non-Specific | -------------------------------------+---------------------------- Changes (by Berserk Cyborg): Attachment "visBug.zip" added http://developer.wz2100.net/raw-attachment/ticket/4828/visBug.zip -- Ticket URL: <http://developer.wz2100.net/ticket/4828> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-09-17 16:24:41
|
#4828: Visible tiles on campaign saves with allies ----------------------------+------------------------------------- Reporter: Berserk Cyborg | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: Engine: other | Version: 3.2 and master Keywords: | Blocked By: Blocking: | Operating System: All/Non-Specific ----------------------------+------------------------------------- Another visibility bug. This time loading a save game on a campaign mission with an ally on it shares the ally tile visibility with the player (but not the objects themselves). I encountered something similar months ago and now I know that was due to alliances persisting across missions. At the moment all alliances are unset before loading the next mission in libcampaign. -- Ticket URL: <http://developer.wz2100.net/ticket/4828> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-09-17 04:19:40
|
#4827: search issues... -------------------------------------+------------------------- Reporter: zutai | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: Website | Version: unspecified Operating System: Windows 10 64bit | -------------------------------------+------------------------- dont know if it is related to the forum update, but the search system for the mods/maps is broken. doesnt keep it's perimeters when you change pages from 8 player maps -- Ticket URL: <http://developer.wz2100.net/ticket/4827> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-09-09 12:30:06
|
#4826: moving around the map -------------------------------------------------+------------------------- Reporter: Nod0n_ | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: Input system (mouse / | Version: git/master keyboard) QT backend | Operating System: All/Non-Specific | -------------------------------------------------+------------------------- Hi, This is my first Ticket and I hope I do it all right. Just tell me if I miss something. Forgon in the IRC told me to write a Ticket about it. What I think could be done better: Moving around with the arrow keys is not very good when you use other keys (for example f1-f6) in the same time. Moving with the mose to the edge of the screen is not very fast because you will have to move your mouse back to the center after moving the map. How would it be better?: Use the mouse to move the map but: you click your right mouse button and hold it down, while holding the right mouse button, you move your mouse in a direction. this will make the map move in this direction. This is not easy to use if you never did, but after 30 min of using this you will be a lot faster. When you have radar, the radar will still be faster for long distances, but only on big maps. I know this from an other RTS called CnC Generals (from EA). The steps: 1) click the right mouse button (and hold, don't release it) 2) move the mouse slightly in one direction 3) release the right mouse button A video where you can see the usage of both, clicking on the minimap and moving this the mouse together. You can only watch the first 30 sec, no need to watch more ;) youtube: [https://www.youtube.com/watch?v=4CutLTu5gf0&list =PLtGvoQJjZNvuCi9PswKPB-g5PqMYJOxE_&index=12] While making this map movement your selected unit / building should stay selected, your mouse should not move on your screen, only the map. (like in CnC Generals) If you have any question or need more information let me know. Salutations Nod0n -- Ticket URL: <http://developer.wz2100.net/ticket/4826> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |
From: Warzone 2. T. <in...@de...> - 2018-09-09 02:17:29
|
#4825: can't download game -------------------------------------+------------------------- Reporter: Malikia Garandar | Owner: Type: bug | Status: new Priority: normal | Milestone: unspecified Component: other | Version: unspecified Operating System: All/Non-Specific | -------------------------------------+------------------------- I recently got this Chromebook and the first thing I did was try to download this game because I've played it and I LOVE it. But when I download it, the file doesn't contain the launcher, just the games info and programming. Help! -- Ticket URL: <http://developer.wz2100.net/ticket/4825> Warzone 2100 Trac <http://developer.wz2100.net/> The Warzone 2100 Project |