Hello! I put the "/" to try and fix the problem but the bat is still showing the same information as the previous post.
this is what the module_info.py looks like now
# Point export_dir to the folder you will be keeping your module
# Make sure you use forward slashes (/) and NOT backward slashes (\)
export_dir = "D:/stuff/steamapps/common/MountBlade Warband/Modules/Native - Personal mod/"
#export_dir = "C:/Program Files (x86)/Mount&Blade Warband/Modules/Native/"
when I run the bat as admin this is what I get
python: can't open file 'process_init.py': [Errno 2] No such file or directory
python: can't open file 'process_global_variables.py': [Errno 2] No such file or directory
python: can't open file 'process_strings.py': [Errno 2] No such file or directory
python: can't open file 'process_skills.py': [Errno 2] No such file or directory
python: can't open file 'process_music.py': [Errno 2] No such file or directory
python: can't open file 'process_animations.py': [Errno 2] No such file or directory
python: can't open file 'process_meshes.py': [Errno 2] No such file or directory
python: can't open file 'process_sounds.py': [Errno 2] No such file or directory
python: can't open file 'process_skins.py': [Errno 2] No such file or directory
python: can't open file 'process_map_icons.py': [Errno 2] No such file or directory
python: can't open file 'process_factions.py': [Errno 2] No such file or directory
python: can't open file 'process_items.py': [Errno 2] No such file or directory
python: can't open file 'process_scenes.py': [Errno 2] No such file or directory
python: can't open file 'process_troops.py': [Errno 2] No such file or directory
python: can't open file 'process_particle_sys.py': [Errno 2] No such file or directory
python: can't open file 'process_scene_props.py': [Errno 2] No such file or directory
python: can't open file 'process_tableau_materials.py': [Errno 2] No such file or directory
python: can't open file 'process_presentations.py': [Errno 2] No such file or directory
python: can't open file 'process_party_tmps.py': [Errno 2] No such file or directory
python: can't open file 'process_parties.py': [Errno 2] No such file or directory
python: can't open file 'process_quests.py': [Errno 2] No such file or directory
python: can't open file 'process_info_pages.py': [Errno 2] No such file or directory
python: can't open file 'process_scripts.py': [Errno 2] No such file or directory
python: can't open file 'process_mission_tmps.py': [Errno 2] No such file or directory
python: can't open file 'process_game_menus.py': [Errno 2] No such file or directory
python: can't open file 'process_simple_triggers.py': [Errno 2] No such file or directory
python: can't open file 'process_dialogs.py': [Errno 2] No such file or directory
python: can't open file 'process_global_variables_unused.py': [Errno 2] No such file or directory
python: can't open file 'process_postfx.py': [Errno 2] No such file or directory
Could Not Find C:\WINDOWS\system32\*.pyc
______________________________
Script processing has ended.
Press any key to exit. . .
However, when I run without admin, I get the result that I posted previously.
Do we still need to follow the environmental variables step according to Lumos guide?
https://forums.taleworlds.com/index.php?topic=240255.0
This is what his guide says
Are you finished with the theory? I want to start modding now.
Yes, I am. So, now let's start the modding. You want to setup a Module System, don't you? Well then, just go to the thread where we summarise downloads (found in this same board... or if you click here) and get yourself a fresh ModSys for your particular game of choice. (You're looking for the "Download Module System" section, can't miss it!)
Now. In order to be able to compile the files into game-readable text files, full of numbers and numbers and numbers, and to make your awesome mod come true, you need Python (the language). Having a real pet python might help, but don't count on it. Now, don't go rushing into downloading the latest Python. Here's something really important that you should know: The ModSys does NOT work with any Python newer than 2.x*. Fortunately, the same thread you've already got open also features a link to the Python website, so you've been saved a Googling; grab the latest 2.x.x version from there.
Now all you have to do is to install Python. Using Admin rights, please. Oh, it's a good idea to install it in its preferred C:\Python27 directory (if you're still using Python 2.7 in your day and age, oh reader from the future!).
Next up. Go to your Environment Variables to see if everything is OK. For those that don't know what Environment Variables are - well, these are OS things, which your Windows uses. You will only have interest in the "PATH" variable. Now open that window and get to business.
(click to show/hide)
Windows XP: My Computer (right-click) -> Properties -> Advanced -> Environment Variables
Windows 7, 8: My Computer (right-click) -> Properties -> Advanced system settings -> Environment Variables
and he also says
Scroll that list until you find the "Path", then click it and hit the "Edit" button down there. This Path variable is basically just a string of paths to certain things which are important for your OS. It's different on every computer.
In order for your compiler to work without any hacks or fixes, you must have your Python folder in your Path variable. For an example, if you did install your Python in C:\Python27, then you should add ;C:\Python27 at the end of the Path. Do NOT alter the Path in any other way! As it contains important system stuff, it's definitely NOT recommended. Just add that ;C:\Python27 if it's not there. I think it won't be there, since I had to enter it manually. I think.
Anyways, notice the semicolon (
that is before the C:\Python27. Entries for different applications are separated with semicolons in the Path variable string, so you should add that semicolon so your OS knows what you're talking about.
And that's about it for setting Python up.
* That's actually a lie. If you're familiar with Python, you're free to re-write the Python "compiler" that the ModSys uses, and thus convert it to Python 3.
That's all part of the guide I copied but from here on its just me
I used that guide but found that all the variables were already there when I installed python....I think...Also I am running windows 10 if that helps in any way. Sorry for all the trouble, apparently I suck pretty bad at this stuff.
Thank you for reading!