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

Allow import as Items #2

Open
farling42 opened this issue May 15, 2021 · 8 comments
Open

Allow import as Items #2

farling42 opened this issue May 15, 2021 · 8 comments
Assignees
Labels
Complex Core enhancement New feature or request

Comments

@farling42
Copy link
Owner

farling42 commented May 15, 2021

A single configuration flag to indicate if we create JournalEntry or Item (or Actor) objects.

@farling42 farling42 changed the title Import entries as Items Allow import of entries as Items May 15, 2021
@farling42 farling42 changed the title Allow import of entries as Items Allow import as Items May 15, 2021
@farling42
Copy link
Owner Author

Maybe set up a configuration window so that particular topic category_name values can be identified as Items rather than Journal Entries.

@farling42
Copy link
Owner Author

Items appear to be a type of Entity (or Document in 0.8) that can be customised differently for each Game System.

@farling42
Copy link
Owner Author

Now that 1.0+ is reading the RWexport file, we could read the section as soon as a file is selected, so that the user is able to select which categories are Items and which are Journal Entries (and maybe even Actors - so that JE's don't get created for things that should be only actors).

@farling42
Copy link
Owner Author

farling42 commented Oct 27, 2021

A simple two-column arrangement:

  • RW Category
  • What to import as: Journal, Item type 1, Item type 2, Item type 3, etc.

The item types can be determined from the world system's template file (using something like:

for (const item of game.system.entityTypes.Item) ...

Based on the game system, defined in RWexport file in top export element, game_system_id attribute (as long as it matches the Foundry game system), then we can use a predefined list of categories vs Item types.

@taspoff
Copy link

taspoff commented Feb 7, 2023

Now there is possibility to import .json in order to adapt every system game, would it be easy to import the RW "named equipment" and "named object" as foundry item (instead foundry journal) the most simply way (name +picture and everithing else as description?) ?

Once edited in Foundry, we could use the exported json as additionnal snipet in realmworks and keep it reusable?

@farling42
Copy link
Owner Author

farling42 commented Feb 7, 2023

Have you tried turning on this module option (although decoding for PF1 are implemented)?
image

@taspoff
Copy link

taspoff commented Feb 7, 2023

I did it, but it didn't worked as named object. But it worked with named equipment finally :)

@farling42
Copy link
Owner Author

I will have to check the workings, the full list for PF1 is:

{
		[ "Feat",                  "feat" ],
		[ "Archetype/Domain/Etc.", "feat" ],
		[ "Trait/Drawback",        "feat" ],
		[ "Skill",                 "feat" ],
		[ "Magic Item",            "equipment" ],
		[ "Mundane Weapon",        "equipment" ],
		[ "Mundane Item",          "equipment" ],
		[ "Mundane Armor/Shield",  "equipment" ],
		[ "Named Object",          "equipment" ],
		[ "Named Equipment",       "equipment" ],
		[ "Race",                  "race" ],
		[ "Class",                 "class" ],
		[ "Spell",                 "spell" ],
}

@farling42 farling42 added the enhancement New feature or request label Jul 4, 2023
@farling42 farling42 self-assigned this Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complex Core enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants