Page 1 of 1
Hacked Door?
Posted: Sun Feb 12, 2006 4:56 pm
by Szopeno
Hi. I am new here. I have just registered but i can't stand waiting to ask this question until the activation code hits my email. So I ask yet as a guest. How to make hacked door in RTC? I tried to use option 'hacked' but it seems it doesn't work. Any help?
PS: Sorry for my English. :>
Posted: Sun Feb 12, 2006 6:45 pm
by beowuuf
The hacked door is actually a different door type - so you need to change say door_portcullus to door_portcullus_broken
A hackable door used the option' STRENGTH=(BASH:0,FIRE:100)' to show lack of immunity to chopping
Posted: Sun Feb 12, 2006 7:17 pm
by Da_Ruby
Umm yeah but the broken door dont actually let yolu walk through them.... (or at least i think i need to check another dungeon to see if there is an already bashed door....)
They act like a normal dooir, you can see through them but not walk through them :O
(or am i being an idiot)
Posted: Sun Feb 12, 2006 8:24 pm
by Gambit37
Edit the door and select the 'hacked' raido button. All doors are 'closed' by default, even the hacked ones.
Probably a good feature request: GG -- can you make broken doors automatically hacked when placed in the editor?
Posted: Sun Feb 12, 2006 8:45 pm
by beowuuf
They are aren't they? the Door_portcullis_broken etc placement...
Posted: Sun Feb 12, 2006 8:58 pm
by Szopen
I am using the radio button 'hacked'. But the state of door doesn't seem to change. After operation, door remain closed or opened. If closed, they don't let you go through them. The look is ok. When opened, they allow you to pass but the look is wrong. They look like normal opened door. There's no for example shattered wooden remains along doorframe. And I'm using RTC 0.34. Any suggestions?
Posted: Sun Feb 12, 2006 9:24 pm
by beowuuf
Yeah, that's weird - there seems to be somehting missing. As you say, a 'hacked' door behaves like a closed door, and if you put 'state=(open) the it looks like an open door!
Posted: Sun Feb 12, 2006 9:28 pm
by Gambit37
Ah, that's your problem, v034 has a bug on that screen: setting hacked doesn't get saved properly.
You can edit the text file manually if you find the code for your door and change it, like this.
Code: Select all
ref000805-2 DOOR_BLACK_BROKEN 5 8 0 STATE=(HACKED)
This bug is fixed in the v035 editor...
Posted: Sun Feb 12, 2006 10:10 pm
by Szopen
A, yes. I've just tried Gambit's 'straight-in-code' modification and it works. Thanks a lot! :>
Posted: Mon Feb 13, 2006 2:14 am
by Da_Ruby
ah cool, easily fixed then
Thanks Gambit
Posted: Tue Feb 14, 2006 4:45 pm
by George Gilbert
As Gambit mentioned this is something i've already fixed in V0.35 (can't find the post immediately, but it was fixed as part of another issue) - for now just change the txt file directly.
Unfortunately I can't make "hacked" the default state for hacked doors in the editor. This is because the only thing that makes a hacked door hacked, is the "hacked" state! Other than the state, as far as the engine is concerned there is no difference whatsover between doors...