2017-04-30 Meeting Summary

2 posts / 0 new
Last post
Atrayonis's picture
Atrayonis
Developer EmeritusInterior DeveloperQuest Developer
Joined:
2015-09-28 20:13
Last seen:
1 year 11 months ago

Carried over Agenda

  • Further Discussion of House Redoran (Faction page overhaul)
  • Interior merges
  • Foul Murder
  • Ranks and Hierarchy
  • Nav Andaram
  • Tribunal Temple and its environs
  • Ascadian Bluffs (Region Template)
  • More Almalexia/Alt Orethan
  • Update various documents on the site
  • Finish reviews of various assets and get them into Tamriel Data (Add-on), and mark these as such in the Assets Browser.

 

Meeting Summary

Section Files

Section files and their relation to Indev and Mainland were discussed. In general, consensus is that, file wrangling aside, more section files are better since they enable cleaner dialogue editing and less hassle with merging interiors and local quests.

To start out, three new section files will be created:

  1. Hlaalu-Thirr, as per the map Gnomey made
  2. Roryn Bluffs, including both the other Roth-Roryn and Ascadian Bluffs cells (excluding vanilla cells)
  3. Lake Andaram, which is bleeding into Thirr Valley and the Deshaan Plains.

Menaan and NPCing

NPCers are quest developers. There will not be an additional role for them. NPC design will initially be handled via the asset browser; exterior and interior developers working on a location and anyone else who has ideas can submit them to the relevant entry. When the time comes for implementation, quest developers should check the entry to see what they need to implement as well as any suggestions they might want to implement.

Actual implementation would be carried out in a claim (with dialogue work being preestablished while the claim is still in design), containing both a copy of the release (section) file of the settlement as well as the actual esp the quest developer creates.Options for work separate from the release file are:

  1. quest devs work with temporary cell names, don't initially put ownerships or world edits, and give merge instructions for what cells should be named after merging their file. Ownership and world edits would be applied afterwards directly to the release file, ideally by the quest developer.
  2. quest devs rename cells in their own copy of the release file before doing any other work, don't initially put ownerships or world edits, and give merge instructions for what cells should be named before merging their file. Ownership and world edits would be applied afterwards directly to the release file, ideally by the quest developer.
  3. quest devs rename cells in their plugin, claim all interiors in their section for ownerships or world edits, and give instructions for all those interiors to be deleted from the release file before merging their file.

Menaan as a testbed for top-down development, before was planned with an NPC layout in mind http://tamriel-rebuilt.org/comment/1374#comment-1374 and the Quester who gets to implement these NPCs is encouraged to follow these documents. With only one more interior claim needing to be reviewed, special attention should be paid that the NPC implementation can serve as guideline for future settlements.
There is obviously room for deviation - important NPCs (marked as such) are planned top-down, but the misc NPCs can be played around with by the implementer. It’s also (still) allowed for the NPCer to plop in mini-quests if they so desire. As always, documentation and discussion is the key issue here! NPCers should ask questions if they are unsure.

Further workflow:

Interior developers can add creatures and are encouraged to add pathgrids. Exterior developers are discouraged from adding creatures but should add pathgrids where they are necessary (bridges and other hard to navigate areas). Neither should add NPCs.

Parker's picture
Parker
Developer EmeritusInterior DeveloperQuest Developer
Joined:
2016-01-19 04:30
Last seen:
2 years 8 months ago

All sounds good to me. Glad to see us moving forward with new NPC work.