setshape2

[Rogpog]

If you completely change the npc characteristics using setshape2 to nonblocking, it becomes unclickable and pretty hard to change or delete.

NPC Code:

---

if (created) setshape2 3,3,{0,0,0,0,0,0,0,0,0};

---

It also seems like type 20 still doesn't have a throw-through attribute (blocks player, but allowing npcs and projectiles through).

NPC Code:

---

if (created) setshape2 3,3,{20,20,20,20,20,20,20,20,20};

---

[Python523]

Originally posted by Rogpog
If you completely change the npc characteristics using setshape2 to nonblocking, it becomes unclickable and pretty hard to change or delete.

NPC Code:

---

if (created) setshape2 3,3,{0,0,0,0,0,0,0,0,0};

---

It also seems like type 20 still doesn't have a throw-through attribute (blocks player, but allowing npcs and projectiles through).

NPC Code:

---

if (created) setshape2 3,3,{20,20,20,20,20,20,20,20,20};

---

it's because for 0, it litterly becomes unblocking, you can move through it but, you CANT click on it
and 20 means you can throw something THROUGH the tiles, it doesn't mean you can walk through them, so if it allows projectiles and NPCs that you have picked up and thrown, then it IS working

[Rogpog]

lol, I mean it isn't letting them through. As far as I know, it's behaving exactly like type 22 (blocks everything)...

[Python523]

Originally posted by Rogpog
lol, I mean it isn't letting them through. As far as I know, it's behaving exactly like type 22 (blocks everything)...

try picking up a bush and throwing it over?

[Rogpog]

::Repeats experiment for the 146th time ::

Nope, still isn't working.
If I asked about the fuctionality of type 20 and clearly explained how it wasn't performing as expected, wouldn't it be obvious that it's been personally tested numerous times and that I know how it's supposed to work? :o

sorry, j/k... I know you're trying to help, but everything your telling me I've heard over and over again. Since setshape2 came out I've been trying to find possibilities for the syntax and still no luck with this particular one.

[Falcor]

It may only work with very thin throwthrough tiles, I think it was ment for fences, not just having one big object. although I could be wrong, Test it out doing something like....


setshape2 10,2,{20,20,20,20,20,20,20,20,20,20,20,20,20,20,20 ,20,20,20,20,20};

==========================================

Nevermind, I just tested it. It looks as though it is indeed a bug. Perhaps not with the command per say, just the hardcoded script for default throwing objects. Perhaps its only checking tile indexes and not tiletypes.

[Rogpog]

Yes, perhaps, and all his time people have ben saying I've been doing it wrong...

As for type 0, the only way I know of deleting an npc with all the params set is by converting the level to nw format and removing it using wordpad. Is there any way to fix this inconvenience?

[Python523]

Originally posted by Rogpog
Yes, perhaps, and all his time people have ben saying I've been doing it wrong...

As for type 0, the only way I know of deleting an npc with all the params set is by converting the level to nw format and removing it using wordpad. Is there any way to fix this inconvenience?

yes, don't make the whole npc have the shape of 0

[aylad]

Originally posted by Python523

yes, don't make the whole npc have the shape of 0

Now, I'm not up to date on all this new scripting syntax, but..... isn't this what "dontblock" and "dontblocklocal" is for?

[Python523]

Originally posted by aylad


Now, I'm not up to date on all this new scripting syntax, but..... isn't this what "dontblock" and "dontblocklocal" is for?

maybe you only want to make a certain part of an npc walkable? like the 2k1 ships

[aylad]

Originally posted by Python523

maybe you only want to make a certain part of an npc walkable? like the 2k1 ships

Read my quote: I was talking about making the WHOLE npc walkable. That's when you get a no-can-click problem, apparently, and I just thought you'd use dontblock instead.