Notes |
|
(0001791)
|
khaos
|
01-12-13 09:30
|
|
Even though you are a dev now. I have to note this: nameloc technically exists. You can store tag.nameloc=<args> and parse it to an empty cliloc. This then does the name for the item.
Sphere by default already parses <NAME> to an empty cliloc field and does this. Otherwise we'd have to build an entire list of possible names to check the cliloc # against. Which I don't plan on doing. This can be soft coded.
If you want; you can code in NAMELOC and have it grab from a list of names in SPHERE_DEFS.scp; like we do height. Otherwise I don't see any other use for hard code additions as more creatures get added and people will get new names.
Another thing to note is pulling from a list for every item/creature or however you do this. Though this might be optimal on some servers... I would make the coding to check for an OF_NAMELOC flags. So people can choose to parse the definition list or not. |
|
|
|
"changing item's names to #clilocid will give the name correctly in cliloc but showing You put the #clilocid in your backpack..."
I think the best solution is to fix the "You put the #clilocid in your backpack." message to actually work. |
|
|
(0001798)
|
XuN
|
01-12-13 23:15
|
|
Using name instead of nameloc leads to a problem with messages, also having nameloc let people with custom clilocs add their names to the items easily.
Fixing that message won't solve the problem if certain servers are using both client 203 and higher or if they doesn't want to use clilocs by turning out the option in the .ini. |
|
|
(0001804)
|
Ben
|
04-12-13 05:32
|
|
This is now implemented... se revision file |
|