25 || Preconditions || The Rubberband is placed/selected in strictly vertical or in rising diagonal (low left end, high right end) orientation. || |
26 || Preconditions || The Rubberband is placed/selected in strictly vertical or in rising diagonal (low left end, high right end) orientation. || |
26 || Details || In Rubberband's above mentioned orientations (= sprite frames) edge pixels of other orientations are visible/placed. || |
27 || Details || In Rubberband's above mentioned orientations (= sprite frames) edge pixels of other orientations are visible/placed. || |
27 || Workaround || If you do *NOT* play on official server you could replace your Rubberband's spritesheet (Data/Graphics/amRubber.png) with the [https://hg.hedgewars.org/hedgewars/raw-file/076aa3b2587dc539033a3eb60305e01e763e1bef/share/hedgewars/Data/Graphics/amRubber.png fixed version]. If you intend to play over a private server or over local network make sure you only play together with people having the exact same fix or else the game might desync and aborts due to different game/map state information || |
28 || Workaround || If you do *NOT* play on official server you could replace your Rubberband's spritesheet (Data/Graphics/amRubber.png) with the [https://hg.hedgewars.org/hedgewars/raw-file/076aa3b2587dc539033a3eb60305e01e763e1bef/share/hedgewars/Data/Graphics/amRubber.png fixed version]. If you intend to play over a private server or over local network make sure you only play together with people having the exact same fix or else the game might desync and aborts due to different game/map state information || |
28 || See also || [https://hedgewars.org/files/rubberpixglitch.png screenshot (by Wuzzy)] issue 903 [https://hg.hedgewars.org/hedgewars/rev/076aa3b2587dc539033a3eb60305e01e763e1bef fix 076aa3b2587dc539033a3eb60305e01e763e1bef] || |
29 || See also || [https://hedgewars.org/files/rubberpixglitch.png screenshot (by Wuzzy)] issue 903 [https://hg.hedgewars.org/hedgewars/rev/076aa3b2587dc539033a3eb60305e01e763e1bef fix 076aa3b2587dc539033a3eb60305e01e763e1bef] || |
29 || Status || FIXED || |
30 || Status || FIXED || |
30 |
|
31 = Release 0.9.20 = |
|
32 |
|
33 == Game crash when roping into "Sea" world edges == |
|
34 || Preconditions || "World Edge" in active game scheme are set to "Sea" || |
|
35 || Details || When a hedgehog, using rope, leaps or swings into the World Edge, it will get teleported to under the water surface. If it then falls into death without using the rope again, the game crashes. || |
|
36 || Workaround || Try to avoid getting into the World Edge while using rope. If it happens anyway, just press the fire key immediately to reuse the rope before the hogs falls into death. This should put the game back into a state that will not crash. || |
|
37 || See also || issue 764 || |
|
38 || Status || FIXED || |
|
39 |
|
40 == Some trainings are broken - impossible to destroy targets == |
|
41 || Preconditions || Player hedgehog in training is set to invulnerable (it's in a protective bubble) || |
|
42 || Details || Due to a bug the invulnerably of a hedgehog is temporarily applied to the target/crate/barrel during attack || |
|
43 || Workaround || None known || |
|
44 || See also || issue 766 [https://hg.hedgewars.org/hedgewars/rev/ead5e4b21671f3b7fb1a59b922ce21c51eb80b28 fix 955a90b8886577fcc8f20b7c6e3a64d6518a8c5f] || |
|
45 || Status || FIXED || |
|
46 |
|
47 == Drill Rockets will sometimes explode on land impact (like a bazooka shell) instead of drilling == |
|
48 || Workaround || None known || |
|
49 || See also || issue 766 [https://hedgewars.org/files/drilltest.png pic of failing drill rocket test] (compare to [https://hedgewars.org/files/drillnemo.png pic of successful drill rocket test]) || |
|
50 || Status || FIXED || |
|
51 |
|
52 == Ranking of teams in after-game statistics does not reflect the actual game result == |
|
53 || Workaround || None known || |
|
54 || Status || FIXED || |
|
55 |
|
56 == Game crashes when !IceGun is used to freeze water on low land graphics == |
|
57 || Workaround || None known || |
|
58 || See also || issue 777 [https://hg.hedgewars.org/hedgewars/rev/67b7bc53963963c56ca29425de85484247b72539 fix 67b7bc53963963c56ca29425de85484247b72539]) || |
|
59 || Status || FIXED || |
|
60 |
|
61 ---- |
|
62 = Release 0.9.19 = |
|
63 |
|
64 == !TrophyRace and other scripts/missions don't work properly == |
|
65 || Preconditions || Windows. Using Hedgewars installed from the download not long after release. || |
|
66 || Details || The race is not a race anymore, etc. The scripts seem to do nothing || |
|
67 || Workaround || Start Hedgewars and click the "Downloadable Content" button. After the page (hopefully loaded) download "Fix for Mission maps in original 0.9.19 release. Mission Maps Hotfix". Note: This fix will only affect the currently logged-in windows user. || |
|
68 || *Solution* || Re-download and reinstall Hedgewars 0.9.19 (the updated hedgewars installer for windows is fixed) || |
|
69 || Status || FIXED || |
|
70 |
|
71 == 'Quick game' will fail to start if the randomly chosen theme for the map is a DLC/manually-installed theme == |
|
72 || Workaround || None. Just restart quick game until a default theme is randomly chosen, then the game should load normally || |
|
73 || See also || issue 664 [https://hg.hedgewars.org/hedgewars/rev/955a90b8886577fcc8f20b7c6e3a64d6518a8c5f fix 955a90b8886577fcc8f20b7c6e3a64d6518a8c5f] || |
|
74 || Status || FIXED || |
|
75 |
|
76 = Release 0.9.18 = |
|
77 === Engine === |
|
78 |
|
79 == Fort Mode won't start == |
|
80 || Preconditions || Running Hedgewars engine from a binary/exe that was built before the fort mode fix/commit was applied to the 0.9.18 codebase || |
|
81 || Details || When trying to run a game in fort mode, the engine will only appear briefly as it fails to start properly || |
|
82 || Workaround || Finding or building a more up-to-date 0.9.18 hwengine binary || |
|
83 || See also || [https://hg.hedgewars.org/hedgewars/rev/2fc02902c7cbf3c29bfe08a50e5f37983582b251 fix 2fc02902c7cbf3c29bfe08a50e5f37983582b251] || |
|
84 || Status || FIXED || |
|
85 |
|
86 == Weapon menu misbehaves in certain situations == |
|
87 || Details || Weapon menu closes when it shouldn't, doesn't open on first try, etc... || |
|
88 || Workaround || None, you'll have to reopen the weapon menu again || |
|
89 || See also || issue 465 || |
|
90 || Status || FIXED || |
|
91 |
|
92 == Camera moving automatically even when Auto-Camera is disabled == |
|
93 || Preconditions || A non-local team selects a weapon/utility that requires point-and-click targeting (girder, airstrikes, homing weapons, teleport, etc) || |
|
94 || See also || [https://hg.hedgewars.org/hedgewars/rev/209c9ba77a0980a640151a185f119219b350c59e fix 209c9ba77a0980a640151a185f119219b350c59e] || |
|
95 || Status || FIXED || |
|
96 |
|
97 == No captions when muting audio == |
|
98 || Details || If you press 8 or set a volume of 0 a 'Audio Muted' message will stay on top, hiding any other caption. || |
|
99 || See also || [https://hg.hedgewars.org/hedgewars/rev/7681d14b9f0191eda821a9b744f0a093430321ee fix 7681d14b9f0191eda821a9b744f0a093430321ee] || |
|
100 || Status || FIXED || |
|
101 |
|
102 === Frontend === |
|
103 == Returning from netgame room leads to "In game..." screen (instead of lobby) == |
|
104 || Preconditions || Happens after failed game start (because of desync or similar) || |
|
105 || Workaround || None. Since the user can't leave that screen, a restart of Hedgewars is necessary || |
|
106 || Status || FIXED || |
|
107 |
|
108 == Frontend Crash when somebody joins your room == |
|
109 || Preconditions || Hedgewars was started with Frontend-Sounds turned off, then they were turned on || |
|
110 || Workaround || Restart Hedgewars after turning Frontend-Sounds on || |
|
111 || See also || issue 506 || |
|
112 || Status || FIXED || |
|
113 |
|
114 == Frontend Crash when canceling a !YouTube video upload == |
|
115 || See also || issue 471 || |
|
116 || Status || FIXED || |
|
117 |
|
118 == Wrong theme selected for static/preset map in online game (desync on join) == |
|
119 || Workaround || None known yet (try rejoining?), a server-side workaround is under consideration though. || |
|
120 || See also || issue 481 || |
|
121 || Status || FIXED || |
|