Cash ticket
#31


3 minutes ago, Scura said:




i prefer read what the strings say directly in the source. Specially if i need to manage the variables or attach the place holder into it ... just a personal preference hardcode it (you can of course attach a comment near to it, but i like the hardcode version)!




I thought there was a backdoor or vulnerability with the content of the lod files, I was already eating my head ?

#32


25 minutes ago, nicolasg said:




I thought there was a backdoor or vulnerability with the content of the lod files, I was already eating my head ?




nope, lod file are just the struct of db converted in a file ... but i guess you already know since you coded the string reader !

 

about the topic, i just thought to share the hardcoded version in case someone wanna use ^^

#33

I think lod is by far the easiest way, especially with the multi language system everyone uses because that doesn‘t even send the language info to the server. Furthermore you don’t have to add cases for every new language which i‘d personally forget when adding a new language later on ?  of course you can have a default string, but overall it seems to be a bunch of unnecessary work

#34


Just now, Desarija said:




I think lod is by far the easiest way, especially with the multi language system everyone uses because that doesn‘t even send the language info to the server. Furthermore you don’t have to add cases for every new language which i‘d personally forget when adding a new language later on ?  of course you can have a default string, but overall it‘s just a bunch of unnecessary work




don't know how is coded the multilanguage version since i didn't used it, should the lod have the same index per item? i seen many server's where index (about strings) are not sync, so you have to code the "switch" statment anyway, which start to make the lod idea pretty hard to be followed! 



Forum Jump:


Users browsing this thread: 1 Guest(s)