新手想学习做MOD几个基础问题，请教

牛肉火锅

1：比较好上手的是不是已经发布源代码的那个，比如我想做潘德子MOD的子MOD，没有源代码，能做些什么呢？我主要是想先调调技能效果什么的就行。魔球没法调试脚本吧，只能设置装备兵种一类的。没源代码的话，反编译的不一定对是么

2：PYTHON还是必须要用2.6吗，然后战团源代码是最新只有1.171么。我系统是WIN11
3：有靠谱的反编译工具吗。他们大佬做的都是用战团发布的源代码，然后自己去写需要的源代码来实现自己想要的功能的是吗。正常情况写，如果没有作者自己开源，是没有办法靠反编译去做局部修改的吧？我说的不是数值上的，是功能上的
4：如果只能自己写代码，哪里有骑砍的指令库可以查吗，还是说没有这一说。。
问题都很小白，大家请见谅。。希望大佬们不吝赐教，谢谢

杰喵喵

老老实实先从战团代码看看起吧，B站有三啸(朱红之恋)很基础的手把手教学视频

牛肉火锅

杰喵喵 发表于 2025-10-31 23:24
老老实实先从战团代码看看起吧，B站有三啸(朱红之恋)很基础的手把手教学视频 ...

谢谢大佬回复，我看了置顶那个视频了。第二节视频没了。必须看B站上的是么，我去看看，就是这个源代码门槛卡的死死的感觉

huagao

看到潘就不想回答了。。
反编译就可以做所有ms能做到的修改，实际上读TXT不是不行，主要是机器码的可读性和复用性很差。另外不要迷信反编译，半吊子东西越用越没出息。
裸装MS是不能用Python3的，之前有人发过修正版的，得你自己找
指令库。。你想问的是API手册吧。。。operation和common基本都在这两里面了，前者是能用的函数，后者里面有关于编译的基础原理。来自: Android客户端

牛肉火锅

huagao 发表于 2025-11-1 09:10
看到潘就不想回答了。。
反编译就可以做所有ms能做到的修改，实际上读TXT不是不行，主要是机器码的可读性和 ...

好的，谢谢大佬解惑。。。主要是潘德现在玩的比较多，所以想修改下自己想要的玩下，她城他们那个源代码是找作者要的吗，还是潘德开源了呢。。
总之谢谢大佬，没源码还是不去费劲了，钻研下R大的领军者吧

huagao

牛肉火锅 发表于 2025-11-1 10:19
好的，谢谢大佬解惑。。。主要是潘德现在玩的比较多，所以想修改下自己想要的玩下，她城他们那个源代码是 ...

潘德是没有源码的，只能自己琢磨txt。领军者这块确实是美食榜第一，多看有好处

zrcs

对我们这些玩儿家来说改MOD好过完全做MOD,做MOD很多方面不擅长，我只擅长搬运模型改数据，就是一些基础功都难以搞定，比战后自动收俘虏，战场小地图等等。一些MOD本身功能齐全，比如领军者，三国魂等等用来改改，简单高效模型数据飞起，关键这些MOD完全体验过，没有什么影响游戏玩儿下去闪退的严重BUG，其他MOD可能就没有这么好命，就是感觉改MOD已经很累了，我真的佩服那些做MOD的高人，就是毅力就比不了。

牛肉火锅

zrcs 发表于 2025-11-1 10:58
对我们这些玩儿家来说改MOD好过完全做MOD,做MOD很多方面不擅长，我只擅长搬运模型改数据，就是一些基础功都 ...

是的哈，现在没那么多时间了。如果再回到刚毕业那会或者大学时代，就接触玩骑砍了，我估计我都能抽空去好好自学编程了，现在只能靠着简单的一些修改游戏经验去改改MOD玩。兴趣确实是学习最好的动力

112233lyh

她城他们拿txt硬改的，硬改的结果就是，做同样的东西要比别人花几倍的精力，还会因为难以排查的问题报错。哪怕是潘改中最顶部的那批，绝大部分顶天了也就到处扒功能，没什么功能上的创新。
硬要搞的话，这几天有两个逼正在测试特殊办法整出来的潘得源代码，可以蹲一下。不过就算是完美反编译的，注释、common和局部变量命名都没了，可读性极差。来自: Android客户端

奥杜因阿卡托什

