hello guys, someone has corrected the door of Zaken?

 

on my server, players are going into it with strider and also passing between it before the proper time ...

 

my zaken door:

door_begin	[Devil_006]	type=normal_type	editor_id=21240006	open_method=by_skill	level=7	close_time=120	height=245	hp=150000	physical_defence=1000000	magical_defence=383	pos={52423;219103;-3209}	range={{52423;219032;-3312};{52423;219032;-3312};{52423;219174;-3312};{52423;219174;-3312}}	default_status=close	master_name=[sunrise]	master_open_event=act_close	master_close_event=act_open	door_end

 

 

thx

it has nothing to do with the door,but with the geodata

i can't help you how to fix geodata...

no...is not...

 

the problem is only the door, DHX (pvpgamming) corrected only the door and solved the problem ...

just create zone to skill where is not possible to summon pet .)

It is a geo problem, period.

 

If you don't know anything about a subject, why bloody pretend you do and then reference someone else?

 

 

However, how you approach to solve the problem for you individually.. that's something else.

It is a world collision problem,

 

in correct server when trying summon pet in incorrect zone, server do not allow to do so and will send message

Here is a crude, temp fix. What it does is prevent pets from being summoned in the Zaken area. It will not prevent a player from bringing a Strider with them, it only prevents summoning them.

 

skill_begin	skill_name=[s_wolf_collar]	skill_id=2046	level=1	operate_type=A1	magic_level=1	effect={{i_summon_pet}}	operate_cond={{can_summon_pet};{op_not_in_area;[zaken_no_restart]}}	is_magic=0	mp_consume2=0	cast_range=-1	effective_range=-1	skill_hit_time=5	skill_cool_time=0	skill_hit_cancel_time=0.5	reuse_delay=0	effect_point=0	target_type=self	affect_scope=single	affect_limit={0;0}	next_action=none	ride_state={@ride_none}	skill_end

strider summoned elsewhere

player goes to the door, then clicks unmount

big chance to get through if problems with collision :)