PDA

View Full Version : Reverse drag and drop not working



Iceman
June 5th, 2024, 14:55
I resolved this the old fashioned way and recreated the encounter. But it was still puzzling and Im wondering if there was an easier way.

A month or more ago (about 1000 updates ago) I created an encounter and dropped it into the combat tracker. Its been sitting there as I slowly drag and drop from the CT to a very large map.
So today I wanted a quick look at the CR for all of them currently on the CT so I went to drag and drop from the CT into a NEW encounter I just created, which was ofc blank to start with.

'Only records from campaign record lists can be added to encounters.'

That is the message I repeatedly received on any NPC being dragged from the CT to the new Encounter, regardless of whether I did it just from the shield on the CT or if I opened the NPC first and then dragged it. So I had to search for each and every NPC which was easily and quickly available in my NPC list and dragged it into the new encounter block and got my CR.

But Im still confused as to why this happened in the first place, though I would have to guess that something became incompatible over the last thousand updates or so.
Any insights appreciated.

Trenloe
June 5th, 2024, 15:01
But Im still confused as to why this happened in the first place, though I would have to guess that something became incompatible over the last thousand updates or so.
Nothing to do with updates. This is built-in checks in the code to make sure that base data records are used in encounters. Records in the combat tracker (CT) are self-contained within the combat tracker - that is, when a creature is added to the CT a copy is made of the complete creature record for each entry in the CT. NPC/Creature records in the CT are normally there for a short time and go through changes (usually HP wounds and effects, but could be more changes).

NPC entries in an encounter are links to the dragged record. The code only allows base records - not records from the CT, as using CT records will quickly invalidate encounter data as they probably won't exist when you come to use them, and if they do (i.e. the records are still in the CT) it'll create duplicates in the CT.

So, it's good coding to prevent issues in the future. Of course, it doesn't help you trying to use an encounter to quickly calculate the CR, but that's really a small functionality of the encounter and using CT records for that is not part of the design nor, as you find, possible.

Trenloe
June 5th, 2024, 15:09
I created an encounter and dropped it into the combat tracker. Its been sitting there as I slowly drag and drop from the CT to a very large map.
So today I wanted a quick look at the CR for all of them currently on the CT so I went to drag and drop from the CT into a NEW encounter I just created, which was ofc blank to start with.
Your best approach would have been to make a copy of the original encounter record and edit the creature count to reflect what was in the CT, then adding in any base records as needed.