Catalyst Gaming
Backup Sections => 
Half-Life 2 Roleplay => Archive => HL2RP Development[ARCHIVE] => Bug Reports => Topic started by: Khub on March 03, 2012, 07:05:36 AM
-
Hey.
Several loyalist may have their points history so big that we won't see it all. Expanding the textarea may be very, very helping. Doing same thing with the /viewobjectives, and maybe with /viewdata as well.
http://cloud.steampowered.com/ugc/486625647062920646/03C88D48810E499B6DE42B11F23D37DAC7D2BF5E/ (http://cloud.steampowered.com/ugc/486625647062920646/03C88D48810E499B6DE42B11F23D37DAC7D2BF5E/)
http://cloud.steampowered.com/ugc/486625647062924830/0B895F6C2EF97ABD80A2BD94B9F3721DC914928E/ (http://cloud.steampowered.com/ugc/486625647062924830/0B895F6C2EF97ABD80A2BD94B9F3721DC914928E/)
-
It would also be nice if they extended the text area in paper, I hate having to use 2 or 3 pieces of paper whenever I write announcements.
-
[suspicious]The problem is that Garry's mod LUA offers something called "usermessages" to transfer data between client and server. In the current version (not being problem in GM13 anymore), there is a limit of maximum data size that can be transferred in one umsg. However, this can be hacked by sending multiple usermessages. (I at least believe this is the problem.)[/suspicious]
-
I was under the impression that you could click on the last letter and press the down arrow to view the entire record.
-
I was under the impression that you could click on the last letter and press the down arrow to view the entire record.
I believe I already tried that, I can try it again though.
-
K it's done by SQL. You reach 255 characters and ur runs out of space in the notes. I havent counted it but this is what I think it is due to karma talking to me about it.
-
Changing the database table's column datetype to TEXT is question of two minutes :)
-
It is text, how do you think we have reasons?
The issue is the character limit which may not exceed 255 or whatever. It can not be changed as it is the maximum. You would have to use extra fields and this is a complicated process.
-
It is text, how do you think we have reasons?
The issue is the character limit which may not exceed 255 or whatever. It can not be changed as it is the maximum. You would have to use extra fields and this is a complicated process.
Datetype VARCHAR, which is probably used, has it's range limited to 255, 1 byte. Datetype TEXt doesn't. It also has some limit but it is 256*256 I think, what is a bit more. Maybe some developer should respond us? :)
-
Yes, I know I am late. This has nothing to do with the SQL, never has. Paper is saved in text files, and the limit has to do with how usermessages work; nothing with SQL like Karma likes to say. It's just his way of saying "i dont know how to do this".
-
Isn't there a chance that you would redo the point history into datastreams, like Crap-head solved it on OCRP?
-
Lol, I thought my datapad file would be overflowing. Guess not... D:
-
Isn't there a chance that you would redo the point history into datastreams, like Crap-head solved it on OCRP?
Not really going to a problem since loyalist points are no longer used. ViewData rarely goes above the character limit, anyway. Same for ViewObjectives.
-
Well, it does not happen often any much.. But with the format we >should< have in the datafiles, two medical entries are enough to fill most of the space up.
-
The point system is gone now anyway... So... Yeah. I don't think we need to worry about this glitch anymore.
-
the format we should have in the datafiles, two medical entries and two detainment records are enough to fill the UMSG space up.