Anonymous | Login | Signup for a new account | 19-04-25 05:41 CEST | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||
ID | Project | Category | View Status | Date Submitted | Last Update | |
0002235 | SphereServer | new feature request | public | 01-11-13 11:45 | 04-12-13 05:32 | |
Reporter | XuN | |||||
Assigned To | Ben | |||||
Priority | normal | Severity | minor | Reproducibility | have not tried | |
Status | resolved | Resolution | fixed | |||
Platform | Windows | OS | 8 | OS Version | pro | |
Product Version | 16-06-2013, 0.56b Prerelease | |||||
Target Version | Fixed in Version | 0.56c Nightly | ||||
Summary | 0002235: Nameloc to items | |||||
Description | Just like name but storing cliloc id for this item, so anyone can add (if they wish) custom clilocs and show them in item's names, or just showing default items localiced in vendors shop, etc Something like tag.cliloc can be made but it wont do the trick nice as when bouncing you will see the 'name' instead in the msg, when using .add and so on, also changing item's names to #clilocid will give the name correctly in cliloc but showing You put the #clilocid in your backpack... not a solution either. | |||||
Tags | No tags attached. | |||||
Nightly Version | Automated (specify build number) | |||||
Experimental Flags | None | |||||
Option Flags | None | |||||
Internal Build Number | 1672 | |||||
Attached Files | ||||||
![]() |
|
(0001791) khaos (developer) 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. |
(0001797) RanXerox (developer) 01-12-13 22:37 |
"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 (developer) 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 (manager) 04-12-13 05:32 |
This is now implemented... se revision file |
![]() |
|||
Date Modified | Username | Field | Change |
01-11-13 11:45 | XuN | New Issue | |
01-12-13 09:30 | khaos | Note Added: 0001791 | |
01-12-13 09:30 | khaos | Assigned To | => khaos |
01-12-13 09:30 | khaos | Status | new => feedback |
01-12-13 22:37 | RanXerox | Note Added: 0001797 | |
01-12-13 23:15 | XuN | Note Added: 0001798 | |
01-12-13 23:15 | XuN | Status | feedback => assigned |
03-12-13 19:41 | XuN | Status | assigned => closed |
03-12-13 19:41 | XuN | Resolution | open => fixed |
04-12-13 05:32 | Ben | Note Added: 0001804 | |
04-12-13 05:32 | Ben | Assigned To | khaos => Ben |
04-12-13 05:32 | Ben | Status | closed => resolved |
04-12-13 05:32 | Ben | Fixed in Version | => 0.56c Nightly |
Copyright © 2000 - 2010 MantisBT Group |