Character Sheet Damage

"" has been used now in most all my character sheets. And have been doing so for months if not a year or more. It was an update I liked as it shows up well. Since I started using that code it has been probably more than 20+ character sheets. "[f=h1]" is another one used but only in the notes area. It is also being used in most all my character sheets. And most all my character sheets are 5e standard sheets with both sets of code in them.

That "" is primary in the "Notes" area but sometimes in the "Items" area. In the butchering recently received, that code was only in the "Notes" area. Rarely I ever use it in the "Items" area. And it was "weapon" and "Items" area that was being edit which didn't have that code in it. Just a thought.

This butched character sheet is also the first 5e standard sheet used since the new system code has been installed. I know cause the 5e standard sheet was alter and not the same as it has been before. The previous two butchering was on custom sheets and may have been just as some new system code was being used.

And I hope that a previous character sheet of "Sedaris of the Sea" can be dug up and replace the current butched sheet as any previously saved copy have to be tons better than the current butched sheet.

**** Grrrrr. 4th time! ****

It was the auto info put in the weapons area that triggered the loss. I'm fairly sure. I still lost terminus new data put in. Please Fix or remove that automatic selection function that is defective and disastrous.

Field codes were designed for custom character sheets. What you're doing is not what the code is designed to do.

I've started using NotePad++ for my custom sheet work, and for "archiving" characters by saving completed ones as text files. Notepad++ has some html understanding, but it isn't a full html renderer, obviously.

