Is it possible to rename the individual mod folders sitting in the Community folder to something of your choosing without  breaking the mod? All modders have their own folder naming conventions and when looking through these, it is sometimes difficult to know at a glance what each mod is. Especially for scenery objects such as stadiums, towers and bridges, but also liveries etc.

For example, one good freeware livery's title is "OperatorLand468-livery-a320NeoBA". Could this be renamed to something simpler and neater like "Livery A320 BA" for example?

It's a minor OCD thing but does anyone know - before I go and experiment and risk crashing the sim?

Yes......however if you have PAYWARE like ORBX which also places stuff into the community folder, I would advise not renaming because when ORBX update their product via ORBX Central you will end up with another folder layed down.  Unlike the freeware stuff which is usually a manual copy and paste.

1 hour ago, RaptyrOne said:

Is it possible to rename the individual mod folders sitting in the Community folder to something of your choosing without  breaking the mod? All modders have their own folder naming conventions and when looking through these, it is sometimes difficult to know at a glance what each mod is. Especially for scenery objects such as stadiums, towers and bridges, but also liveries etc.

For example, one good freeware livery's title is "OperatorLand468-livery-a320NeoBA". Could this be renamed to something simpler and neater like "Livery A320 BA" for example?

It's a minor OCD thing but does anyone know - before I go and experiment and risk crashing the sim?

Hi,

Yes, it is possible to rename most of them. But, do not use space and some strange characters. For example this is a common use

scenery-monaco-vfr   or   airport-kmia-miami-international  or livery-a320-thy  or  utulity-a30nx-fix  ....

Edited October 2, 20205 yr by kt069

I have prefixed all my freeware with LIV MOD FIX SCE etc.  This means I can quickly sort it by sensible groups.  However take note of my previous comment about payware folders.

20 minutes ago, kt069 said:

Hi,

Yes, it is possible to rename most of them. But, do not use space and some strange characters. For example this is a common use

scenery-monaco-vfr   or   airport-kmia-miami-international  or livery-a320-thy  or  utulity-a30nx-fix  ....

Whay not using space? These times are long long time ago.

32 minutes ago, Nemo said:

Whay not using space? These times are long long time ago.

I think it is a limitation in the developer tools. I had spaces in the names of some scenery I was working on, and it treated each word in the name as a separate file and broke everything. I agree with you, the tools should be able to handle spaces, but apparently they cannot. 🤷‍♂️

1 hour ago, sidfadc said:

I have prefixed all my freeware with LIV MOD FIX SCE etc.  This means I can quickly sort it by sensible groups.  However take note of my previous comment about payware folders.

That's exactly what I would like to do, yes!  Will make it so much easier to identify each and organize them. Noted on the payware. Agree, I would be careful not to touch those. I only have one payware addon so far and even when I ran the patch update the other night, I chose not to remove that from the Community folder.

Also keep track of the mod download links as they made need to be updated after each patch, especially if they fix something in the game. Keeping a list where each mod came from now seems to be mandatory.

I read here on the forums that you need to be aware that these mods load into the game in sequential order (numeric and/or alphabetic).  So if the mod begins with the number 1 the remaining number mods will load, followed remaining (first letter alphabetic) mod loading.  Depending on what these mods do, they may overwrite functions prior loaded mod.

13 minutes ago, Mike S KPDX said:

I read here on the forums that you need to be aware that these mods load into the game in sequential order (numeric and/or alphabetic).  So if the mod begins with the number 1 the remaining number mods will load, followed remaining (first letter alphabetic) mod loading.  Depending on what these mods do, they may overwrite functions prior loaded mod.

Using a prefix like L+ for livery or M+ for mods will keep the foilder name in the proper order. Changing the name itself could be problematical.

Vic

I would have liked to add folders to the community folder so that each folder would contain ie; liveries, aircraft, mods, scenery, etc

It's becoming a mess with just a jumble of names/letters/numbers.

 

4 hours ago, trevg said:

I would have liked to add folders to the community folder so that each folder would contain ie; liveries, aircraft, mods, scenery, etc

It's becoming a mess with just a jumble of names/letters/numbers.

 

I'm sure most of us would prefer a system like that. For now though, the best option seems to be as suggested above, prefixes. Some examples of mine:

 

AIRPORT_USA_airport-6wa2-v01-beta

AIRPORT_USA_airport-kcgx

AIRPORT_USA_aquilasim-nasa

...etc, then:

MOD_[GROUND-SERVICE] Goldhofer-Tug_v2_by_DaStrobel

MOD_GateGourmet-Catering v1.2

SCENERY_baddweapon-scenery-alaskawaterheightfix

SCENERY_CAN_toronto

SCENERY_IRE_connollystation

 

The bold parts are my added prefix to the original add-on name. Note the underscores in lieu of spaces. For scenery files, I've added country codes (CAN - Canada, IRE - Ireland etc). Seems to be working fine so far...

 

Edit: of course, not adding prefixes to anything from payware developers such as ORBX in case they don't update properly.

Edited October 3, 20205 yr by 109Sqn

19 hours ago, Nemo said:

Whay not using space? These times are long long time ago.

It is sensible to avoid characters that may be misinterpreted by scripts and other coding, examples of things to avoid are spaces and commas as they are often database separators and # because in many languages it is a comment.  You are free of course to use these characters and see if there is an issue,  but it is often simpler to just avoid them from the get-go.