Jump to content

AL|EN

Modders
  • Content Count

    685
  • Joined

  • Last visited

About AL|EN

  • Birthday 03/22/1982

Profile Information

  • Gender
    Male
  • Location
    Poland

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. AL|EN

    Mod Compatibility List for EET

    @K4thos So how about replacing html by markdown? Even less work.
  2. @cmorgan When using LABEL for ID context, translating will deny it's purpose. You would not want to have language-dependent tp2 filename inside weidu.log, right?
  3. AL|EN

    Progress Reports

    You welcome! The pleasure is on my side
  4. It goes even futher: all mod components can have one major label (eg. "MyMod") and and also extra unique label ( eg. "MyModDragonQuest", " "MyModIslandQuest") so it's possible to check for ANY component of the MyMod.tp2 and aslo for specific component separately. Just to be clear: the LABEL keyword name is not adequate to the context of the usage. I only used it because weidu doesn't have anything else. If there would be an eg. "ID" keyword with documentation, the context of the usage would be much more clear.
  5. @jastey I was thinking about code example but anyway: 1. You are talking about cross-mod requirements (not cross-mod conflicts between two or more mods/components which can be handled differently), when the one mod is looking especially for specific external mod component, right? List of things: - bg1npc v24 component 10 (former 1) : The BG1 NPC Project: Banters, Quests, and Interjections - Jarl's Adventure Pack Main Component (auto-assigned number of 1) : the main component - cross-mod requirements which are defined by such code: (you don'r really need to use folder name and .tp2) ACTION_IF (MOD_IS_INSTALLED ~BG1NPC/BG1NPC.TP2~ "1") BEGIN Problem: bg1npc v24 changed DESIGNATED number from 1 to 10(for valid reasons) so now JAP needs update. Unfortunately, you are depended on other modder support. But there is a way for bg1npc to help you in a way which won't force modder to keep DESIGNATED numbers the same for eternity. But let's start from the beginning: - let's use weidu %TP2_BASE_NAME% as ID, it's the tp2 file name without intention and without 'setup-' - the BG1NPC mod is inside BG1NPC/BG1NPC.tp2 file, it has ID of 'BG1NPC' ... that doesn't solve anything So ... let's assume for a second (not an actual suggestion for bg1npc) , that the "The BG1 NPC Project: Banters, Quests, and Interjections" component would exist as ... separate tp2 file: - it would probably have a filename of: BG1NPCBantersQuestsInterjections.tp2 and 'BG1NPCBantersQuestsInterjections' as ID But since I'm not suggesting that bg1npc mod should be spited into many tp2 files, what we can use to have ID for mod component? Weidu doesn't have support for such thing but it has ... LABEL: 1. The "BG1 NPC Project: Banters, Quests, and Interjections" component needs to receive LABEL keyword with "BG1NPCBantersQuestsInterjections" https://github.com/Gibberlings3/BG1NPC/blob/eev2.5/bg1npc/bg1npc.tp2#L65 There is no technical reason to change such label and one component can have multiple labels if needed. 2. Instead of checking hardcoded component number (MOD_IS_INSTALLED ~BG1NPC/BG1NPC.TP2~ "1") check for component number of the LABEL: (the syntax is not great but it is what current weidu require) ACTION_IF (MOD_IS_INSTALLED "BG1NPC" (ID_OF_LABEL "BG1NPC" "BG1NPCBantersQuestsInterjections")) BEGIN So no matter what BG1NPC DESIGNATED number will use for this component, as long as it won't change label, you and all other mods are safe It still require cooperation between two modders but the main benefit is: it doesn't limit the author of the BG1NPC in terms of how he can structure internal mod components. I'm aware that all of this require change the concept of how modders see mod components but for me, mod components were always ... well, mods! I use LABEL keyword only because weidu doesn't have any kind of support for component ID out of the box. But if there are valid user cases... History shows that it won't work because there are technical reasons to change DESIGNATED (install sequence, GROUP etc). My suggestion would be to ask for label-based solution or implementation of the "component ID" support for weidu in any kind of form.
  6. Valid point, please give me example so I can see the context and show you how to solve this issue
  7. No, because there is no established alternative, and even if there were, it would not deprecate READLN because there would still be valid use cases. @Wisp To what extent you are fine with updating description of ACTION_READLN? How about: ACTION_READLN variable Do not use this action without a real reason. There are no valid cases for it which cannot be replaced by SUBCOMPONET or user configuration file. Waits for the user to provided an enter-terminated string and store it in variable. Said string will be stored and re-used during non-interactive reinstalls. and additionally, replacing READLN tutorial section with SUBCOMPOENT/user config tutorial for the examples covered?
  8. If you happen to have Winddows XP 64-bit ...
  9. To give you even more motivation for removal of the ACTION_READLN: many modders are using you mods as an examples in order to start with IE modding. So such contributions have extra value: not only makes mod better but also teach others how to have best code for staring point
  10. I've never played Breagar so I can't comment on NPC itself but it's real pleasure to see ACTION_READLN removal! Thanks!
  11. AL|EN

    Site and Forum Feedback

    "Mark site as read" redirect to the main site instead of the forums.
  12. AL|EN

    Tweaks Anthology v8 Now Available

    Yes, Project Infinity can do this, you have to set folder for extracted mods, set language to English and import weidu.log
  13. AL|EN

    Mod Compatibility List for EET

    @K4thosYou can switch to https://htmlpreview.github.io
  14. AL|EN

    EE/EET Mod Setup Tool

    @Kaliesto What i mean is: you can install EET using PI right now but it requires extra steps: converting BWS/BWP install order, separate installation of mods for BG1EE-part.
×