Leaderboard
Popular Content
Showing content with the highest reputation on 03/11/2024 in all areas
-
1 point
Version 1.0.0
113 downloads
Restored Rage Feat By djh269 Date: 22.02.2024 Description: I was looking through k_inc_force.nss and I notice some leftover Force Powers / Feats and decided to restore Zaalbars Rage Feat. Compatibility: Compatible with any mods, if there's any issues please don't hesitate to contact me. Credits: KOTOR Tool – Fred Tetra TSLPatcher – stoffe & Fair Strides -
1 pointView File KOTOR 1 Community Patch The K1 Community Patch (K1CP) is a compilation of previous bugfix mods and a multitude of new original fixes put together with the intention of resolving the many and various issues that KOTOR has. This includes some well-known game breaking bugs/softlocks, broken quests, inaccessible content, as well as lesser issues such as problems in conversations, visual inconsistencies, player annoyances, etc. The intention is for the changes to be as seamless as possible, fixing and improving things whilst still retaining the original developer intent. A huge thanks to all of the mod authors who created these mods, and allowed them to be included in this patch! Unfortunately, the individual list of changes has grown far too long to be included in this post. However, you can view a detailed breakdown of each author's individual contributions in the included readme file and a summary of the changes the current version has made since the previous release in the changelog file. List of Contributing Authors (alphabetical): A Future Pilot blennus danil-ch darthbdaman DarthParametric Ebmar Frykas Gimmick5000 jc2 JCarter426 Kainzorus Prime Kexikus KOTOR 1 Restoration Team Leilukin Markus Ramikin N-DReW25 ndix UR R2-X2 Red Hessian Salk th3w1zard1 Thrak Farelle WildKarrde Installation: Run INSTALL.exe and navigate to your K1 install folder. Generally speaking, this mod should be installed before anything else, except mods that do hard edits/overwrites of 2DA, TLK or MOD (module) files. Warning: Never run the installer from inside the archive! Always extract the archive onto your hard drive first. N.B.: With the advent of version 1.10.0, K1CP has migrated away from the use of TSLPatcher and switched to HoloPatcher. This allows for additional patching functionality and resolves some bugs encountered with TSLPatcher. HoloPatcher is also multi-platform. The bundled installer is the Windows version, but Mac and Linux users can download the appropriate installer for their system here. It is highly recommended that you do not install the game on your system's C drive, especially in Program Files. Windows can have permissions issues when trying to install the mod to a C drive destination. If you are using the Steam version of the game and have installed Steam in its default Program Files location, we advise creating a new Steam Library on a different drive and moving the game there via the game's Properties pop-up in Steam. Translation: The mod now has translations in French and Russian, available as separate patches. To use, first download the base K1CP v1.10.0 archive and extract it to your harddrive. Download your translation patch of choice and extract its contents into K1CP's tslpatchdata folder. Proceed to install the mod as normal. Traduction (Français - Harlockin): Le mod a maintenant des traductions en français et en russe, disponibles sous forme de patchs séparés. Pour l'utiliser, téléchargez d'abord l'archive de base de K1CP v1.10.0 et extrayez-la sur votre disque dur. Téléchargez le patch de traduction de votre choix et extrayez son contenu dans le dossier tslpatchdata de K1CP. Procédez à l'installation du mod comme d'habitude. Переводы (Русский - olegkuz1997): Мод теперь включает в себя переводы на французский и русский языки, доступные в виде отдельных патчей. Для использования сперва скачайте базовый архив K1CP v1.10.0 и распакуйте его на жесткий диск. Скачайте нужный вам патч с переводом и извлеките его содержимое с заменой в папку tslpatchdata K1CP. После чего приступите к установке мода как обычно. Compatibility/Known Issues: K1CP uses module injection in an attempt to remain as compatible as possible with other mods. This may result in issues with mods that simply put files in the Override folder. It is recommended that you consult the individual authors of any large scale mods, particularly those that edit DLGs and scripts, as to whether their work is compatible with K1CP. Some mods will likely require updates, some may need to be installed in a specific order, whilst others may be fundamentally incompatible. K1CP currently only supports the English language version of the game, and makes a number of edits to the TLK file in English. If anyone is able to provide translations of these changes to other languages, please let us know. The KOTOR 1 Restoration (K1R) mod is incompatible with K1CP, however there is ongoing work to re-create the K1R mod for K1CP: https://deadlystream.com/files/file/2345-restored-content-for-k1cp-demo/ These are the currently known bugs/issues with KOTOR or the mod that the K1CP is looking to resolve: https://github.com/KOTORCommunityPatches/K1_Community_Patch/issues If you find any others, especially with changes/additions K1CP makes, please report them on the Github issue page or here on Deadly Stream so they can be addressed. Be sure to include as much information as possible, including a list of all the other mods you have installed, the order you installed them in, steps to reproduce the problem, along with screenshots and save files, if appropriate. You may also be directed to provide the install log file, a list of the contents of your Override folder, and specific MOD files from your modules folder. Uninstallation: Given the complexity of this mod, a clean install of KOTOR is the recommended approach for uninstalling K1CP. However, HoloPatcher does provide uninstall Shell (Bash) and PowerShell scripts which will work as long as K1CP was the most recent mod installed. Permissions: Due to this mod being a compilation from many different authors, please do not distribute/rehost it. Acknowledgements: All of the mod authors who have helped make this patch a reality - thank you! - especially for agreeing to distribution outside of Deadly Stream Fred Tetra - For KOTOR Tool tk102 - For DLGEditor and K-GFF JdNoa/Dashus - For DeNCS stoffe - For TSLPatcher/ChangeEdit/TalkEd bead-v - For MDLEdit and KOTORMax ndix UR - For TGA2TPC, TPCView, and MDLOps v1.0+ seedhartha - For KOTORBlender fork for Blender 2.8+ Cortisol - For Holocron Toolset and HoloPatcher/PyKotor th3w1zard1 - For additional customisation and feature improvement of HoloPatcher Fair Strides - For various tools and updates to older tools DrMcCoy - For Xoreos Tools Snigaroo - For maintaining mod builds at https://kotor.neocities.org/modding/mod_builds/ danil-ch - For the original info.rtf template Many thanks to ebmar, Salk, and KnifeMaster for providing numerous bug reports and beta testing certain fixes THIS MODIFICATION IS PROVIDED AS-IS AND IS NOT SUPPORTED BY BIOWARE/OBSIDIAN ENTERTAINMENT, LUCASARTS, DISNEY OR ANY LICENSEES/SPONSORS OF THE MENTIONED COMPANIES. USE OF THIS MODIFICATION IS AT YOUR OWN RISK AND NEITHER THE ABOVE MENTIONED COMPANIES NOR THE AUTHORS ARE RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR COMPUTER BY THE USAGE OF THIS MODIFICATION. Submitter A Future Pilot Submitted 04/21/2018 Category Mods K1R Compatible No
-
0 pointsI don't know what was in the full original description of your mod, so I'm assuming the permission consisted only of what was written in the post. You're right in saying that 'using the work in a mod' does not mean that 'uploading the work unchanged by itself' is okay, and that the person in question misinterpreted your permissions. But speaking generally about permissions, I think there may be a flaw in your logic, SH. Since there are no universal written rules and explanations about what proper modding etiquette is, different people may understand it differently. For example, my experience with permissions comes mostly from using models from Sketchfab and similar sites. Many models are licensed under a Creative Commons Attribution (CCA). In the Comments section under models, in addition to discussions, advices and screenshots of a model ported into the game, sometimes polite people also ask about permission to use the model in video, games, etc. And I noticed that some authors responded with something like “Yes, that’s why I specifically published the model with a free license. Why are you still asking? Just use it already however you like". And it’s easy to understand why: the authors release dozens of models, hundreds of people download them, even if every 100th asks for obvious things (about permissions when they are written on the page), it will become annoying. At the same time, I've seen some modders (retired and active) respond that they don't care/are not interested in what people do with their old mods as they move on. Some authors ask to inform them about the use of their work in other mods because they are interested, but others do not specify anything at all and I wonder if they will be bothered if I write to them about some years-old model? Since then, I've taken a stance: if the modder has allowed everyone to use the mod/model, then be grateful, respect the author and their time, and don't bother them unless you have something to say/to show. In my opinion, it would be better to thank the modder and show them how their work helped create a great new mod, than to ask for permissions (which are already given in the Readme), waste the person's time, create expectations and then fail to produce anything. Modders in the KOTOR community usually don't publish mods under licenses, but the terms 'You can use/modify the mod, just credit the author' written on the mod page or in the Readme file can be considered the equivalent of CCA license. It does not impose any obligations other than “attribution.” If the mod author does not specify additional requirements/wishes, then the user (especially if he is not an active member of the community) may not be able to know their preferences and will have to rely on his own inner judgment. Whether he contact the mod author before or after the release, or not at all, depends on the user. To avoid misunderstandings about 'permissions', modders should write their requirements as clearly as possible, so that there is no potential ambiguity, and expect users to do only what is written in the permissions.
-
0 points
-
0 points
-
0 points