• Hello game master! Welcome to our growing community. Please take a moment to Register (top right button, see how: Slides).

    If you use Campaign Logger, you can use the same login details - we've linked the app to this forum for secure and easy single sign-on for you.

    And please drop by the Introductions thread and say hi.

Creating Campaign Entries from within Campaign Logs

vnavone

New member
Hireling for Adventure
If I'm making a Campaign Log and name a brand new character by typing "@name", shouldn't "@name" then automagically become a Campaign Entry? Seems weird that I should have to go to Entries and manually add that character if it already exists in a Log. See video:
video
 

JochenL

CL Byte Sprite
Staff member
Wizard of Adventure
Beta-Tester
Faster Combatant
Adventure Builder
Gamer Lifestyle
Adventure Master
You are right and this is an ongoing discussion.

Consider this: You create a post where you mention @name for the first time. @name is automagically created. You then edit the post manually to contain @nombre instead of @name. @nombre is automagically created. Now you have @name and @nombre.

My fear is that this rapidly escalates.

Maybe the system recognizes which CEs are empty and used nowhere and drops them silently?
Maybe automagically created CEs are only "virtual" as long as they are empty?
That way I could list all tags as CEs and show the virtual ones (those without actual content) in a lighter color and with a dotted border.

Ideas and suggestions are welcome!
 

vnavone

New member
Hireling for Adventure
How about if all tags that are orphaned or don’t have any associated entries go into a unique category on the Campaign Entries page, from which you can either promote or delete them? That category could be called something like “pending” or ”orphans”. I like your “virtual” idea too, where tags remain in place with other entries, awaiting confirmation or dismissal.
 

javalen

New member
Wizard of Adventure
Adventure Builder
Adventure Master
Consider this: You create a post where you mention @name for the first time. @name is automagically created. You then edit the post manually to contain @nombre instead of @name. @nombre is automagically created. Now you have @name and @nombre.
I don't know React (just Vue) and I obviously don't know how your website is set up, but I would try to decouple the name from the tag itself, once it has created. It seems like it is already creating a UUID for the entry when it is created, so editing @name -> @nombre could just change the name field of the associated entry for the associated UUID, but changing it to an already existing entry would update what is being injected.

Again, I know its easier to type out than actually do.
 

JochenL

CL Byte Sprite
Staff member
Wizard of Adventure
Beta-Tester
Faster Combatant
Adventure Builder
Gamer Lifestyle
Adventure Master
You are right; the name and ID are decoupled. I want to leave renaming a tag a conscious, explicit action. Guessing which tag was renamed into which other just by looking at a log entry change will rapidly become difficult and uncertain.
 

javalen

New member
Wizard of Adventure
Adventure Builder
Adventure Master
Probably a good decision, but I've had the same wish that an entry would be created without me having to manually create it.

Maybe if you click on an entry that hasn't been created, it creates it and navigates to it, instead of the entries page? This could be done along with the orphan idea above.
 

JochenL

CL Byte Sprite
Staff member
Wizard of Adventure
Beta-Tester
Faster Combatant
Adventure Builder
Gamer Lifestyle
Adventure Master
Maybe if you click on an entry that hasn't been created, it creates it and navigates to it, instead of the entries page? This could be done along with the orphan idea above.
That was my idea about the virtual entries and how they should behave.
 

Toasty

Member
Hireling for Adventure
Wizard of Adventure
Adventure Builder
Adventure Master
There is a mechanism from a wiki that I think worked well.

If you have a link to a page that exists, the link shows up as blue. But if the link is to a page that doesn't yet exist, it is red. And clicking on a red link brings you to a new blank page where you can fill out information, after which the link will turn blue.

The analogy here is that creating a new user with @name will show up as red if "name" doesn't exist. Click on "name", and it takes you to the character page where you can fill out that character info. Or, don't click on it yet if you are not yet ready to do so.

If I have a link to @name, and I change it to @nombre, and "nombre" doesn't exist, then you are specifying a new name, and you get a red link.

If what you really wanted to do was to rename "name" to "nombre", then go to the "name" character and rename it "nombre", and it will change everywhere it is used.
 

JochenL

CL Byte Sprite
Staff member
Wizard of Adventure
Beta-Tester
Faster Combatant
Adventure Builder
Gamer Lifestyle
Adventure Master
As tag link colors can be changed by the user, I don't want to use it to indicate a non-existing campaign entry. Within a log, this functions already as desired. If you click a tag you get a filtered list and the campaign entry at the top. If it is not there yet, you can just fill it.
The "problem" is that, in the campaign entry overview page, there are only existing campaign entries shown and you have to remember an existing tag's exact name to create a campaign entry for it. I think the virtual entries will help that. They could be recognized as more lightly colored and behave like the Wiki you mentioned.
 

JochenL

CL Byte Sprite
Staff member
Wizard of Adventure
Beta-Tester
Faster Combatant
Adventure Builder
Gamer Lifestyle
Adventure Master
I am planning virtual entries for implementation.
 
Top