
I contributed a few NPCs, but the forms involved so much time and fiddly interactions I did not submit many. I used that site heavily for my D&D 3.5 campaigns. Her library grew to 100s of NPCs and you could sort by CR, Type, Tag, etc.

She built forms so you could upload NPCs, magic items, etc. I see the Library as an add-on, and not part of CL Core.Īnd some game systems will need more form elements than crunch.įor me, this all harkens back to a wonderful site that used to be called DM Lilith's Tools. While CL offers simple system neutral tools like the 3LNPC generator, I'd then like users to add crunch to those NPCs as needed for sessions. I'm thinking about this because I'd like similar forms for D&D, PF, and other game system Libraries. Your session could timeout, wifi drop, or some other issue. It's going to take you awhile to figure out each form element if you're in creation mode. With large forms like this one, I think auto-save would be great. Also, spinners instead of drop-downs, and screens with multi-select capabilty (eg just keep scrolling through each decision and tap as you go instead of forcing all decisions on one small pixel range).ĭesktop Mouse also provides easy click zones and can also take advantage of right-mouse buttons.ĭesktop Keyboard should provide logical keyboard shortcuts and logical tabbing orders so you never need a mouse to complete the form. No small drop-down tap areas - big circles or boxes.

Mobile means different screen orientations and making things easy to tap. I think next would be to design a form for three user types: A login provides any user data, for example. I think the first order is to make a smart form whenever possible.
