Dev Blog 21/09/17

Norwood · Sep 21, 2017

I'm curious... you only mention Visual Studio 2015, does this mean that Visual Studio 2017 won't be supported for some reason?

Lumos · Sep 21, 2017

Norwood said:
I'm curious... you only mention Visual Studio 2015, does this mean that Visual Studio 2017 won't be supported for some reason?

While it's odd that they don't mention 2017, not being able to use 2017 would be extremely unlikely - can't think of any reasons that would make that logical. I assume the devs are simply using 2015 internally, and that's why they mentioned only that version in their reply.

Ki-Ok Khan · Sep 21, 2017

Great blog!
My question for the QA team ;
-What kind of processes do you go through while testing scenes and campaign?

I am too eager to learn about this , simply because I worked at automating tests / testing as an intern for a while.
Please gib answer

Norwood · Sep 21, 2017

L̨u҉m͞o̧s̡ said:
Norwood said:

I'm curious... you only mention Visual Studio 2015, does this mean that Visual Studio 2017 won't be supported for some reason?

Click to expand...

While it's odd that they don't mention 2017, not being able to use 2017 would be extremely unlikely - can't think of any reasons that would make that logical. I assume the devs are simply using 2015 internally, and that's why they mentioned only that version in their reply.

The only reason I can think of is if they are developing some sort of plugin that only works with the 2015 version.

Lumos · Sep 21, 2017

Yeah. The debugger, perhaps. Ah, who needs debugging anyways? We've been faring just fine without it. :lol:

VVyrd · Sep 21, 2017

Awesome blog! Decently long and very interesting, certainly has upped my hype for the game itself and everything we will be able to do with all those tools. Just hope the script system isn't too limited for us programmers - Really like to add new features that actually feel new, rather than having to go through tedious work-arounds that rely on already existing features. This is something that Paradox games do really, really badly, where modding always consists on changing the game's text on most features, and that's about it.

JuJu70 · Sep 21, 2017

Unlike Warband, the vanilla game scripts will not be directly modifiable by modders.

that's strange and worrisome. Does it mean I can't change the native script and have to reinvent the wheel? Will I be able to see them at least?

UghUghUgh · Sep 21, 2017

I would have loved to have more info on the sieges. In Warband there was either a fixed ladder or a moving siege tower and just two points of defence and a spawn point for reinforcements (if I remember correctly).

If you are going to revisit the scene editor, please explain the options that were surely added to give the AI some directions. How does the AI decide, which point to defend and when to give up and withdraw? Is there anything that is already part of the scene editor? The level of complexity has increased a whole lot and AI coding is probably one of the reason why the game keeps getting delayed.

Swyter · Sep 21, 2017

Cool stuff! Duh has done a great job selecting the questions for the most part. Hopefully the inner logic of the game will still be exposed at a low level so that people can misuse features to their advantage.

As unlikely as it is that old school modders return to Mount&Blade it is nice seeing some recognition and future support to those that have extended the lifetime of the games with their work.
We've never had a lot of direct support for even the most basic documentation of things like flags or file formats. People like mtarini and cmpxchg8b had to reverse engineer most of it.

We didn't even have enough information to import custom skeletal animations into the engine until well into 2009, when mtarini was so fed up with the limitations of BRF Edit that began OpenBRF while working on TLD!

The community has always been doing all the heavy lifting, so this looks like a change of pace.

gypsydevil · Sep 21, 2017

Another Thursday, another great blog. Lot's of detail. Cool,Cool,Cool.

Lumos · Sep 21, 2017

JuJu70 said:
Unlike Warband, the vanilla game scripts will not be directly modifiable by modders.

Click to expand...

that's strange and worrisome. Does it mean I can't change the native script and have to reinvent the wheel? Will I be able to see them at least?

Doesn't make sense for us not to be able to see what's going on. That answer's a little vague indeed, but my assumption is that the "Native" scripts and logic will be "chunked" into relatively small segments (individual scripts?), which we won't be able to fiddle with per se, but overwrite at will (according to a load order, which is how "multiple mods at the same time" could work). I'm more than certain we'll be getting the equivalent of a "Native source" folder - nobody could possibly expect modders to figure the whole thing out without looking at the real code.

Yabloko · Sep 21, 2017

Pretty neat, even if I only understood half of the answers.

Kuroodo · Sep 21, 2017

For next weeks blog, since you're interviewing the QA Lead, I'd like to ask what was one of the strangest or funniest bugs that they've experienced during QA.

usnavy30 · Sep 21, 2017

Awesome blog today

A good portion of the modding questions answered, and I can appreciate that Taleworlds takes the time to respond thoroughly to them.

kraggrim · Sep 21, 2017

Best blog ever.

QA question: What's the most fun aspect to test in BL?

Varrak · Sep 21, 2017

18. Will it be possible to alter where the AI aims with ranged weapons?

You can give them an entity to target.

monoolho · Sep 21, 2017

Rodrigo Ribaldo said:
The performance tool is a topping on the cake. Anyone who had a mod out there tried to judge by ear how to balance beauty with performance.

Have to agree with that.

AWESOME BLOG. Seriously, you guys. You just made my heart tingle. Modding now will sound so... easy compared to text-editing and python (which I never managed to learn at all).
This blog fulfilled my mind with the inner terrors of modding it wanted. But I will control myself, at least 100h I must spend on vanilla, and only then will I mod... It's only fair. It's like being on a diet and going to a eat all you want buffet, you have to have discipline.

I have no questions for the next blog, not at this time at least. Too bad I couldn't ask the ones before, I had some stuff I thought would be nice but anyway, I thank you with all my heart for you gave me my heart's content today. This will be a good week.

EDIT: Just saw it now, and I second this question.

Kuroodo said:
For next weeks blog, since you're interviewing the QA Lead, I'd like to ask what was one of the strangest or funniest bugs that they've experienced during QA.

This. This is a good question. Some insider 'blooper reel'. That's funny and interesting stuff. If videos/.gifs are available, that's a must in the blog.

lolxd · Sep 21, 2017

do we need to compile the C# script? or just put that C# script in human readable format just like javascript files?

Duseda · Sep 21, 2017

Well, i really liked those news cant wait :3

Count Delinard · Sep 21, 2017

Duh said:
I am really happy about this blog Thank you Callum and Taleworlds (especially everyone that sat down and read and/or responded to our wall of text)! And thank you to everyone that contributed questions in the Forge!

Shameless forge self-promotion

Also, already congratulated you privately but indeed great work Callum and everyone who sat down to think answers for each question!!

Dev Blog 21/09/17

Users who are viewing this thread

Recruit

Archduke

Ki-Ok Khan

Recruit

Archduke

Knight at Arms

JuJu70

Squire

Grandmaster Knight

Squire

Archduke

Sergeant Knight at Arms

Recruit

Grandmaster Knight

Marquis

Baron

Knight

Veteran

Regular

Lord of Uxkhal

Global Moderator

Similar threads