Jump to content

lynx

Modders
  • Posts

    3,900
  • Joined

  • Last visited

Everything posted by lynx

  1. I understood it as an extra way to reduce the confusion between the two. And really, as a fork, the team behind it can point it to wherever they want.
  2. Talk to the author then. It's likely the mos is malformed. You didn't actually ask for a smaller resolution, right?
  3. Find out which mod installed T-1002.mos first.
  4. Come on, leave your bile at the door mysterious veteran. Let's not have a repeat of the needless downward spiral that was the closed SHS thread.
  5. Calm down everyone. The code and data of both projects is still open and public, so anyone can make direct change suggestions there.
  6. Do you have _ApplyPatches.bat anywhere in the game dir? It's from BWPFixpack and is used to do what its name says.
  7. Yes, if the download link points to my modhub, it will pick up version changes automatically. That's enough for simple version bumps, but when new togglable stuff is added like with the updated BGQE, more work is needed to present that to the user.
  8. this is the full list for bg2: https://gibberlings3.github.io/iesdp/files/ids/bg2/sndslot.htm for the filename, just use a consistent prefix, since you're not creating it for a npc. I think subtitles for this kind of thing depend on the feedback settings in options.
  9. IWD patch 2.5 is still IWD1, not IWD2 and with all the bg/iwd1 ee games on the same engine (I think they're now in sync), there's no engine barrier for a integrating iwd1 into bg or vice-versa.
  10. Looking at older threads, maybe it's just too soon in game time.
  11. Of course. Here's another distinction. Jagged Alliance 2 had its source released and the engine got a bunch of cleanup and some bugfixes from the community. Due to the latter it can't be called vanilla, so it's called stracciatella, the fixes being the small chunks of chocolate in the vanilla.
  12. Argent updated the iesdp entry, so I've moved this to the archive.
  13. I agree with Argent77; it's the same interpretation used in other gaming communities.
  14. Well so what are those changes? I imagine you were able to remove some code by dropping support, but that's a trivial guess.
  15. So what are the main maintainability changes? Seems odd that it's a fork and no obvious conflicting changes at a glance.
  16. Thank Gond for scripting. The lists are now updated.
  17. Ok, both things should work now. ChangeWeather has the same id and SetStat is supported (though tobex made it very limited). Couldn't grep any uses in SCS though, so
  18. Yeah, I'll just fix that one spell it was created for and assign it a higher number — it predates ee. It's the only conflicting id on the tobex list too.
  19. First, you're not comparing the same thing. Tobex doesn't do anything to this opcode, since it wasn't present in the engine before ee. It has a different opcode at that address (Stat: Set stat), the new one is at 0x140. Installing tobex doesn't affect gemrb, but this is about the numbering collision, since the ids files are in conflict. And then missing functions — I think the new setstat is just for the extra mode that ensures ordering. That log line is perfectly fine.
  20. Great job everyone, especially Roxanne for shepherding everything!
  21. As soon as people start relying on it, the bug morphs into a feature. :/
  22. thanks, added note. Quite bizarre behaviour.
×
×
  • Create New...