PunchFox

Nice one. You have no valid explanation to give in regards to my clear and legitimate questions/suggestions, and when I call you on it, I must be "trolling". You may as well just admit that you have nothing valid or sensible to say, it's already clear as day. Truly hilarious. Keep up the work on your admittedly thorough, but nonsensically designed installer.

So it's built like that intentionally, though you won't explain why, and I can easily give a few reasons why it's a bad idea.... Not to mention, while I admittedly don't know much about your particular program, I do know quite a bit about programming its self, and I can't for the life of me, imagine why it would be so difficult to simply NOT copy in XVM, just the other mods... Furthermore, I took a few minutes to decompile your installer and check the insides. It's just an Innosetup installer, with all of the scripting handled by their 3rd party library, am I right? Changing some flags and script lines around -should- be very simple. At this point though, I am getting the idea that you are rather stubborn about the way you program functions, even if it makes no sense at all, and I also gather you may not 100% know exactly what you are doing (insisting on using nightly builds). I suppose I can just start using the direct link, or possibly start compiling my own mod pack and forego your installer, because I think it's rather silly to continue providing support via those obnoxious ad.fly links for such an odd and poorly designed mod installer, as "convenient" as it may be.

Yes... I noticed... and hence the issue. All the mods outside of the XVM section do NOT need XVM to function. So why does your mod installer insist on slipping it in regardless? Especially since it doesn't even do anything at that point, it just loads in and causes issues., without physically modifying the game. Shouldn't it be easy to leave out the XVM files if none of the XVM stuff is selected? What reason do you have to put it in anyways? XVM has many bugs and issues aside from the Vanilla game. Even if it doesn't cause issues for a particular client, it drastically increases load times and memory consumption. Therefore, if one doesn't want to use it, it's rather silly to slip it in anyways, "invisible". Even when invisible, it still causes said issues. Now you know the problem. :)

As the title states: You can completely deselect XVM, and only select mods which can run without XVM. Aslain's still copies in XVM files nonetheless. This is entirely unnecessary.

Bump?

I made one suggestion that still allows you to include the nightly build, and I also mentioned a separate, but related, issue. Will you please comment on them?

Um, bump? Did Aslain really move my topic out of the Issues section, just so he could ignore it? This is still an issue...

That's great to know, and I'll keep it in mind. Definitely solves the problem of wanting to stick to a stable version, and I will do this immediately. However, I still think that implementing a simplistic, no-muss option which doesn't require me to run around downloading individual packs (the main reason I like Aslain's) and lets me choose between the latest stable version, and Aslain's choice of nightly, would round out his mod pack installer very nicely. It also doesn't solve the issue of wanting to forego XVM entirely - To see what I mean, try deselecting XVM entirely, and then install Aslain's pack. Then check your res_mods folder. XVM will still be there, and World of Tanks will still load it. This should be changed. EDIT: But now that I think about it, one of the other reasons I like Aslain's is because it lets me easily configure XVM its self... for example, I hate the modified damage display, as well as the modifications it makes to the little displays above each tank in battle. I usually disable these options in Aslain's, and just use the rating feature. Ever since the official online XVM editor became obsolete, it's a real pain to modify the XVM config, so I still think it would far more preferable to include the two builds officially through the installer, so that you can use his configuration tool on them. Having said that, can someone please direct me to a tutorial or give me a brief explanation on how to disable all the fancy shmancy UI modifications which XVM makes? :) All I really want is to see the WN8 numbers next to player's names on the info panel, and have them colored appropriately.

I don't know anything about the XVM-specific development process, so please let me know if you're more familiar with it, but on a general basis, no, stable commits are NOT randomly decided. They are labeled as stable because the dev team feels that they are feature-complete, and that there are not any known major bugs. Of course, mistakes will always happen, but with nightly builds, they are not even trying to create a bug-free build. It's simply a mid-way point between stable releases for the dev team and other contributors to keep track of progress, whatever state that progress may be in. Again, if you happen to be a contributor to the XVM project and know something more then I do, please let me know. :) The problem is that it is never "safe" to use a nightly build. The description of their nightly build which I quoted in my initial post explains why this is the case, as well as my explanation of the build process, and stable vs nightly labels. You do bring up a valid point in the case of quick-releases after recent WG updates, or previously unknown bugs in the stable version. However, as I also said in my initial post, these nightly versions, even if they inlude one or two fixes for something which may be causing issues in a "stable" build, are VERY likely to have tons of bugs for other things, so you are really just trading one issue for a dozen others. As I stated before, for a long time, I couldn't even run your mod installer, because the nightly version was causing consistent crashes since 9.5. This issue only disappeared when you switched back to the stable. I have a solution though: How about include an option where users can select which build they want to use? You can include both a stable build, and the latest nightly build you deem "necessary". On a similar note, I noticed that even when you entirely de-select XVM from your mod installer, it still slips an XVM build into my mods folder. This is entirely unnecessary, and exacerbates the issue. I originally tried using your mod installer while deselecting XVM, hoping I could use the mods that don't require it without issue, but this proved fruitless, since your installer gave me XVM anyways, and the crashes continues, even though I wasn't actually using it at all. In the end, I needed to gather up my individual mods and package them together, which is really a big painful hassle compared to the ease of use your installer gives me. :) So, in summary: If you must continue supplying nightly builds, please include a secondary stable build which I have the option to use, and as well, please make it possible to deselect XVM such that your mod installer will NOT install it at all. If you made these two changes, your already great installer would be even better. Thank you for taking the time to read my post and respond, I really do appreciate it, and I look forward to seeing what you think of my own responses and suggested solutions!

Hello, I noticed that you recently switched to stable builds, specifically, after having to revert back to a previous build because of bugs/user issues. I thought you would stick to using the stable version for good, but in the latest update, you went back to using the nightly build.... Why are you doing this? To quote from the official XVM website at http://www.modxvm.com/en/download-xvm/ In other words, the nightly version is NOT stable (unlike the aptly named "stable version") and is prone to bugs, issues, etc, as you should have already noticed in v4.2.18 of your mod installer. Furthermore, for a long time (since 9.5, to be specific) I couldn't even use Aslain's at all, because it was using the nightly version, which had an error that was causing me to constantly crash on match load. Only when Aslain's finally switched over to the stable version after the 9.6 update, did this issue disappear. Now you are switching back to the nightly. I really do appreciate the Aslain's mod pack. It is the most thorough and customizable mod installer I have yet to find, but the fact that it relies on an UNSTABLE nightly version is really a glaring flaw. What reasoning is behind this choice? Why is sticking to the stable version not an option? Please, stop using the nightly version, because as it is, I refuse to download recent Aslain updates, since I would rather keep the version that uses a stable build of XVM (I'm on v4.2.20 atm). I know I'm repeating myself at this point, but I feel like I can't stress myself enough: The nightly build is NOT for regular use. Please don't use it. Use the stable version. Because it's stable. Thank you for reading, and I hope you take this into consideration.