1.做潘德很有钱途，但是没什么前途。等你技术强到能在潘德上加功能时，你会发现熟悉它的txt的时间，足够你给它的功能、任务、系统全部在战团上复现一遍了。
2.我用的2.7；对。
3.一般用codeeditor，不过这个格式比较老，不能直接用。而且就像上面一条说的那样，反编译的东西比真正的源代码缺少了很多很多信息。
4.指令库的话下个ms，里面的header_operation就是所有操作符。然后script是允许你自己写的封装好的脚本，某种意义上也相当于操作符。

偃靖

刚开始学不用考虑反编译，可读性太差。建议学习native和领军者。这俩的源码都是不错的学习资源。还能对比两者的代码和功能，对比对学习帮助也比较大。

牛肉火锅

112233lyh 发表于 2025-11-1 13:41
她城他们拿txt硬改的，硬改的结果就是，做同样的东西要比别人花几倍的精力，还会因为难以排查的问题报错。 ...

好的，明白了，也解惑了。就不死磕了，学习R大的领军者中

112233lyh

牛肉火锅 发表于 2025-11-2 22:06
好的，明白了，也解惑了。就不死磕了，学习R大的领军者中

学习代码可以来68181940这个群，大部分在世作者都在里面。来自: Android客户端

gsanders

偃靖 发表于 2025-11-2 04:33
刚开始学不用考虑反编译，可读性太差。建议学习native和领军者。这俩的源码都是不错的学习资源。还能对比两 ...

  I agree with this post.

  For me, I started with wanting to add a feature (Wife as a companion) to a mod I was playing at that time (summer 2014) "Brytenwalda", which had source code.  I just wanted to add that ONE feature, so I left the rest of the code as it was.

   I later tried the same thing for Gekokujo, since that ALSO had source code.
   I noticed not that many mods had source code, besides Native.  Modders loved their secrets!

   Sometime later I noticed Perisno had an issue with dialogs -- all the races except humans responded as if female gender.  The point was at each mod I focused on changing ONE thing only, and then tested that working, and changed one more thing ... and a few thousand repeats later became a "modder".  I never, ever, went from a blank screen to a finished mod, it was always a slow evolution of something that worked into something that (sort-of) worked much later but with a few hundred changes along the way.

   Something that would have saved a lot of time at the beginning was when I noticed I did not have to "guess" what each line did, but "edit" header_operations.py  to see the exact syntax of each line.  
Of course that file is in English, so if you have trouble reading my replies you have two barriers, not one, keeping you from modding.

  There are some excellent walkthroughs on modding Warband at Taleworlds forum.

  From there, I would say many of the older mods source used syntax specific to earlier Warband versions, and sometimes the source makes assumptions about the run time environment that changed over time.
I specifically see that with anything using Modmerger, where the old modmerger kits assume specific code to search for in the module system to use as a roadmap of where exactly to insert some new code and those lines are changed or gone in a later native version.

   95% of mods kept the native code someplace, and added small extensions or dropped in OSP kits for some function that seemed cool at the time but with very little re-thinking happening.  This tends to produce frankenstein mods that have a checklist of "must have" features but are glitchy because the add-in code OSP kits each assume they are the ONLY non-native code and tend to re-define the same slots for data storage in game for their own special purposes.

  I ended making an excel file to keep my slots assignments without re-use of the same "unused" slots so I could juggle all the add-ins against a master list of "used" and "unused" locations.  This came from something I saw at Silverstag and I am grateful for it, as mods that did not do this had a fair number of glitches that could have been prevented by a few days review.  For example, in Paradigm Worlds the author had a large number of add-in functions, with around 30 preventable glitches that I found in a 2 day review of the code before remaking it as "Paradigm Chronomancer".  Of course, I did not just cut and paste his old code when remaking a mod - I went through nearly every single line and remade them, which took most of a year instead of two months slash and burn as I first planned.  

   You can spend a great deal of time working on a mod and if you only want to add some cute graphics or something new then you can still burn a great deal of time trying to understand what the original code thought it was doing.

   I strongly do NOT recommend trying to disassemble or direct edit text files to guess what they do.  
There are too many places where something you want is spread across several places in the code and you would have a much easier time finding all of those places if you have the original source code.  This just means you limit your remakes to mods with source included.

   I included all my source at Phantasy Calradia 2024 version and Paradigm Chronomancer, before that I kept the source closed like everyone else, in part to protect other people's assets (such as Perisno or Warsword Conquest).  Also I specialized in coding deep mechanics and not eye catching graphics, so mostly I used other peoples art at existing, dead or dying mods and remade the code internals.  This is why I have a long resume of mods I made "layers" of but few mods I made start to finish alone.  The list is fairly large though.

  My advice anyway.