| Anonymous | Login | Signup for a new account | 08-09-10 03:00 CEST |
| Main | My View | View Issues | Change Log | Roadmap | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0001709 | [SphereServer 0.56b] executable - generic | crash | always | 16-01-10 05:44 | 24-08-10 22:37 | ||||
| Reporter | xantier | View Status | public | ||||||
| Assigned To | |||||||||
| Priority | normal | Resolution | no change required | ||||||
| Status | closed | Product Version | PreRelease/Nightly | ||||||
| Summary | 0001709: Tiledata Read error ! | ||||||||
| Description |
06:40:CRITICAL:Error Pri=2, Code=0, Desc='CTileItemType.ReadInfo: TileData Read', in GetItemData 06:40:ERROR:(sphere_item_misc.scp,1421)Setting new id for base type i_xbow_sup not allowed 06:40:ERROR:(sphere_item_misc.scp,1421)Setting new id for base type i_xbow_sup not allowed There are billions of errors like those. I'm using old tiledata and latest SVN. I can't add new item, all of them give error because of Setting new id on xx.. I was trying to code i_lightning_bow and i can't replace i_bow for ID= and same for ALL items (checker board uses 0fa6, same). |
||||||||
| Additional Information | |||||||||
| Tags | No tags attached. | ||||||||
| Nightly Version | Not Available | ||||||||
| Experimental Flags | None | ||||||||
| Option Flags | None | ||||||||
| Attached Files | |||||||||
|
|
|||||||||
Notes |
|
|
(0000349) xantier (reporter) 16-01-10 05:49 edited on: 16-01-10 06:07 |
- Added 0001657: Support for the increased tiledata size in client 7.0.0+. As a consequence, multis must now start from 08000 instead of 04000 and scripts must be adjusted accordingly (the default script pack has been updated). If an older client encounters an item within the 04000-07fff range they will only see a worldgem bit (01ea7). This causes everything happens on my server. I can't change my scripts again cuz i changed every file in my own pack and i don't want to do it again. There must be a feature for old tiledatas. I am using T2A tiledata for ERA server. |
|
(0000350) Terrikate (reporter) 16-01-10 13:42 edited on: 16-01-10 13:44 |
Solution. Update your scripts with the modified in scriptpack http://tracker.sphere.torfo.org/bugs/view.php?id=1684 [^] - Updated 0001684: sphere_item_magic_armor.scp, sphere_item_magic_leather.scp, sphere_item_magic_weapon.scp, sphere_item_misc.scp, sphere_item_profession_cartographer.scp, sphere_item_provisions_armor_color.scp, sphere_item_provisions_deed.scp, sphere_item_provisions_ore.scp (Replaced custom script IDs with defnames to fix conflicts with new tiledata size -- some items did not have a defname so watch out if you have any of these in an existing world save) EDIT. The only problem I have with sphere_multis.scp, because you have to use MULTIDEF, but you can have a copy of the old without problems |
|
(0000351) Terrikate (reporter) 16-01-10 13:48 |
Anyway, I forgot to indicate, the next error continues with the old version of tiledata even with all the changed objects. CRITICAL: Error Pri = 2, Code = 0, Desc = 'CTileItemType.ReadInfo: TileData Read', in GetItemData |
|
(0000352) xantier (reporter) 16-01-10 18:45 |
Thanks mrsugarcube for giving that recently fixed scripts.. |
|
(0000366) nolok (reporter) 27-01-10 22:00 |
I modified these files one month ago, i don't remember very well, but this error should be caused by a re-definition of the id of the item. Example: [ITEMDEF 01234] ID=i_arrow DEFNAME=i_arrow_fire If you use a numeric itemdef and later set an id, you'll get this error. But if you do: [ITEMDEF i_arrow_fire] ID=i_arrow You should not get this error. I hope this will help you :P |
|
(0000598) MrSugarCube (administrator) 24-08-10 22:37 |
Aa it's already noted, the problem here is caused by scripts not being updated after the resolution of 0001657. Any attempt to use an item (or multi) whose ID falls between 04000 and 07FFF will have its attributes read from tiledata.mul and produce this error if that file is still the old size. |
| Copyright © 2000 - 2008 Mantis Group |