Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confirm delete #179

Merged
merged 7 commits into from
Feb 14, 2022
Merged

Confirm delete #179

merged 7 commits into from
Feb 14, 2022

Conversation

draconas1
Copy link
Collaborator

@draconas1 draconas1 commented Feb 12, 2022

Me implementing this now has nothing whatsoever to do with me entering all my players powers and accidently slipping the mouse from "edit" to "delete"

Configurable, On by default.

EndlesNights and others added 7 commits February 12, 2022 13:33
Steve has gained an implement and an AoE fire power that uses the implement.

An example ritual and an example NPC (Badgers are not in 4E as creatures, so do not have to worry about OGL issues) (Ritual costs are tricky to grab as the attribute dropdown gets cleared as soon as it's off a character)

Feat that adds to fire attack and damage powers (to show on steves new fire power).

Updated fighter weapon talents to have an effect to boost that attack. This can be done automatically for 2 Handed Weapons, alas 1 handed weapons need a custom variable, but at least we get a custom variable demo!
When adding equipment to token action HUD integration I was reminded that in order to get it working I had to poke some quite internal and knarly methods in 4E.

Basically things that we would change, that would then break token hud, and we would have no idea why.

So I refactored them all into the hooks.js object, which gives Token HUD a single place for when it needs to call any method on one of our objects.  Especially as a lot of them the logic is actually in the sheet.  This means they will at least show up in a usages search in VSCode/Webstorm etc... so we know if we change them to also update the calling method.

Method signatures were made to be as standardised as possible with all relevant information, so hopefully if we ever change an implementation there is no need to change api.
Me implementing this now has nothing whatsoever to do with me entering all my players powers and accidently slipping the mouse from "edit" to "delete"
@EndlesNights
Copy link
Owner

I kept meaning to do this, but I think I just never got around to it because I have yet to accidently delete anything! Lucky me, but bad on me for not implementing it sooner to save others.

@EndlesNights EndlesNights merged commit 3def8c6 into EndlesNights:dev Feb 14, 2022
@draconas1
Copy link
Collaborator Author

draconas1 commented Feb 14, 2022 via email

@draconas1 draconas1 deleted the confirm-delete branch February 18, 2022 17:49
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