Yes. I have some for the one built-in sheet character I created (https://gamersplane.com/characters/dnd5/30319/)—interestingly, for a game @GeneCortess was running :). It uses checkboxes to track used spells. I put the code inside a 2col section in the items area. Uses table formatting as well (zebra, etc.). I did not have a problem with it when the game was active.

I disagree. I didn't activate the automatic weapons selection. It is built into the 5e basic character sheet. So, it is unavoidable as you put in weapon descriptions. It was not any code function that I added.

And if you add in the weapon descriptions before you add tons to the items and notes area, you will not see the bug effect as there wouldn't be anything to truncate.

Due to the fact that 5e basic character sheet has been alter with the new system that perhaps a bug was introduced.

That's good to know, potentially rules out the check box as the culprit.
I don't use the built-in 5e sheet, so I'm not very familiar. What is automatic weapon selection? I don't know what you mean by that.

On the standard 5e character sheet. When you mouse over weapon description area, it nicely hunts for previously used text just like the dice system does but I believe it is bugged. The search for the data isn't the fault, it is how it is displayed in weapon description area and that is different code form how it is displayed in the dice system code. It is the displaying part of the code for the weapon descriptions that I believe is bugged.

Custom sheets and standard sheets both use the same system editor program. There are not two system editor programs. This is a fine reason why one's coding used in custom sheets works the same in standard sheets. It is meant to be universal. One system editor program does it all.

But the weapon description feature of the 5e basic sheet goes out of the system editor program to get that info that it uses and to be sure from a programmer standpoint that is now a danger and apt for pitfalls. And surely where I would look for the bug.

Ex-programmer Gene.

I use the D&D 5e character sheet hosted on GP, and I have no idea what you're talking about. What are you using that allows a mouse-over of a text field to bring up "previously used text?" Is it when you are Editing the character sheet, or just viewing it? What is displayed in the weapon description area that is different from dice?

You mentioned adding html code to the character sheet. Is that in order to display the checkbox? What other elements are you adding to the standard sheet?

On my GP-hosted 5e character sheets, everything is just text. I don't use any code, I don't use any extensions or other things. It's difficult to figure out what might be the problem in your character sheets that no one else has experienced. Is there a way for you to show your character sheet and the code you're using so that we can better understand it?

Okay. To be exact as I can.

You use a 5e basic character sheet. You go to the 'Weapons' area. You mouse down to the 'Notes' area. It also does this in the 'Name' area. As you type there the system hunts for your older text that you have typed. It does this automatically. You will note that sometimes the system leaves the area highlighted which is probably a bug too. This part of the code is where I believe the bug is.

I have seen where the system will take the previous typed info that you accept and the reprint it to other entry area such as 'Attack Bonus' and 'Damage' fields. Which is a bug too.

None of that happens when I edit the 5e basic character sheet. However, that behavior sounds like your browser caching previous input, which I have seen in text fields on GP and elsewhere, for example when adding a dice roll to a game forum post. That is a feature of the browser, not GP.

Do you have a specific example of the weapon description code that is bugged? I'm wondering if your browser is interpreting the cached data in a weird way.

I hope my built-in windows 10 browser isn't the problem. I'm not using 3rd party.

As stated, the bug is on how the acquired text is being displayed. There is no error in retrieving it.

What is the acquired text?

Gesh. Acquired Text is the text that system tells you. It is the text that was last used on the field. In the 5e basic sheet. It is the last text used in the fields 'Name', 'Attack Bonus, 'Damage' & 'Notes' in the 'Weapons' area. That is acquired text as it is not what you just are now typing. It is text that the system has hunted for and is offering to you.

If you have done several 5e basic sheets then you have used different values for those fields and they system will display possible text for you to use. The system remembers what you have typed in those fields before.

Being that I have done 20+ 5e basic character sheets, it always offers me stuff. If you accept what it offers then you are accepting the acquired text and not using what you typed.

Sorry, I will clarify. What is the text being displayed for you?

If the system is trying to display everything you've entered into that particular text field, it really does sound like it's your browser. GP itself does not save nor cache the text you've entered. It should be possible to clear your browser's cache, though it will mean you'd lose anything from other sites that's also saved in cache.

CancerMan. I didn't write the programs and nor do have access to them. I have not foggiest notion where the system gets its information for the acquired text. I just know that the text submitted is text that I have previously used. This implies to me that the system going out of its way to find that data.

But the content of the field is not the problem as stated. It is how it is being displayed. Best to keep your focus there. So, it has NOTHING to deal with how it got it or what the data in the field was. Bug is in the display code within the system editor program for the acquired data display fields.

Display problems range from leaving highlighting and to being printed in other fields. Somehow this is all related to the truncations happening to the 'item' and 'notes' fields.

I have had two character sheets destroyed by this bug and have now fairly well figured it out. Because of the nature of the bug, it will not show up in custom sheets probably unless they use that acquiring text feature which would require that bugged display code that is used in 5e basic character sheets.

That is to say this is most likely a 5e basic character sheet bug only. That is unless some other sheet uses such then the bug in the system editor would affect those sheets too.

Gene, I'm beginning to think like CancerMan that it is some caching or clipboard issue. Perhaps the built-in sheets have some kind of anchor or identifier which allows the clipboard to "remember" past input whereas custom sheets, by definition, do not so nothing is retained. Have you tried a different browser?

It's probably your browser. As I said, GP does not store any data you've entered in previous edits. Clear your browser's cache or saved session data, re-login, and try editing a character sheet again. Maybe use a test character sheet if you don't want to affect one of your existing characters.

Avraham & CancerMan. So, it has NOTHING to deal with how it got it or what the data in the field was.

Content from the browser or cache doesn't matter. It is not a content problem. So different browser or clearing the cache would have no effect. It is strictly a display problem. Highlighting is obviously a program bug. Printing in multiple fields is a program bug.

This probably only effects the acquired data feature in 5e basic sheet. If it was a browser or cache, other problems would be occurring as those are wide problems and this is a narrow one.

Gene, the sheets are stored in GPs database. Those with knowledge of the backend have stated that the backend database knows nothing about what may have been typed there before. It only knows what is saved to the database when the "save" button is hit. When previously typed data manifests on someone's screen in a browser window, to my knowledge, that can only be from a cache or a clipboard on the user's own machine. By what mechanism do you believe this "acquired data" works, if it isn't something stored on GPs database, as stated by CancerMan and @Keleth if I recall correctly?