Sam., on 31 Jul 2020 - 12:16, said:
Congratulations on the beta release and thank you for your hard work! A couple initial thoughts:
- The download link in the readme points to an outdated version.
- The GitHub link in the readme returns a 404 error (destination does not exist).
- The readme claims "This mod is designed to work on all classical Infinity Engine games" but then fails to list BG1/ToSC (and PS:T).
- Have you considered including the HQ Music for an all-in-one 1pp package?
- I understand the desire to move away from READLN, but for the component options that are binary (not install | install), doesn't it make much more sense to make them directly installable components (or more likely subcomponents) rather than burying them in an INI file?
- Why does the Attachable Wings component require 101 to be installed? It shouldn't (or didn't use to) have any dependencies whatsoever.
- Also, please do include the male variant of the wings.
- Readme links: As I did not want players to install this beta version before official release, I did not transfer it from my GitHub account to SHS one. As a result, the DL links point either to SHS DL Center (previous version not yet updated) or to SHS 1pp repository which does not exist for the moment. Sorry for the inconvenient, but this will be solved once the mod will be officialy released.
- Good catch: I forgot to replace "all classical IE games" with "most"

Once again, it seems we have the same ideas: I have considered regrouping HQ music packs in the same package, as we have gathered all the IA archives (the test version of which will be published in the course of next week
). But at first, I preferred to solve the 1pp problem. Once this version is validated, I can easily include the music packs in the same package.
Attachable Wings: I agree with both your proposals. So I can cross that line off the todo list.
Considering the configuration options, the problem is that most of them are used by the 400 component which depends on which core components have been installed. I've done some testing to replace the READLNs actions with sub-components. Unfortunately, this resulted in a plethora of new components that would have made the installation much more complex. I have a project under way to group the components by group: installing the core data (component series 200 to 209), patching objects and spells, that might simplify the process. I know that changing options in an external ini file may seem complicated for some players, but it's the only easy way to simplify the installation which becomes transparent to the player once he.she has read the readme.
Cahir, on 31 Jul 2020 - 12:53, said:
Noob question, can it be installed on EE? If yes, will EE game benefit from this mod at all? I realize that the content of IPP is included in EE's, but maybe not all the content? Maybe there are some parts of the mod that could be used for EE's?
This is a point listed in the todo list. However, at this point, this will cause more problems than it might solve. I had in mind to release a "1pp fixpack" mod for EE games that would patch EE games items and spells with classical 1pp content not yet included. That could be done once this version is validated.
skellytz, on 31 Jul 2020 - 18:44, said:
Thank you!
So, just a quick test and sadly it seems like the colors from the extended palette are still treated as random (ie will change every load). Have you attempted to fix this issue?
Unfortunately, after reading all posts dealing with this subject, I came to the conclusion that there were no way to fix it, at least beyond my abilities. And that the readme warning is still available:
Quote
Interesting side note: If a colour that has an entry in RANDCOLR.2da is set as an entry of a random colour itself, it will show up as the intended colour value.
However, if someone has figured out a solution, I would of course be glad to include it. 
Edited by Gwendolyne, 31 July 2020 - 12:44 PM.