Making a repeating field with a fixed amount of entries

Is it possible to create a repeating field with a fixed amount of entries without an add/remove button. Let's say 10 or 20.

If you want to make a section with a fixed number of entries, why do you want to make it a repeating field? Genuine question - I'm confused. Seems like it would be easier to just create normal fields and use CSS to control visibility if needed. Repeating fields introduce complications, and if you can do without them, it's a lot easier on the players (easily understandable attribute names, for example).

GiGs said: If you want to make a section with a fixed number of entries, why do you want to make it a repeating field? Genuine question - I'm confused. Seems like it would be easier to just create normal fields and use CSS to control visibility if needed. Repeating fields introduce complications, and if you can do without them, it's a lot easier on the players (easily understandable attribute names, for example). +1.

It's a good question the main reason is simplicity to write the workersheet functions and less possibility to make mistakes. Right now I'm writing stuff like "sorry the 20 extra skill spaces check which one changed, parce the word of the event that initialize the function, get the corresponding I'd, modify the value with the ID  Also I would like to have at least 5-10 repeating fields, as a minimum, already created but empty :)

This is possible by using sheetworkers to create the entries and css to hide the add/delete buttons. I could see it being a useful method for handling things that have essentially the same code repeated multiple times instead of handwriting each section and then copy/pasting with small changes (e.g. acrobatics instead of athletics) or using regex to programmatically generate the section of essentially repeating items. Doing this would (as an off the cuff estimate) remove a couple hundred lines of html from my sheets.

That would be great Scott. I know how to remove the button but not sure how to do the rest :( So far I created a fixed amount of fields manually and it's... Ok for me. But if someone has to refactor/change the sheet..  it would be a pain in the ass.

Honestly, i still think you're better off without using a repeating section. You can duplicate a section 10-20 times easily enough with copy/paste, and the only things you'd need to change within those section are attribute names which could be done again with fairly quick copy/paste. I dont think the extra lines in the html will make any difference efficiency-wise (probably better, honestly). You can write functions to handle all the attributes without duplication (some techniques for that here&nbsp; <a href="https://wiki.roll20.net/UniversalSheetWorkers" rel="nofollow">https://wiki.roll20.net/UniversalSheetWorkers</a> ), and you (and more importantly, the players when creating their own macros) don't have to deal with randomly generated UUID's in attribute names. That said, it's your sheet so I wont press the issue :)

you are probably right. My problem is many times I have stuff like on change skill1 change score1 on change skill2 change skill2 etc... My trick was parcing and get the number

That's definitely a solvable problem as that linked page should show. If you need help creating a sheet worker that does the same job for multiple stats, I'm always happy to help (and that link I gave may help too).

Oh no I solved it it's just... Not elegantly solved 😅.