+- SphereCommunity (https://forum.spherecommunity.net)
+-- Forum: Sphere 0.56d (/Forum-Sphere-0-56d)
+--- Forum: General Help (/Forum-General-Help)
+--- Thread: Still have Main Threads error :( [last profiles] (/Thread-Still-have-Main-Threads-error-last-profiles)
Pages: 1 2
RE: Still have Main Threads error :( [last profiles] - Extreme - 09-24-2012 09:43 AM
I'll try the 2 scripts now. Rly thanks.
I should now use the .online? and not the .conteoips?
Use both, but conteoips you need to adapt it on your script.
You can cast equipped with a player ^_^ I have checked out it.
Im using Terrikate r1535 17.09.12 this last ...
When I have changed the sphere happend this, before not.
Can you check it and report it in the bug page?
Download the last one and try.
No, do it yourself.
RE: Still have Main Threads error :( [last profiles] - Lazarus - 09-24-2012 09:46 AM
(09-24-2012 09:43 AM)Extreme Wrote: I'll try the 2 scripts now. Rly thanks.
I should now use the .online? and not the .conteoips?
Use both, but conteoips you need to adapt it on your script.
You can cast equipped with a player ^_^ I have checked out it.
Im using Terrikate r1535 17.09.12 this last ...
When I have changed the sphere happend this, before not.
Can you check it and report it in the bug page?
Download the last one and try.
No, do it yourself.
Okay
... Just I don't have a account, because that I had asked to you 
Thanks for all Extreme ^_^I ill check it and report it.
RE: Still have Main Threads error :( [last profiles] - Lazarus - 09-29-2012 12:10 AM
.conteoips; .online; f_clear_elem..
Not are more in the server. [not using]
And still having issues...
Maybe? The isfriend?
Im thinking in change the housesystem [isfriend it's for there, if you are not friend you cannot open the door and boxes, I guess...]
I'm getting mad. 2 months and nothing, we can just take the real problem and fix it.. [We try everyday
]This is so... lame
Lazarus
And now; new problems: WARNING:95 chars at 2560,512. Sector too complex!
This is the region of minoc, there are like 30 npcs only... but we have a mistake on a script and this is happend. There; in 2560, there is nothing alive or death
RE: Still have Main Threads error :( [last profiles] - Extreme - 09-29-2012 03:31 AM
Thats a sector, not a map point.
You can fix this problem increasing the "maxcomplexity" thing in sphere.ini
I just don't remember what is it.
RE: Still have Main Threads error :( [last profiles] - Lazarus - 09-29-2012 03:40 AM
(09-29-2012 03:31 AM)Extreme Wrote: Thats a sector, not a map point.
You can fix this problem increasing the "maxcomplexity" thing in sphere.ini
I just don't remember what is it.
But that not is "fix" it's just generate more complexity
I didn't find that much of npcs... There is something wrong i guess but.. I will try to find more thanks!
RE: Still have Main Threads error :( [last profiles] - Skul - 09-29-2012 05:20 AM
You probably have a spawn gembit there that has a high <amount>, look around at the spawn bits and make sure all of the spawns are at a moderate amount. You should add this code to your i_worldgem_bit item
Code:
on=@item
message <name>
if (<type>==t_spawn_char)
if (<serv.chardef.<more1>>) || ( <serv.spawn.<more1>>)
message (Character Spawn: <more1>)
else
message (Invalid Spawn Worldgem Bit)
endif
elseif (<type>==t_spawn_item)
if (<serv.itemdef.<more1>>) || (<serv.template.<more1>>)
message (Item Spawn: <more1>)
else
message (Invalid Spawn Worldgem Bit)
endif
endif
message (Amount: <amount> MinDist: <strarg <morep>> MaxDist: <strarg <streat <morep>>> Distance: <strarg <streat <streat <morep>>>>)
return 1That or you have some invisible items somewhere, either under <p.terrain.z> or high above where someone would not normally notice, or maybe you have some nongen or memory items somewhere. Use this command to see if something is hidden:
Code:
.nuke say xRE: Still have Main Threads error :( [last profiles] - Lazarus - 09-30-2012 06:00 AM
(09-29-2012 05:20 AM)Skul Wrote: You probably have a spawn gembit there that has a high <amount>, look around at the spawn bits and make sure all of the spawns are at a moderate amount. You should add this code to your i_worldgem_bit itemCode:
on=@item
message <name>
if (<type>==t_spawn_char)
if (<serv.chardef.<more1>>) || ( <serv.spawn.<more1>>)
message (Character Spawn: <more1>)
else
message (Invalid Spawn Worldgem Bit)
endif
elseif (<type>==t_spawn_item)
if (<serv.itemdef.<more1>>) || (<serv.template.<more1>>)
message (Item Spawn: <more1>)
else
message (Invalid Spawn Worldgem Bit)
endif
endif
message (Amount: <amount> MinDist: <strarg <morep>> MaxDist: <strarg <streat <morep>>> Distance: <strarg <streat <streat <morep>>>>)
return 1
That or you have some invisible items somewhere, either under <p.terrain.z> or high above where someone would not normally notice, or maybe you have some nongen or memory items somewhere. Use this command to see if something is hidden:and nuke the sector, this will not remove any items, it will force the command 'say x' on any item.Code:
.nuke say x
Trigger on=@item???
I had try with .nuke say x; but nothing's there.
Just to know: The zone is Minoc Territory, Maybe we should change the name in others regions because... it's TOO big the pure region of minoc.
I will increase the max complexity.
---
Still having Main Threads... Every time.
5 mainthreads together...
We are gonna freak
Last profile gumps:
Code:
Profiles OFF: (0 sec total)
Thread 3308, Name=Main
IDLE = 0.0000s avg: 0.0000s [samples: 0 avg: 0 ] runtime: 1s
OVERHEAD = 0.0000s avg: 0.0000s [samples: 0 avg: 0 ] runtime: 1s
NETWORK_RX = 0.0000s avg: 0.0000s [samples: 0 avg: 0 ] runtime: 1s
CLIENTS = 0.0000s avg: 0.0000s [samples: 0 avg: 0 ] runtime: 1s
NETWORK_TX = 0.0000s avg: 0.0000s [samples: 0 avg: 0 ] runtime: 1s
CHARS = 0.0000s avg: 0.0000s [samples: 0 avg: 0 ] runtime: 1s
ITEMS = 0.0000s avg: 0.0000s [samples: 0 avg: 0 ] runtime: 1s
MAP = 0.0000s avg: 0.0000s [samples: 0 avg: 0 ] runtime: 1s
NPC_AI = 0.0000s avg: 0.0000s [samples: 0 avg: 0 ] runtime: 1s
SCRIPTS = 0.0000s avg: 0.0000s [samples: 0 avg: 0 ] runtime: 1s
FAULTS = 0 (total: 0) instances
Scripts: called 5227034 times and took 620931.5875 msec (0.1187 msec average). Reporting with highest average.
FUNCTION 'isbanned' called 1937 times, took 1.3364 msec average (1.2679 min, 2.5582 max), total: 2588.8041 msec
FUNCTION 'list' called 158 times, took 11.7840 msec average (2.0458 min, 32.5607 max), total: 1861.9170 msec
FUNCTION 'iscoowner' called 55001 times, took 0.1522 msec average (0.0379 min, 9.0438 max), total: 8384.6811 msec
FUNCTION 'isfriend' called 48131 times, took 0.7507 msec average (0.0371 min, 10.5392 max), total: 36148.3338 msec
FUNCTION 'guild' called 4 times, took 2.0536 msec average (1.9080 min, 2.2355 max), total: 8.2148 msec
FUNCTION 'admin' called 50 times, took 10.0474 msec average (3.9966 min, 21.2475 max), total: 502.3816 msec
FUNCTION 'admin_renderdialog' called 86 times, took 3.8390 msec average (0.3523 min, 4.4699 max), total: 330.1802 msec
FUNCTION 'f_autotele' called 831 times, took 0.1908 msec average (0.0843 min, 8.5956 max), total: 158.6904 msec
FUNCTION 'f_house_release' called 34 times, took 0.4909 msec average (0.0597 min, 0.7342 max), total: 16.7001 msec
FUNCTION 'f_house_secure' called 5 times, took 1.6219 msec average (1.1732 min, 2.4716 max), total: 8.1106 msec
FUNCTION 'estado' called 39 times, took 3.6158 msec average (2.1816 min, 19.4126 max), total: 141.0259 msec
FUNCTION 'f_onserver_save_ok' called 79 times, took 0.3115 msec average (0.1483 min, 0.4973 max), total: 24.6334 msec
FUNCTION 'f_house_eject' called 12 times, took 1.8259 msec average (0.0924 min, 2.1570 max), total: 21.9139 msec
FUNCTION 'f_house_lock' called 60 times, took 0.4965 msec average (0.0933 min, 0.5887 max), total: 29.7907 msec
FUNCTION 'stuck' called 34 times, took 0.2402 msec average (0.0491 min, 0.3277 max), total: 8.1757 msec
FUNCTION 'f_unfreeze' called 1234 times, took 0.3738 msec average (0.2643 min, 0.9253 max), total: 461.4691 msec
FUNCTION 'f_msg_queue' called 108 times, took 0.1589 msec average (0.0701 min, 1.3573 max), total: 17.1832 msec
FUNCTION 'f_house_add_friend' called 10 times, took 1.9958 msec average (0.3950 min, 5.4671 max), total: 19.9583 msec
FUNCTION 'f_sword' called 11 times, took 0.2025 msec average (0.1919 min, 0.2162 max), total: 2.2310 msec
FUNCTION 'f_onchar_delete' called 12 times, took 419.3582 msec average (399.7205 min, 434.1612 max), total: 5032.2998 msec
FUNCTION 'remove_invalid_houses' called 12 times, took 419.3202 msec average (399.6675 min, 434.1232 max), total: 5031.8438 msec
FUNCTION 'invalid_house_remove' called 12 times, took 419.1151 msec average (399.4691 min, 433.9441 max), total: 5029.3836 msec
FUNCTION 'conteoips' called 2 times, took 19.1802 msec average (12.7588 min, 25.6015 max), total: 38.3604 msec
FUNCTION 'f_guildsys_recruitguy' called 2 times, took 0.7164 msec average (0.6479 min, 0.7848 max), total: 1.4328 msec
FUNCTION 'f_guildsys_addchartoguild' called 2 times, took 0.3492 msec average (0.3255 min, 0.3730 max), total: 0.6985 msec
FUNCTION 'telenextchar' called 51 times, took 0.4188 msec average (0.0963 min, 1.5420 max), total: 21.3671 msec
FUNCTION 'f_macefighting' called 3 times, took 0.3297 msec average (0.3266 min, 0.3350 max), total: 0.9893 msec
FUNCTION 'regs' called 6 times, took 3.0134 msec average (1.3433 min, 10.9055 max), total: 18.0813 msec
FUNCTION 'g' called 10 times, took 1.8630 msec average (1.7395 min, 1.9804 max), total: 18.6325 msec
FUNCTION 'f_fencer' called 1206 times, took 0.1461 msec average (0.1299 min, 0.3461 max), total: 176.3012 msec
FUNCTION 'f_freeze' called 1206 times, took 0.3710 msec average (0.2198 min, 0.6211 max), total: 447.6845 msec
FUNCTION 'check_account_typedef' called 12 times, took 1.6001 msec average (1.1997 min, 2.0433 max), total: 19.2048 msec
FUNCTION 'f_check_typedefs' called 48 times, took 0.3297 msec average (0.1919 min, 0.7060 max), total: 15.8276 msec
FUNCTION 'online' called 2 times, took 12.3716 msec average (12.1503 min, 12.5929 max), total: 24.7432 msec
FUNCTION 'f_ajeitar_itens' called 4 times, took 1.3305 msec average (1.1651 min, 1.5739 max), total: 5.3229 msec
FUNCTION 'consumegold' called 1 times, took 0.3366 msec average (0.3366 min, 0.3366 max), total: 0.3366 msec
FUNCTION 'j' called 1 times, took 0.1598 msec average (0.1598 min, 0.1598 max), total: 0.1598 msec
FUNCTION 'f_jail' called 1 times, took 0.5901 msec average (0.5901 min, 0.5901 max), total: 0.5901 msec
FUNCTION 'f_add_potion' called 1 times, took 0.6761 msec average (0.6761 min, 0.6761 max), total: 0.6761 msec
FUNCTION 'f_fix_house_chars' called 5 times, took 1.9673 msec average (0.9477 min, 2.6909 max), total: 9.8371 msec
FUNCTION 'f_check_house_chars' called 5 times, took 1.7356 msec average (0.6946 min, 2.4221 max), total: 8.6784 msec
FUNCTION 'f_house_add_coowner' called 4 times, took 1.6697 msec average (1.6074 min, 1.7954 max), total: 6.6795 msec
FUNCTION 'house_find_guild' called 2 times, took 0.3380 msec average (0.3378 min, 0.3383 max), total: 0.6761 msec
FUNCTION 'f_house_demolish' called 1 times, took 1.6890 msec average (1.6890 min, 1.6890 max), total: 1.6890 msec
FUNCTION 'area' called 1 times, took 0.1514 msec average (0.1514 min, 0.1514 max), total: 0.1514 msec
FUNCTION 'f_remove_keys' called 1 times, took 1.5286 msec average (1.5286 min, 1.5286 max), total: 1.5286 msec
FUNCTION 'f_house_transfer' called 1 times, took 86.0486 msec average (86.0486 min, 86.0486 max), total: 86.0486 msec
FUNCTION 'addgold' called 1 times, took 0.3042 msec average (0.3042 min, 0.3042 max), total: 0.3042 msec
TRIGGER '@personalspace' called 7941 times, took 0.2813 msec average (0.0159 min, 1.3623 max), total: 2234.7594 msec
TRIGGER '@enter' called 21432 times, took 0.1863 msec average (0.0192 min, 9.7247 max), total: 3996.2265 msec
TRIGGER '@itemdclick' called 830254 times, took 0.1411 msec average (0.0807 min, 29.1422 max), total: 117234.9592 msec
TRIGGER '@dclick' called 625801 times, took 0.1533 msec average (0.0209 min, 13.4300 max), total: 96161.0162 msec
TRIGGER '@npcheargreeting' called 622 times, took 0.2953 msec average (0.2693 min, 0.5521 max), total: 183.7303 msec
TRIGGER '@npchearunknown' called 203 times, took 0.7018 msec average (0.6462 min, 0.9857 max), total: 142.4825 msec
TRIGGER '@spellcast' called 76323 times, took 0.1218 msec average (0.0553 min, 0.9603 max), total: 9311.4951 msec
TRIGGER '@spellsuccess' called 46841 times, took 0.1271 msec average (0.1075 min, 1.2903 max), total: 5966.1472 msec
TRIGGER '@dropon_self' called 12697 times, took 0.1913 msec average (0.1195 min, 0.8329 max), total: 2431.0891 msec
TRIGGER '@targon_char' called 495904 times, took 0.2752 msec average (0.0427 min, 56.3517 max), total: 136585.2296 msec
TRIGGER '@targon_ground' called 343 times, took 0.3724 msec average (0.0514 min, 0.5501 max), total: 127.7775 msec
TRIGGER '@step' called 346 times, took 0.1768 msec average (0.0645 min, 0.5032 max), total: 61.2629 msec
TRIGGER '@hit' called 113691 times, took 0.1276 msec average (0.0807 min, 9.8519 max), total: 14547.4241 msec
TRIGGER '@success' called 14209 times, took 1.2419 msec average (0.0108 min, 11.5490 max), total: 17647.7619 msec
TRIGGER '@targon_item' called 13 times, took 0.7387 msec average (0.0486 min, 2.1441 max), total: 9.6049 msec
TRIGGER '@npcseewantitem' called 18 times, took 0.1475 msec average (0.1293 min, 0.1852 max), total: 2.6602 msec
TRIGGER '@resourcefound' called 10 times, took 0.2590 msec average (0.0189 min, 0.7323 max), total: 2.5909 msecAnd:
This is in the Housing System; There is the most used function.. Im guessing that the housing system is the problem.
Code:
[FUNCTION isowner]
IF ((<DEF.ACCOUNT_OWNERSHIP>==1) && !STRCMP("<UID.<MORE2>.ACCOUNT>","<UID.<ARGS>.ACCOUNT>")) || (<MORE2>==<ARGS>) || (<UID.<ARGS>.ISGM>)
return 1
ENDIF
return 0
[FUNCTION iscoowner]
FOR 1 <DEF.MAX_HOUSE_COOWNERS>
IF (<TAG0.CO_OWNER_<dLOCAL._FOR>>==<ARGS>)
return 1
ENDIF
ENDFOR
return 0
[FUNCTION isfriend]
FOR 1 <DEF.MAX_HOUSE_FRIENDS>
IF (<TAG0.FRIEND_<dLOCAL._FOR>>==<ARGS>)
return 1
ENDIF
ENDFOR
return 0
[FUNCTION isbanned]
FOR 1 <DEF.MAX_HOUSE_BANS>
IF (<TAG0.BAN_<dLOCAL._FOR>>==<ARGS>)
return 1
ENDIF
ENDFOR
return 0