Jump to content

AL|EN

Modders
  • Posts

    1,321
  • Joined

  • Last visited

Everything posted by AL|EN

  1. Or by exporting the install sequence, manually modifying it, deselecting all mods, importing the manually adjusted install sequence, and preform installation.
  2. If you want to avoid such trivial mistakes with wrong tp2 version, you can locally use Mod Release tool: ModRelease - create new GitHub Release from commandline — Beamdog Forums The initial setup is a bit chore, but after it, no more trivial mistakes during releasing new mod version. Yes, PI need new release (not only ta) if you want to 'release' new version into the wild. Please read Delta Updates for mods hosted at Github · ALIENQuake/ProjectInfinity Wiki ,
  3. The new version of the Ascension mod was released. It brings English proofreading of whitespace, punctuation and such, major update to French translation, minor updates for all other translations, fixes for 3 missing translation lines, compatibility with Stratagems "Start TOB with Watcherkeep" component, and some other minor changes and fixes. One important thing that I want to mention is that the ability to translate this mod using tra files is restored, while also keeping the translation system: Infinity Engine/Ascension @ BGforge Hive. Now you can choose which method you want to use. In other words, for those who want to use .tra files, everything returns to how it was for the past 20 years, and for those who prefer the translation system, nothing changes. Download the mod View the readme Learn more about the mod Forums Ascension 2.0.24 The ability to translate this mod using tra files is restored Added compatibility with Stratagems component "Start TOB with Watcherkeep" Fixed creation of imoslay2.spl on classic BG2 Fixed not existing spell name SPIN822b.BAM to SPIN822.BAM Fix for msg2po regex not supporting double quotes English proofread of whitespace, punctuation and such by Jazira Major update of French translation by Jazira, Selphira and Machiavelique Minor update of Russian translation by abalabokhin Minor update of Czech, Chinese, German, Italian, Polish, Portuguese, Swedish and Spanish translation
  4. Ascension 2.0.24 The new version of the Ascension mod was released. It brings English proofreading of whitespace, punctuation and such, major update to French translation, minor updates for all other translations, fixes for 3 missing translation lines, compatibility with Stratagems "Start TOB with Watcherkeep" component, and some other minor changes and fixes. One important thing that I want to mention is that the ability to translate this mod using tra files is restored, while also keeping the translation system: Infinity Engine/Ascension @ BGforge Hive. Now you can choose which method you want to use. In other words, for those who want to use .tra files, everything returns to how it was for the past 20 years, and for those who prefer the translation system, nothing changes. Full changelog: The ability to translate this mod using tra files is restored Added compatibility with Stratagems component "Start TOB with Watcherkeep" Fixed creation of imoslay2.spl on classic BG2 Fixed not existing spell name SPIN822b.BAM to SPIN822.BAM Fix for msg2po regex not supporting double quotes English proofread of whitespace, punctuation and such by Jazira Major update of French translation by Jazira, Selphira and Machiavelique Minor update of Russian translation by abalabokhin Minor update of Czech, Chinese, German, Italian, Polish, Portuguese, Swedish and Spanish translation Translation changes: Ascension-German.htmlAscension-Czech.htmlAscension-French.htmlAscension-Polish.htmlAscension-Russian.htmlAscension-Chinese Traditional.htmlAscension-Italian.htmlAscension-Portuguese.htmlAscension-Spanish.htmlAscension-Chinese.htmlAscension-English.html
  5. Ascension 2.0.23 cosmetic correction of readme file updated Czech translation
  6. Ascension 2.0.22 updated Czech translation
  7. DLCMerger is the newest version of Modmerge, it's just standard WeiDU mod. It comes without annoying bug where restoring game from backup would still mark it as 'modmerged'.
  8. Congrats on release! I found minor issue: the %MOD_FOLDER% must be replaced here with 'akgear' until this bug will be fixed: https://forums.pocketplane.net/index.php?topic=29521.msg340868#msg340868 LANGUAGE ~English~ // Language ~English~ // Directory ~%MOD_FOLDER%/English/!_setup.tra~ ~%MOD_FOLDER%/English/!_watodu.tra~ ~%MOD_FOLDER%/English/!_laofco.tra~ ~%MOD_FOLDER%/English/!_powcrv.tra~ LANGUAGE ~Deutsch~ // Language ~German~ // Directory ~%MOD_FOLDER%/German/!_setup.tra~ ~%MOD_FOLDER%/German/!_watodu.tra~ ~%MOD_FOLDER%/German/!_laofco.tra~ ~%MOD_FOLDER%/German/!_powcrv.tra~
  9. IAP was updated to remove requirements of changing setting for "Workflow permission" since too many people face this issue because of GitHub defaults. No actions are required from modders as long as the latest version of IAP will be used when creating new repositories.
  10. I found nice tool to help detection of changes inside mod folder during installation: FolderChangesView https://www.nirsoft.net/utils/folder_changes_view.html Usage should be explanatory, just add folder to watch and start mod installation with every component.
  11. In general, text files are fine. The allow for even more automation and less unnecessary actions from the users. From what i have seen, advanced users prepare initial version of install sequence using PI and then modify/update it later. Since yaml is most difficult configuration file format for average Joe, you could create simple GUI to prepare yaml files and then launching 'modda' to preform final installation. There is definitely, an audience for such workflow.
  12. Is that mean that even if PI would exist for Linux, you would still prefer command line?
  13. IAP was updated to remove warnings about deprecated 'node 12' and 'set-output' command . No action are required from modders. EDIT: When creating a new repository, you might want to check 'Workflow rights' from the first post. No longer needed.
  14. @TotoR Yes, Git is case-sensitive because it was created to maintain Linux and it's also case-sensitive. Use this one liner: git config --global core.ignorecase true IMHO, it should be standard if you are working with Git/GitHub on Windows.
  15. @ChristianWhich version of WoP did you install?
  16. @Nathan82 Hey, if you still have installation on you drive, can you do weidu changelog of ar6200.bcs file?
  17. @mike123 Do you mean the language order after clean game reinstall and using Ascension as first mod: The first choice is from the mod itself, the second one directly from WeiDU. Yes, it's possible to match the order but it was like that since 15+ years so doing it would probably cause problems for other people who are used to have English as 0. The workaround 1: remove "lang\de_DE" folder from you game. Keep in mind that it will be back when restoring game from backup/verifying game files. The workaround 2: make copy of weidu.conf file and after each clean installation copy it over before installing first mod The workaround 3: create Ascension.bat file and use --force-install-list along with --language 0 --use-lang 'en_US' command line options The workaround 4: use mod manager, you won't ever have to select language again
  18. @Aryene From where you downloaded this mod? I have no idea how you manage to extract the mod archive and get single quote character at the beginning of the folder name. Download the mod from this post: https://forums.beamdog.com/discussion/comment/1103544/#Comment_1103544 and: extract it open karatur\setup-karatur.tp2 replace BACKUP ~\KaraTur\Kbackup~ with BACKUP ~KaraTur\backup~ 4. Save file. Now mod should be detected by PI.
  19. @Aryene What's the "literal" name of the mod folder?
  20. @Ironicus For you specific problem: Ascension mod is processing necessary additions of ToBEx but it fails because you have "bgmain.exe" from non supported 'BG2 gold' edition of the game. So reinstall the game and make full backup of it. Since you have 'gold edition', try to apply this patch as first step: http://www.shsforums.net/files/file/1086-saga-baldurs-gate-conversion/ - this will attempt to make "bgmain.exe" into supported version. If this step success, you should be fine to continue to install BG2Fixpack and Ascension and then rest of the mods. Try it and report back. The bad news: You can't 'reinstall' the game and expect that the save will work unless you installed everything in the same order. Do you have backup of the old installation? So you can read weidu.log and see what order of mods did you use?
  21. While such situation is certainly possible, the key point here is that we have active modder who understand dependences for both mods, so he made the change. I'm sure that there will be a away for him to update the other mod to account for changes either directly by mod author or hosting site maintainer. If not, manual install or ini edit will do the job. Direct (as opposite to simply showing one install order rule at the time) detection of "circular dependency" by mod manager is possible but given that it only occurred once, it has low priority.
  22. As Graion Dilach said, nothing more to add. @subtledoctor For WtP and F&P, best thing to do for this particular case is to create pre-release version of WtP, which will take into account changes in pre-release F&P as they eventually become final.
  23. Disable AdBlock, AdGuard and similar addons, use Edge (Chrominium based) or Chrome, use private mode etc
  24. @UmeChaI'm on Windows 11 and can't reproduce. Can you do clean installation of Win11 x64 inside Virtual Machine and test SCS there?
  25. @subtledoctor The reason why Quester was able to install component 1203 despite using BG2EE engine and EET is because PI is using is using "--force-install DESIGNATED" and at the same time, PI is unable to parse tp2 file and extract any logic conditions due to complexity of such task. Even the "parsing" part require significant amount of work (GLR parser) so it's not something that I can do in nearest future. Maybe someday there will be tp3 that could solve such problems.
×
×
  • Create New...