The Battle for Wesnoth Forums

Ah, thanks dugi for creating the original no random mod that I based this on!
I was a lot easier to code when I had something similar to look at.

Well seems like I was wrong. It does clone the attacks correctly. I just removed the wrong items (attacks in this case) when cleaning up to restore the original attacks
Here is the fixed version. I think it should work correctly now. Let me know if it plays the same as the original mod.

Yeah, that's what I meant the the edit... It seems like I can't copy the original attacks and put them back... Lua doesn't seem to be able to create a perfect data copy just like that... ARGH BTW it fail because the data copy doesn't contain the traits/specials of the units. I don't remove them by h...

I looked that the mod DranKof linked (thanks!) and modified it to do this type of rng instead. The implementation is a a bit different than the c++. In the lua version it modifies the weapon values instead of the random number generator. This might cause problems if there is some crazy custom weapon...

I've ported the PRNG mod to lua. It's not as clean as the c++ code but not you don't have to use new binaries for it to work.

Edit: just noticed it breaks modifiers for weapons :/
Edit2: fixed it see below.

The harder campaign example is exactly why I don't like the current randomness in wesnoth. The pseudo randomness algorithm normalizes the probabilities so that if you ran a simulation of a battle between two units the most probable outcome would be what you'll get in just a few rounds/simulations wi...

Sure here it is with 1.10.6

Here is the 1.10.2 patched binary.

My friend that build the windows binaries is sick so it might take a few days before a new build is up.
Thanks for the feedback.

As I suspected there was a -march=native flag in the codeblocks project files.
Here you have a binary of wesnoth with the rnd patch. It should work on all CPUs that is equal or greater than a Pentium 3.

Edit: see next page for new binary.

This might be a problem with codeblock and it's optimization flags. It seems like it chooses the optimal instruction set from the host computer. In this case it was a sandy bridge CPU so every CPU that didn't have the same instruction set will not be able to run the .exe... We tried to make it compi...

Sorry for the delay. We switched from VS to codeblocks with gcc so there should not be any additional .dlls needed besides the ones already in the wesnoth folder. Report here if this is not the case or if there is any other problem. Here is the patched .exe of wesnoth 1.10.1 (Edit: removed old .exe ...

I managed to get your edited wesnoth binary running in 1.10 in Windows 7 64-bit Pro, however I had installed VS 2010 and its redistributables, and I still needed the first two library files indicated in my previous post above. Good to hear that you got it running. :) I take it that the increased ch...

Indeed, that is pretty cool. ZedDB - I found that using the same files in my 32-bit version of Windows 7 Pro gave an error which suggested that the particular dll file versions I downloaded would only work for the 64-bit version of Windows 7. Hmm perhaps you can try the .dll files that is in the co...

Note, this was with Windows 7 64-bit Pro, with the attachment you provided renamed to "wesnoth.exe" and the above dll files in the wesnoth directory, although named as wesnoth(32-bit).exe I got the same error. My friends computer is also running 64bit win 7. But visual studio compiled it ...