Jump to content
×
×
  • Create New...

[WL2]Wasteland 2 mod injector l'outil indispensable


Recommended Posts

En attendant quelque chose de mieux voici l'outil principal de modding sous Wasteland 2.

http://www.nexusmods.com/wasteland2/mods/10/?

Les notes du développeur :

 

 

This tool allows to inject/replace code within the game in a way that increases mods compatibility (with both other mods, and with official patches). It also allows to define mod's settings, thus making them easily customizable by players. Requires a Windows platform with NET Framework 3.5 or above. v 1.0.3 changes : - Fixed fatal error on 32bit OS (replaced ildasm.exe x64 by the x86 version) - Fixed bug that prevented to uninstall mods if no valid mod was found v1.0.2 changes - Fixed fatal error with GOG version (now Assembly-CSharp.dll is searched in all subdirectories) - Fixed fatal error when system used neutral culture code (e.g. : "ru"). - Fixed false positive security error for class name starting like forbidden namespace (eg "System.RuntimeTypeHandle") (see changelog tab for full changes from older versions) Decompress the archive directly (do not tell you zip extractor to create subfolder) in Wasteland2 folder (e.g. : "C:SteamSteamAppscommonWasteland 2"). Wasteland2ModInjector.exe must be within "Wasteland 2" folder (not in a sub-folder). Same as for installation + ovewrite all files when asked by your zip extractor. To install a Wasteland2ModInjector-compatible mod : - Close the game if it's still running. - Copy mod's .xml file into the "Mods" folder (e.g. : "C:SteamSteamAppscommonWasteland 2Mods") - Launch Wasteland2ModInjector.exe and wait (the process may take a few minutes depending of your computer) - Close the game if it's still running. - Remove corresponding mod's .xml file from the "Mods" folder (e.g. : "C:SteamSteamAppscommonWasteland 2Mods") - Launch Wasteland2ModInjector.exe and wait (the process may take a few minutes depending of your computer) Go in the "Mods" folder and find the .xml corresponding to the mod you want to customize, and open it with a text editor. The settings are between <settings> and </settings> ; if you can't find them the mod can't be customized. You can modify the value attribue for each setting, for example assuming a mod define following setting to mod the character running speed : <setting key="speed" default="12" vanilla="6" /> Replacing it by the following line <setting key="speed" default="12" vanilla="6" /> Will double the speed value relatively to mod's default (and quadruple the speed relatively to vanilla). Depending of the mod and the targeted Wasteland2ModInjector version, the setting tags may have more (or less) attributes than in this example. You should only modify the value attribute (as show before) and leave the other attributes (if any) unmodified. Once customized, close the game if it's still running, then launch Wasteland2ModInjector.exe. Unlike many games Wasteland 2 do not use a sandboxed script engine ; instead almost all its code is hard-coded in an executable dll file. This means mods that modify game's code also contains non-sandboxed executable code with privilege as high as the user that launch the game. Most (if not all) anti-malware / anti-virus wont help much, since game's dll needs to read, write and delete files for totally legit purposes (savegames, exporting characters, etc.). Wasteland2ModInjector will scan mod's code before installation to detect possible harmful code (input/output calls, external executable's execution, ...) and will not install the mod if mod contains such code, but I'm not a security/.net framework expert so it might not be bulletproof. If you install mods, I recommend you to launch the game from a sandboxed environment to protect your data from malicious access/modifications. That being said, using a ready-to-use modified Assembly-CSharp.dll file isn't safer at all... - The game doesn't work anymore !!! Try removing every mods (see Mod Removal section). If it still doesn't work, go in Wasteland2BuildWL2_DataManaged folder, delete Assembly-CSharp.dll, and rename Assembly-CSharp.dll.bak.yyyyMMddHHmmss (yyyyMMddHHmmss is the date : 4 digits for year, 2 for month, etc.) to Assembly-CSharp.dll. You may have multiple Assembly-CSharp.dll.bak.yyyyMMddHHmmss files, choose one corresponding to a date when the game was still working (you do NOT need to run Wasteland2ModInjector.exe after that). - I saw a big vanilla.il file in Wasteland2ModInjector folder, can I delete it ? (Cuz I like deleting files ! ) Well, Wasteland2ModInjector will still work even if you delete it but the next mod installation/removal will me much slower, and it will recreate it anymay (Cuz I like creating files ! ). XML description : Look at Mods/template._xml for an example, the xsd schema is with the source if needed. <mod> Attributes : - name (required) : mod's name. - version (required) : mod's version. - author (optional) : you... - link (optional) : link to mod's webpage (take care to replace & character by xml entity) <settings> (optional) <setting> (optional, required if <settings> is defined, possibly multiple) Attributes : - key (required) : setting's name (don't ask me why i didn't named it "name"...) - value (required) : setting's value... - vanilla (optional) : vanilla value if applicable. <patch> (required, possibly multiple) <from> (required) String from where the vanilla code will be replaced by <replacement>'s content. Only one occurrence of this string must exist in the IL code. <to> (optional) String to where the vanilla code will be replaced by <replacement>'s content (the search starts from the end of <from> string's). If this tag is omitted, replacement will ends at the end of <from> content. <replacement> (required) The replacement code... To reference settings, use $$key$$. Notes : - <from> <to> <replacement> should be within CDATA tag (white-space matter ! ). - line break are normalized, so it should not matter what text-editor settings you use. Copyright © 2014, OVNI All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this    list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice,    this list of conditions and the following disclaimer in the documentation    and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

















== Wasteland2ModInjector installation ==





== Wasteland2ModInjector updates ==




== Mod installation ==







== Mod Removal ==






== Customize Mod's Settings ==






value="12"

value="24"







== Security Warning ==










== TroubleShooting ==










== For modders ==



























































 

 

 

Ce serait pas mal de traduire certains passages en français ou de faire un tuto/screenshots pour aider à comprendre comment ça marche.

Est-ce que quelqu'un s'en est déjà servi ?

Link to post
Share on other sites
  • 2 weeks later...

L'outil de modding fonctionne aussi sous windows 8.1, il suffit de copier le fichier ilasm.exe 

qui se trouve dans votre dossier :

WINDIR%Microsoft.NETFrameworkv4.0.30319ilasm.exe

pour le mettre dans :

Wasteland 2Wasteland2ModInjectorTools

Link to post
Share on other sites
  • 3 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.