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

Tables don't work/save #46

Open
Raybro29 opened this issue May 23, 2024 · 0 comments
Open

Tables don't work/save #46

Raybro29 opened this issue May 23, 2024 · 0 comments

Comments

@Raybro29
Copy link

Raybro29 commented May 23, 2024

Describe the bug
Making a custom LCP for someone else's homeforge. Went to make quirks (about 20, dunno if that's important to point out) for flash clones and exported the file. loaded up to COMP/CON to test it, but none of the custom quirks were there. Went back to the editor, loaded up my LCP and open up the Table section. None of my quirks were there. I made a JSON file to keep my progress with it, but yeah. I have yet to test out the other options for the tables (pilot names, callsigns, and mech names) but I assume that they're also affected.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Tables tab
  2. Make new table entries (quirks, mech names, etc)
  3. Export file
  4. Load file
  5. Return to Tables tab

Expected behavior
I expected this to insert my new quirks/whatever into the randomizer table for quirks/whatever on COMP/CON

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Firefox
  • Version: idk how to check, the latest I guess

Additional context
I imagine that this issue is due to the LCP editor being experimental still. I don't know if it's still being updated (I hope it is cuz I am NOT opening up Visual Studio Code to finish this LCP) so any information on the state of the editor would also be helpful

EDIT: Turns out that even when it works and exports, COMP/CON doesn't take the LCP. I keep getting an error that reads "ERR_ACTION_ACCESS_UNDEFINED: Are you trying to access this.someMutation() or this.someGetter inside an @action? That works only in dynamic modules. If not dynamic use this.context.commit("mutationName", payload) and this.context.getters["getterName"] 6fc5/g/"

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

No branches or pull requests

1 participant