You are here

Community Patch future?

6 posts / 0 new
Last post
Shadooow
Community Patch future?

Hi. I was away from nwn for a looong time. Main reasons were lack of feedback on this project, negative campaign on this project and mainly NWN:EE. Now, I would like to continue working on NWN again but don't know how.

NWN:EE changed everything. While I helped Beamdog with that and I knew it is coming, NWN:EE raised many issues with custom content and nwnx specifically.

I made probably the bad choice of linking nwnx_patch + nwncx_patch plugins with community patch itself. Perhaps it was bad design, but on the other hand, there are many fixes that couldn't be done otherwise, those two projects needs to work together. But NWN:EE will not support nwncx anymore and it doesn't support windows which is a platform I work and develop for*at. This means that community patch for NWN:EE (and the version for EE already exists) will not use any of the nwnx features/fixes.

Fixes are fine, afterall around 80% of the hardcoded bugs fixed in nwnx_patch is already fixed in NWN:EE which is great. Also some of the features like hak preloading are present in NWN:EE but there were more of it and those who used it on 1.69 and relied on it will have problems to move on NWN:EE. As did I.

I still don't know whether I should maintain two versions of community patch one for 1.69 with nwnx and one for NWN:EE without. Whether I should continue improving nwnx_patch for 1.69 or just scrap it all and change community patch in way it works exactly the same on 1.69 and NWN:EE, remove all nwnx dependancies etc.

Any thoughts?

  • up
    100%
  • down
    0%
Surazal

Hi Shadooow, welcome back - good to hear from you again.

IMHO, it may be worth separating the fixes that are nwnx-dependent, so that you have a single non-nwnx CPP for both 1.69 and EE. It would also be worth having a set of nwnx-dependent fixes as a separate download. This approach ensures parity with EE as well as offering 1.69 users the benefit of the nwnx-dependent fixes.

As ever, your contribition and efforts are very much valued and appreciated.

  • up
    50%
  • down
    50%
shadguy

If I were you, I'd shift away from fixing things and shift towards reporting open issues to BeamDog.  Let them fix stuff for everyone with the benefit of your knowledge.

-Dave

  • up
    50%
  • down
    50%
Shadooow

Done and done, I think that everything I fixed in nwnx_patch and also some of the issues I didn't manage to fix myself are reported on private, pre-public bugtracker of BeamDog. Some issues were already fixed, some are in the progress, some were marked as known bug and won't be fixed.

This includes the engine bugs. As for content fixes, BeamDog doesn't seems to have time to deal with them - obviously they cannot just inherit the package of multiple fixes and must investigate every single fix one by one, which is not possible right now when they are on tight schedule. It is even more complicated with fixes to scripts like spells.

As for new bugs, I am not much a player anymore so I can't report much.

  • up
    50%
  • down
    50%
shadguy

Well, if you want to continue the community patch, maybe strip it down to the content fixes that "BeamDog doesn't have time for."   Alternatively, go play with the new stuff and call it a day for nwn ccp. 

You've given us a lot over the years, and I don't (personally) see a ton of value back for your time in continuing to maintain 1.69 versions of stuff - not long term, anyway.

If it was up to you, what would you like to do?

-Dave

  • up
    50%
  • down
    50%
Shadooow

Oh I want closure, question is how to do it properly.

  • up
    50%
  • down
    50%