Category: News ArchiveHits: 1802
In their first livestream of 2018, Beamdog's Trent Oster and Phil Daigle talked about the continued development of Neverwinter Nights: Enhanced Edition, answered a number of community questions, talked a bit about the 2.5 patch for the Infinity Engine Enhanced Editions, and hinted at some announcements that should come our way in 2018. Check it out:
As usual, if you don't want to watch an hour long video, you can check out a recap on the Beamblog.
Additionally, a new patch is now available for the Neverwinter Nights: Enhanced Edition Head Start. It fixes a number of issues, adds a couple of features, and makes a number of new scripting commands that help with minimap management available to the players. Here's an excerpt from the patch notes:
- Servers will not crash anymore when applying damage to a caster will trigger a Concentration check, but the originating player has left the server.
- Servers will not read invalid memory anymore in OnApplyTrueSeeing if no blindness effects were present.
- Servers will now update internal effect pointer housekeeping properly on Effect Removal. This fixes a rare case where a movement speed penalty would not go away after removing an ability penalty (and maybe others too).
- A dozen memory leaks have been addressed.
- Server will not crash anymore when you queue up a player character export and then the player leaves before the export runs.
- Area instancing: Player- and DM-clients are now kept in sync properly about new/deleted areas (no more empty names).
- Area instancing: Server will not crash anymore when areas are added/removed and internal exploration bitmap array goes out of sync.
- Familiar/DM-possession: Server will not write to bordering memory anymore on unpossess when areas are added/removed and the player is in someone else’s body.
- Area instancing: CopyArea should now copy all objects into the new area properly
- Area instancing: CopyArea will not create duplicate object IDs, sowing confusion.
- Direct Connect UI Panel: We broke it in 8153, and now we fixed it again.
- [VM] SetDescription(..): Limit bumped to 128KB. (Was: 8KB). Although we increased the size limit, we recommend keeping this as small as possible as this is sent to clients on each view.
- [C++/Low-Level]: NWNXEntryPoint for Windows and macOS has been exported, paving the way to support it on those platforms. GetBuildNumber has been exported too, which will allow nwnx to fail gracefully on version mismatch, instead of catching fire.