Search results for query: *

It's nice and all but I find that manually editing XML files is a terrible practice anyway...
It's pretty easy to load and edit XML files in C#, that way multiple mods could modify the same file

Don't listen to that guy.
The real answer here is that you usually never need to do unit testing when creating mods, that's just overkill. Usually we do unit tests on a very low level, and this is never done at runtime, but rather at compile time (or when submitting if you have a build validation process).

What you should do instead is secure your code with asserts and logs, that are only enabled in Debug for performance reasons.
The reason is that in case the API changes or if you do some massive changes in your code, you should get notified if weird things happen. That's the proper way to code.

szszss said:

I googled the vector field and I learnt that it's a kind of particle system. This should be correct because all PVFs are in the particles package. Whatever, it's beyond my knowledge.
Anyway, it's not a high priority task. There are only two PVFs in the game assets, and they even don't have regular names. Seems that even Taleworlds doesn't take it seriously.

Click to expand...

Not exactly, a vector field is like a 3D area (field) where for each point, we can indicate a direction (vector). Usually this is represented using a 3D texture, where the rgb values represent a 3D vector (not necessarily normalized). You can think of it as a 3D flow map if you are familiar with that.
This is usually used for particles as you mentioned, to simulate wind or some kind of motion on particles on a small scale.

Now about the procedural part, I'm really not sure what they mean by this. It could be that the vector fields can be created on the fly and can change over time, so that they don't need to store a 3D texture for that, but instead it's represented by mathematical functions.

I didn't notice any example of them being used in the game so far (maybe on the title screen?), so yeah, probably not the highest prio for now.

You were saying in your github that you needed help with force fields. What do you need to know about that?

This save ID thing is not very clear for me either, I believe TaleWorlds generate theirs at compile time so we can't really see what they do from decompiling the libraries.
Maybe a good way would be to hash the full name of your mod (com.yourcompany.yourapp)
Or maybe the game already handles IDs per submodules so you can use any ID you want
This is an area that still needs a lot of research

Could you also add the other submodule events and examples from the StoryMode submodule for instance?
Would be great to have a description of what we are supposed to do in each event and how they relate to the events of the vanilla submodules

ramzamzam9 said:

Just a verry short question, as my coding knowledge is basic at best. Is there / or will there be a simple way of creating own quests? Like, I don't know, some kind of framework or guideline enabling potentialy talented writers with limited to no coding experience to create own quests.

Click to expand...

I believe this is fairly simple, there is relatively few lines of code to be honest. The most wordy part of this guide is the dialog flow. There might be a way to load dialog flows with XMLs, but I believe there is currently no way to do that. So even that you would have to do by yourself.
Otherwise for the quests logic, no other way around this sadly (But then again, not that difficult, might just turn into spaghetti if not made properly)

Ra'Jiska said:

Oh my, this is beautiful ! How do the helmets adapt to such deformations ?

Click to expand...

Pretty well actually! There is a tag for helmet deformation in skins.xml helmet_scaling_factor_min. Even without tweaking values, any kind of head gear adapts fairly well to the deformed heads.

I'm currently working on a mod (not a tool) that will apply these deformations on top of skin.xml so that it keeps the original XML fine if you ever want to disable the mod, and that should also work with mods that add additional deformations.

I could release it right now, but the loading/saving of deformation presets is not finished yet

Oops, sorry about that, I can't really share this on GitHub because that's just the project I use to mess around with the code, so it's very messy
I referenced all the game's DLLs so I didn't have this issue

I believe the bit of code you are mentioning is the check in OnGameStart right?
I believe this check is not necessary for creating a quest, that's just to make sure you only create the quests if your gamemode is the native mode. You don't want to create the quests for other gamemodes for instance.

If you still want this check, you will need to reference the following DLL from the StoryMode module:
Modules\StoryMode\bin\Win64_Shipping_Client\StoryMode.dll

Edit:
I edited the code and added a comment to make it clearer

He will look pretty much exactly like your character, I will update the screenshots if I get it working with other body types, so I can show it working with your child, parents, and brother characters

I made a guide just for that:

I'm guessing that's because there is an ambiguity with both classes.
Since you wrote `using TaleWorlds.MountAndBlade;`, you are accessing the TaleWorlds.MountAndBlade namespace.
You could use an alias instead `using MB = TaleWorlds.MountAndBlade;` if you really need to, but usually having a different class name is much nicer

You should use CampaignTime instead of DateTime, it actually matches the campaign time and you have many functions to convert time (seconds, ms, weeks, etc..), as well as elapsed time and so on