Quote from: DarkOne on June 18, 2013, 09:28 PMfoes

which foes? 

Quote from: barman on June 18, 2013, 09:15 PM
/ts enables fall damage after every shot

?
(Nope.)

A wild update appears. 0.5.2.5

• Finalized the FullscreenFrontend option which now behaves like it would normally (with resolution restoration).
  
• Settings file has fully been reorganized; you must fill your settings again into the new settings file.
  
• Added the Multi-Monitor feature: enable W:A to display the game spanned across several monitors, placed either vertically or horizontally, in either frontend and/or in-game. With AutoSetResolution enabled, the resulting summed up in-game resolution will automatically be set in WA settings on every launch. When using stretched or fullscreen frontend mode, enabling the Multi-Mon in either in-game or frontend will not clip your cursor in the frontend area. NOTE: performance has to be considered when enabling this option. Your hardware, mainly CPU and GPU, should be supporting it well not to allow any lags during the gameplay. Limitations: the display mode has to be "Extend" instead of "Double". The primary monitor has to be on the left for horizontal setups, or on top for vertical setups. For more than 2 monitors, they should go in numerical order (but maybe not, it's up to you to see it). Square setups (double on double) are currently partially supported, but can be looked into later if needed. Maximum texture size supported by your GPU is the limit for the total resolution from summing up all of the monitors' resolutions (if you exceeded the limit, WA will tell you and perform a workaround). Differently-sized monitors are supported but not recommended: it's up to you to decide whether to leave empty space by making the smaller monitor primary or, otherwise, cut a few lines by using the bigger one as primary. At least half of the height (or width in vertical setups) must collide with the monitor on the left; if it doesn't then you probably don't want multi-monitors.
  

ps3? so you cant wait 196 days for the PS4?
ok

People who have WormNAT2 issue (timeout during host creation) hosting from game on 3.7.2.1 please follow this guide and post the results:
http://worms2d.info/Recording_a_packet_log

NOTE: better disconnect the snooper while you are testing (this will give a clearer log)

Quote from: StepS on June 12, 2013, 12:20 AMDon't forget to remove all the other "color fixes" you installed before! They are not needed as the game is in 32-bit colour depth now.

Quote from: avirex on June 12, 2013, 01:51 AM
cool...

but had anyone requested for this? are people going to start paying wwp?

People commenting
http://puu.sh/3dVPu.png
Almost 700000 visitors in 4 years

And about 600 new different people visiting every day...
WWP definitely still got its reputation...

[ English | Русский ]

---

---

Tried different fixes, but WWP crashes on start? Or other problems? Your long internet searches are now over, and here's the solution.

Download:

• Only the fix | Mirror
  
• The fix + HD Resolution support | Mirror
  

How to install: Extract all the files from the archive to your WWP folder and launch WWP.

Last update: 4 October 2014

This will work on any version of WWP, but I personally recommend to patch it to the latest (1.01). The HD patch will only work on European versions of the game!

This will fix the crash problems in WWP for real on all Windows systems, including Windows 11, Windows 10, Windows 8.1, Windows 7, Vista and XP.

Don't forget to remove all the other fixes (such as "color fixes") if you installed them before! They are not needed as the game runs in 32-bit colour depth now, eliminating the color issue.
The same applies to WWP.exe "compatibility" options in the file properties. It's best to disable them all.

The windowed mode feature will also enable a cool windowed mode.



Features:

• Ability to enable windowed mode both during the match and in frontend menus. Open wndmode.ini and change "WindowedFrontend" and/or "WindowedInGame" from 0 to 1 to enable window. Frontend will be in the top left corner due to technical limitations; the in-game process will be in center of the screen.
  
• When in windowed mode during the match, unpin the cursor from the game window by alt-tabbing or pressing Ctrl+G. You can then move the window border (enabled through the "Border" setting in the ini file). Pin it back by clicking inside the window (or using Ctrl+G again).
  
• Minimize the game using Shift+Esc, Win+D, Win+M, or any other method you like. For fullscreen this only works when playing the match (to prevent crashes in frontend menus), in windowed mode the minimization always works perfectly.
  
• Press Alt+F4 when playing a match and you will immediately return to the frontend menu just like in WA. If you also press Alt+F4 in the frontend menu, WWP will shutdown.

Still having problems? Troubleshooting FAQ!

Spoiler! View

Q: When I start WWP, a black window appears, and then the game crashes with "WWP has stopped working" error.
A: Please ensure that:

• You have installed the fix correctly.
  
• All of the "Compatibility" options, like "Limited colour mode" are disabled. The game will not start if you force a 8-bit (256 color) or 16-bit color mode through the Compatibility options.
  
• No other fixes are interfering with the module.

Credits:

• menopem for his awesome d3dhook library from D3DWindower, otherwise this all wouldn't be possible!
  
• VEG for adapting d3dhook to make it independent with a settings file (wndmode).
  
• Kawoosh for the original white-fields-fix solution and the WormKitDS loader.
  
• StepS for further working and supporting the fix updates specifically for WWP/W2/WA after Kawoosh's solution, and making ReSolution.
  
• S*natch/des for their original Worms 2 HD patches. Thanks to that I was motivated to create ReSolution for Worms 2 and WWP!
  

oh yes
http://www.youtube.com/watch?v=kWSIFh8ICaA

you cant watch new replays on old update. there was once a converter but it doesn't work because the game logic is likely to change even a tiny bit with each new update. unless one of the players in the game used 3.6.31.0 and the author of the replay had 3.7.2.1, then it is possible.
as about lags - can you explain which lags? what is your cpu?

minigames need a good encryption when sending data, otherwise it's too easy to fake the results with a sniffer

noobot?

yes, don't thank me you lazy ass!

fixed

guys. ignore the warning. the module gets parameters and hosts fine, it's only WA which is arguing.
if i find time, i'll update wheat snooper...