Questnet Symbols Problem!
I think Im Dead
27 Nov 2004, 10:07Alright Alex, lately I've been doing a lot of coding on news posting and forum type of scripts for use on Questnet server. All of this is going quite well, except for unfortunately if someone uses a single percent sign % in string of text they type in, it crashes the server.
I know this is caused due to Quest not finding the other % sign to close off the assumed numeric variable, but the problem is that I know Quest can print such symbols.
We know this because the default say command hardcoded into Questnet will allow you to message any kind of symbol you want(so far that I've tried) to other players. So somehow Quest is capable of storing and interpretting the symbols but it's hardcoded. Is there a fix to this you can start working on for the next version perhaps? Is this possibly a bug? I only think it's a big deal because well, in a text game, you need to have no limit to the assortment of text you can use, and this does include characters and symbols outside of the alpha-numeric spectrum.
Here's what Questnet spits out in the script log...
Line parameter <User.RNETitlePreview[userid]; $removeformatting(Using percent signs crashes quest see % ?)$> has missing %
Some sort of response to this would be greatly appreciated.
I know this is caused due to Quest not finding the other % sign to close off the assumed numeric variable, but the problem is that I know Quest can print such symbols.
We know this because the default say command hardcoded into Questnet will allow you to message any kind of symbol you want(so far that I've tried) to other players. So somehow Quest is capable of storing and interpretting the symbols but it's hardcoded. Is there a fix to this you can start working on for the next version perhaps? Is this possibly a bug? I only think it's a big deal because well, in a text game, you need to have no limit to the assortment of text you can use, and this does include characters and symbols outside of the alpha-numeric spectrum.
Here's what Questnet spits out in the script log...
Line parameter <User.RNETitlePreview[userid]; $removeformatting(Using percent signs crashes quest see % ?)$> has missing %
Some sort of response to this would be greatly appreciated.
paul_one
27 Nov 2004, 15:21It says in the help file that two %%'s will act as one, so maybe try that?
I don't know about the user input though...
I don't know about the user input though...
Alex
27 Nov 2004, 16:27I see the problem - I can't think of a workaround for it though. I'll fix this in the next version. Do you really mean that it crashes the server though? It should just print an error to the log file and carry on.
I think Im Dead
27 Nov 2004, 17:06Here's a screenshot of the server crashing. *click* The shot is a little hi-res and is about 212k, so sorry for anyone on a slow connection, but I wanted it to be readable...
In the screenshot you can see in the Questnet text display where the first line of text is stored fine, so it's not a coding issue. I believe Questnet also does this with the more obvious signs like # and $, though you may want to check others if you plan on adding a fix.
You can also notice the debug log window has a little new text it's scrolled, which is probably the previously mentioned "Line parameter <User.RNETitlePreview[userid]; $removeformatting(Using percent signs crashes quest see % ?)$> has missing %"
In the screenshot you can see in the Questnet text display where the first line of text is stored fine, so it's not a coding issue. I believe Questnet also does this with the more obvious signs like # and $, though you may want to check others if you plan on adding a fix.
You can also notice the debug log window has a little new text it's scrolled, which is probably the previously mentioned "Line parameter <User.RNETitlePreview[userid]; $removeformatting(Using percent signs crashes quest see % ?)$> has missing %"