![]() |
house customize problem - Printable Version +- SphereCommunity (https://forum.spherecommunity.net) +-- Forum: Sphere 0.56d (/Forum-Sphere-0-56d) +--- Forum: General Help (/Forum-General-Help) +--- Thread: house customize problem (/Thread-house-customize-problem) |
house customize problem - midikit - 05-10-2016 02:48 PM Hello, seniors server owner. I'm using SphereServer 0.56c Pre-releases and scriptpack. Call the customize mode and click on the building had items in the house site. However, there is no change to the following message is output to the server console. 12:57:WARNING:Invalid item 0739 being added to building 040017e5c by 01b485. The use .gm and gm mode should work without any errors. And, it can be built. Does it work only house customize gm mode? Without using gm mode, How does it work? Please help me. RE: house customize problem - rastrero - 05-10-2016 11:14 PM which house scriopt are u using? RE: house customize problem - midikit - 05-11-2016 02:09 AM rastrero Thank you for the reply. ![]() used SphereServer Community Script Pack (included) : sphere_house_system.scp or SphereCommunity / SShare / Systems - : housing24.scp (Author : Mordaunt) Both of these problems occur. RE: house customize problem - Mordaunt - 05-11-2016 03:56 AM What server version and what UO Client are you using? Housing scripts are not to blame here. Custom housing is in the source and depends on the right client version. All any housing script will do is call the functions that are already built in. RE: house customize problem - Coruja - 05-11-2016 04:44 AM Code: 12:57:WARNING:Invalid item 0739 being added to building 040017e5c by 01b485. this item 0739 is not on your script pack so sphere will give this warning when you try to add an "invalid" item using the house customization engine. So to fix this warning you just need add this item on your script pack PS: this item is already included on default script pack on /scripts/items/sphere_item_building_stairs.scp, maybe this file is missing on your server RE: house customize problem - midikit - 05-11-2016 06:02 PM Mordaunt Thank you for the reply. My Server version : 0.56c Pre-releases and 0.56d nightly My Client version : Classic client : 7.0.49.2 Enhanced client : 4.0.49.2 Coruja Thank you for the reply. /scripts/items/sphere_item_building_stairs.scp file was already being used. And I saw check the contents. [ITEMDEF 0738] DEFNAME = i_stairs_wood_2 RESOURCES = 50 i_board CATEGORY = Buildings - Stairs SUBSECTION = Wooden Stairs (dark) DESCRIPTION = Stair DUPELIST=0739,073a,073b,073c,073d,073e,073f,0740,0741,0742,0743,0744,0745,0746,0747,0748,07b3,07b4,07b5,07b6 [ITEMDEF 0739] // Wooden stairs (dark) DUPEITEM = 0738 And, .gm in the off state, and the items are made properly .add 0739. script also registered in the normally spheretable.scp. [RESOURCES] // Sphere.ini and spheretable.scp are automatic. // All the other scripts we want to load. scripts / sphere_admin.scp scripts / sphere_backward_compatibility.scp scripts / sphere_book.scp scripts / sphere_defs.scp scripts / sphere_dialog.scp scripts / sphere_events_human.scp scripts / sphere_events_npcs.scp scripts / sphere_menu.scp scripts / sphere_name.scp scripts / sphere_serv_triggers.scp scripts / sphere_skills.scp scripts / sphere_skillmenu.scp scripts / sphere_newb.scp scripts / sphere_speech.scp scripts / sphere_types.scp scripts / items / scripts / items / multis / scripts / stones / scripts / stones / guilds / scripts / stones / towns / scripts / npcs / scripts / speech / scripts / sphere_spawns.scp scripts / sphere_spells.scp Also it produced normally in the .gm off state .add command. customize to house state only occurs the problem. In using the .gm gm on state and customize house is operating normally. Even if you enter any item in the .gm off status customize, it does not create all the code out of the item. The gm off state does not make anything to customize. Both destined only item code, the same error occurs. plevel7 owner shall have the same error also gm off state. I tried using 0.56d nightly. But it could not be used with the same error. |