Settlement Menu System

[Xgf]

Settlement Menu System

I'm very concerned about the modders freedom.

- the menu system is based on formlist (form list are awesome for modding without conflict)
- when the CK is available there is a method (AddForm) you can form list dynamically expand.

When the CK is available, eeveryone modder can expand the menu, without being in conflict with other mods.

I tested all and can prove it at any time!

Such as Mod Settlement Keywords creates an artificial restriction and a monopoly.

Please help to prevent

[AceSevenFive]

Here's what I gathered from this post:

 

-Formlists are good for avoiding mod conflicts.

-The Creation Kit has AddForm available to add to formlists.

-Once the Creation Kit comes out, everyone can expand the menu without conflicts.

-SK has a monopoly [because a combined effort is good.]

-The OP doesn't speak English natively.

[Xgf]

yes sorry for my english. it makes it very difficult for me to thematize this, and to show the problems. I hope they understand the sense

all good except one

>>>because a combined effort is good
because they downgrad a dynamic extensible system (for anyone without conflict) to a static.

if I agree to SK and deveop a mod based on SK, and I have an idea for an new menuentry, It's not allowed for me to do it!

From the SK Homepage:
>>>These are modifications that completely rely on the Settlement Keyword system. They follow two rules:
>>>- 1. They don't add any Keywords.
>>>- 2. They don't add any of their own FormIDs

But there is no technical need for this. I have worked for four years with the CK and Papyrus. If you have only the view of FO4edit then there is missing so much.

 

As I said can prove it. It lacks only the CK and 5 lines papyrus code, the rest I have already created.

It is not a question of majority. It is a matter of technique. Therefore, to know they, this requires the CK and Papyrus!

PS:

http://www.creationkit.com/FormList
http://www.creationkit.com/FormList_Script

The methode exists also in Fallout4
.Fallout4\Data\Scripts\FormList.pex

Edited February 28, 2016 by Xgf

[AceSevenFive]

Actually, there is a technical need. While I do concede that SK was mainly built around Homemaker [in my opinion], the alternative is hitting the keyword limit, which is not fun. SK reduces this risk by encouraging mod developers to work within a specific framework. If a mod developer can provide a good reason for adding a new keyword, it'll be added.

 

If you don't think that SK should have a monopoly, you're more than welcome to implement your own version. Who knows, it may even be better than what we have now.

[Xgf]

>>>Actually,
At the moment yes ........ but soon no longer.

Just imagine .... the system would be of bethesda (it is!!... SK it only expands and restrict it).
And bethesda would say: "They don't add any Keywords." and "They don't add any of their own FormIDs" it would go a scream through the community. It would be heard until the end of the solar system :smile:

>>>>If a mod developer can provide a good reason for adding a new keyword, it'll be added.

Ahha .... it goes exactly about that ....and who determines whether it is a good idea, and how long does it?

Edited February 28, 2016 by Xgf

[PoliteRaider]

I'm sorry but I don't understand your point.

 

You certainly don't have to use the SK framework if you don't want to. It's a very popular community standard because it works well and got in early, but it's certainly in no way compulsory.

 

Personally, even if the technical issues with keywords and formlists were completely resolved, I'd still want some form of community standard. Just to make sure that I don't have 120 categories in my workshop list, some with a couple of items and others with hundreds. I'm happy with the way SK works, although if a superior framework were developed then I'd be happy to use that too, so long as it could get enough community support to make it worthwhile.

[Xgf]

I'm sorry but I don't understand your point.

 

You certainly don't have to use the SK framework if you don't want to. It's a very popular community standard because it works well and got in early, but it's certainly in no way compulsory.

 

Personally, even if the technical issues with keywords and formlists were completely resolved, I'd still want some form of community standard. Just to make sure that I don't have 120 categories in my workshop list, some with a couple of items and others with hundreds. I'm happy with the way SK works, although if a superior framework were developed then I'd be happy to use that too, so long as it could get enough community support to make it worthwhile.

 

Are you so sure?

 

- SK has renamed all Vanilla Keywords, all Formlists and move. vanilla menu entries. That would not be necessary.

- SK does not have support for the String Files it is language dependent and needs to be translated. Again a source of errors

 

I am a script writer (also professionally) and have a lot of experience with the papyrus language I can handle this. But it is an additional workload and also more testing.

 

I have already problems with user they have "SK" loaded. They come to me. from SK helps no one! But yet I do nothing except I insert a a few of new constructible objects.