Job names are Porings

[LadyNanuia]

Right so, ive got a wierd issue i cant seem to figure out, all job names are "Poring",

I did some changes to Msg_conf & Pcjobname.lub and Msgstringtable to have some custom names, they all turned to Poring, however i changed all of these back (to unedited versions to make sure i didnt make a mistake)

AND ITS STILL PORING..

Edit : My client version is 20231104 and Server is the latest rA to provide potentially relevant details.

I'd appreciate any advice on how i might solve this issue / where to look, thank you

Edited May 7, 2024 by LadyNanuia

[Chaos92]

41 minutes ago, LadyNanuia said:

Right so, ive got a wierd issue i cant seem to figure out, all job names are "Poring",

I did some changes to Msg_conf & Pcjobname.lub and Msgstringtable to have some custom names, they all turned to Poring, however i changed all of these back (to unedited versions to make sure i didnt make a mistake)

AND ITS STILL PORING..

Edit : My client version is 20231104 and Server is the latest rA to provide potentially relevant details.

I'd appreciate any advice on how i might solve this issue / where to look, thank you

jobdb is readed as it should be or not ? @job anything does it gives you the skills ?

You client seems new compare to released one so I dont know if there is related issue about that.

How about use the clean one before u change any files.

[LadyNanuia]

4 hours ago, Chaos92 said:

jobdb is readed as it should be or not ? @job anything does it gives you the skills ?

You client seems new compare to released one so I dont know if there is related issue about that.

How about use the clean one before u change any files.

Doing @job works fine, all classes work perfectly fine, it just says "Poring" in the name field in the top left and in the character screen, same with party so..

[munkrej]

Without seeing the pcjobname.lub file it's impossible to tell exactly where the error is. But I imagine it's either that the filename's case in your grf and your patch missmatches or the file is missing the correct function. Just taking a semi-default file and replacing it in your grf works as intented.

So I'd advice this:

* check the exact case of your pcjobname.lub - e.g. PCJobName.lub

* create a deleting patch for that file

* patch in your original / fixed file

(double check in the grf that your file was applied correctly)

 

[LadyNanuia]

On 5/7/2024 at 9:37 PM, munkrej said:

Without seeing the pcjobname.lub file it's impossible to tell exactly where the error is. But I imagine it's either that the filename's case in your grf and your patch missmatches or the file is missing the correct function. Just taking a semi-default file and replacing it in your grf works as intented.

So I'd advice this:

* check the exact case of your pcjobname.lub - e.g. PCJobName.lub

* create a deleting patch for that file

* patch in your original / fixed file

(double check in the grf that your file was applied correctly)

 

I see your picture from our server but thats before the last patch that caused this issue, it was working fine for a year or so before.

[munkrej]

Did you even read my message? The picture is from the date I posted. If you patch the file correctly it would look like that.

Edited May 19, 2024 by munkrej