Modder prefix name list

Willkommen in der Transport Fever Community

Welcome to the fan community of Transport Fever and Train Fever, the economic simulators of Urban Games. The community is free for you to share and inform yourself about the game. We cultivate a friendly and objective interaction with each other and our team will be happy to answer any questions you may have.

 

Registration and use is of course free for you.

 

We wish you a lot of fun and hope for active participation.

The Team of the Transport-Fever Community

    Hi all, after just seeing irrelevant 's last Youtube I want to ask if and how we can create and manage a list of acknowledged modders and the prefixes we use for our models.

    Personally I'm using "bko_" for every mod I release. I do not only use it for the mod file itself but also for just about every folder or file within the mod that is created by me. This makes it very easy to recognise my mod files in debug mode and crash logs.


    Now I think for TPF3 we should make a list of 'acknowledged' modders and the prefix each uses. Can we do so, e.g. in a Lexicon entry, and more important how can we maintain such? Maybe only moderators should be able to adjust the list(?) or can we allow users to only add unique records to a table.. If we have a database I know such can be done, but I'm unsure to what extend the Lexicon has these capabilities.


    What are your ideas on this?


    --- using Google translate for German --- übersetzt mit Google translate ---


    Hallo zusammen, nachdem ich mir gerade irrelevant 's letztes YouTube-Video angesehen habe, möchte ich fragen, ob und wie wir eine Liste anerkannter Modder und der von uns für unsere Modelle verwendeten Präfixe erstellen und verwalten können.


    Ich persönlich verwende „bko_“ für jeden veröffentlichten Mod. Ich verwende es nicht nur für die Mod-Datei selbst, sondern auch für nahezu jeden Ordner oder jede Datei innerhalb des Mods, die ich erstellt habe. So sind meine Mod-Dateien im Debug-Modus und in den Absturzprotokollen sehr leicht zu erkennen.


    Ich denke, wir sollten für TPF3 eine Liste anerkannter Modder und deren jeweiliges Präfix erstellen. Können wir das z. B. in einem Lexikoneintrag tun und, noch wichtiger, wie können wir diese pflegen? Vielleicht sollten nur Moderatoren die Liste anpassen können oder können wir Benutzern erlauben, nur eindeutige Datensätze zu einer Tabelle hinzuzufügen? Wenn wir eine Datenbank haben, ist das möglich, aber ich bin mir nicht sicher, inwieweit das Lexikon diese Möglichkeiten bietet.


    Was sind Ihre Ideen dazu?

    Reply in German if you want, but allow me to stick to English.

    Like 1
    Quote from dview

    eine Liste der anerkannten Modder

    Die Fragen sind:

    * Wer bestimmt, wer ein anerkannter Modder ist?

    * Soll jemand, der eine Mod erstellt hat, vorher ein Anerkennungsverfahren durchlaufen?

    * Müssen bestimmte Qualifikationen nachgewiesen werden?


    Ich befürchte, dann wird es kaum noch Nachwuchsmodder geben.



    Quote from dview

    Präfix erstellen

    Ich ergänze sämtliche Mods mit Hinweisen auf bestimmte Kategorien. Die Präfixe sind für mich unwichtig.



    Quote from dview

    Ich verwende es nicht nur für die Mod-Datei selbst, sondern auch für nahezu jeden Ordner oder jede Datei innerhalb des Mods, die ich erstellt habe. So sind meine Mod-Dateien im Debug-Modus und in den Absturzprotokollen sehr leicht zu erkennen.

    Da sehe ich keine Probleme bei der Verwendung.

    Not sure what that list should do?

    Most Modders use the full name for the modfolder prefix, prefixes in other files are rarely used.


    But incase anyone wants to actually compile such a list, generic stuff, like the material for the untensils in my EW IV dining cars get the prefix "hd"

    What would be more helpful (but more arduous to set up) would be to have a Database of Variable Names so that Modders can see what terms have been used already so that we don't have unintentional overwrites from Mods that could release years apart. I have no idea how we would even begin to track this since thousands of Variables can be used in one Mod alone.

    P8_2401_Coeln  HundertDampf


    The main person to acknowledge is the modder. I mean I can create a list from all the mods I downloaded, but besides a lot of work that does not say the modders will stick to the use of the naming I find and I could identify someone incorrect. Of course others should have the decency not to use a prefix already in use by someone else and preferably modders are consistent in using their prefix.

    The benefit of such a list is that A it reduces risk for mod collisions and B will allow users to find who to contact in case of questions or issues. There it is especially useful when the prefix is used also for filenames and sub folders since those are visible in the debug mode and sdtout.


    I think something like this table (feel free to copy and expand):


    Mod prefixModder (Transportfever.net user)Contact viaRemarks
    bko_dviewMessage me on transportfever.net

    Reply in German if you want, but allow me to stick to English.

    I see no advantage of standardizing modder prefixes, specially for normal players. If you want to know who build a mod, you can refer it from the mod.lua. This standard prefixes will not work on teamworks.

    Generally it's good to namespace lua-scripts, parameters and model/texture directories, but in most cases the mod name is enough. (I use 'eisfeuer.mod_name' in the lua script namespace but it's not necessary (except 'mod_name')).


    I'see more advantage to standardize asset categories. Categories like '1111' or 'Siri' doesn't help me a lot and make my asset menu very messy. For example, if I want to place a signal tower I have to know who made it.

    We already have started to make a category list, but it is not up to date.

    Assets: Kategorien

    Quote from N0neGiv3N

    Database of Variable Names so that Modders can see what terms have been used already so that we don't have unintentional overwrites from Mods that could release years apart

    This isn't necessary; if variables are overwritten, it's the modder's from the not working mod, own fault. You have to use variables LOCAL always, then they will only be used within the script (mod). That are basics for scripting for every game not only TPF2.

    So if a mod doesn't work, it's only because that modder, didn't take this into account.

BlueBrixx