[DiscordArchive] Thanks that is a step forward Though am not sure which field to apply the fix for... is it: Target
[DiscordArchive] Thanks that is a step forward Though am not sure which field to apply the fix for... is it: Target
Archived author: Celeby • Posted: 2025-08-17T13:30:31.134000+00:00
Original source
Thanks that is a step forward Though am not sure which field to apply the fix for... is it: TargetARadiusEntry or RangeEntry?
Archived author: Tea • Posted: 2025-08-17T13:33:59.004000+00:00
Original source
RangeEntry
Archived author: Celeby • Posted: 2025-08-17T13:36:05.657000+00:00
Original source
Thanks I will give it a try
Archived author: Celeby • Posted: 2025-08-17T13:43:15.557000+00:00
Original source
That works! I should have asked this sooner still out of curiosity and learning purposes, isn't it better to add some default range that would apply for all spells missing it? Rather than having to add each spell to the applyfix?
Archived author: Tea • Posted: 2025-08-17T13:44:57.598000+00:00
Original source
uh no
Archived author: Tea • Posted: 2025-08-17T13:45:08.697000+00:00
Original source
the thing is that this spell doesnt "not have spellrange entry"
Archived author: Tea • Posted: 2025-08-17T13:45:20.259000+00:00
Original source
it has one thats pointing to a record with 0 range by default
Archived author: Celeby • Posted: 2025-08-17T13:47:31.234000+00:00
Original source
Yes that part i understand so the 0 could be replaced (in the core) with a default value for spells with ImplicitTarget TARGET_DEST_NEARBY_ENTRY. That would in theory fix all similar spells with this issue but maybe I am missing something in how spells work... am no dev