Skip to content

Cleanup, quickcasting (UG), overcast table, lores dropdown#2608

Open
silentmark wants to merge 2 commits into
moo-man:masterfrom
silentmark:misc
Open

Cleanup, quickcasting (UG), overcast table, lores dropdown#2608
silentmark wants to merge 2 commits into
moo-man:masterfrom
silentmark:misc

Conversation

@silentmark
Copy link
Copy Markdown
Contributor

  1. Removed unused imports from files,
  2. re-added quickcast from UG
  3. change in the way how lores for spell are being presented in sheet,
  4. fix for overcastpertable and re-added option to the spell sheet.
  5. minor null-check that sometimes happened for me.

computeTemplates()
{
let templates = this.parent.itemTypes.template
if (!templates || templates.length == 0) return;
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the point of this?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

had few errors in the past so i have added this check.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well that doesn't make much sense, there's no reason that'd be undefined.

<div class="form-fields">
<input type="text" list="lores" data-action="editLore" value="{{loreValue}}">
<select name="system.lore.value">
{{selectOptions lores selected=source.system.lore.value}}
Copy link
Copy Markdown
Owner

@moo-man moo-man Sep 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like a step backwards, what is the reason? Not using select has been intentional since the creation of the system.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, didnt know that it was desired. I had some problems with translations - initially it is stored as "key" but after edit - it becomes a simple string, which is causing problems in few scripts or even here:

else if (spell.system.lore.value == "witchcraft")

the situation was that i had some spells that were not translated, i wanted to manually change their lore and then - some stuff stopped working.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is a problematic area that's always been difficult. The system should be checking to see if the input entered matches an existing lore key, if so, store the lore key, otherwise, store the input.

Comment on lines +81 to +84
<div class="form-group">
<label>{{localize "SHEET.OtherCost"}}</label>
<input type="text" name="system.overcast.valuePerOvercast.cost" placeholder="{{localize "SHEET.OtherCostPlaceholder"}}" value="{{system.valuePerOvercast.cost}}" />
</div>
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this WOM specific? I don't see anything hiding this option if that's not being used.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

right, it is WoM specific, i will add the flag to check the config and display only when relevant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants