Jump to content

King Diamond

Members
  • Content Count

    31
  • Joined

  • Last visited

About King Diamond

  1. To clear all misunderstandings here is that I've already told to yarpen: So, I'm not a guy to be asked for any PERMISSION, sorry....
  2. Damn! I think I even have a copyrighted nickname here! But probably...that's a nice opportunity to ask for an autograph while being sued by King himself....
  3. That is my thouht exactly And as soon as that DVD will have a PRICE (even 1 cent - doesn't matter) it's a business subject since that moment with a whole corresponding matter (and possible consequencies ). I have a strong feeling that the modding community should stay distant from that and remain 100% altruistic . A nice list of links with detailed descriptions would be more than enough IMHO.
  4. May be It's not so important. I should have been more specific... sorry. There's just a double set of identical AR6400 Northern links to AR3000, AR5202 and AR5200. One set could be removed safely.
  5. Plz look at links for AR6400. I think there's some mess with it (possible wrong indexing for area entry)...
  6. Then we should ask Avenger about the exact mechanism of how engine handles and executes various actions 'coz I think he's the only person (really?) who studies disassembled code... 2Avenger Have you taken a look into that matter already? Does engine execute all actions instantly, in a single thread, or start separate threads for some actions without waiting for them in a main script running thread(that definitely would take some extra time to complete)?
  7. It's necessary to recreate INSTANT.IDS than, 'coz SetGlobal() is listed there...
  8. It's necessary to use Continue() very carefully.... So, here's a code: IF Global("wmSpawnJoluv","GLOBAL",0) THEN RESPONSE #100 CreateCreature("wmart1",[1337.1751],4) // Joluv SetGlobal("wmSpawnJoluv","GLOBAL",1) Continue() END IF Global("wmSpawnJoluv","GLOBAL",0) THEN RESPONSE #100 CreateCreature("wmart1",[1337.1751],4) // Joluv SetGlobal("wmSpawnJoluv","GLOBAL",1) Continue() END IF Global("wmSpawnJoluv","GLOBAL",0) THEN RESPONSE #100 CreateCreature("wmart1",[1337.1751],4) // Joluv SetGlobal("wmSpawnJoluv","GLOBAL",1) Continue() END Do you know what results will it produce? There will be all 3 Joluv's spawned All those SetGlobal()'s just don't take effect if the code is in the same pass. But if we remove the very 1st Continue() (that will force to end the 1st code pass) all triggers below will work as it should be.
  9. pipe04.bcs I simply forgot about. MISC_02A is still missing....
  10. + I think all effects of that spell should Bypass Resistance. + a thought about 'Create inventory item'(122) opcodes in spells. Shouldn't they all bypass resistance? I can give a list of possible suspects there: SPCL918, SPCL919, SPCL931, SPCL932, SPCL933, CDHLYSYM, SPIN829, SPPR207, SPWISH13
  11. I've already posted that some time ago but can't find that post to refresh it. So here it is again... Tracking spell (SPCL922) needs to be fixed. Original spell has a bug. Upon casting it adds itself as a new innate ability once again to obtain an effect of constant presence of itself in a spellist. But all that extra charges are going to reappear after the rest altogether. To prevent that it's necessary to remove this spell from the spellbook by applying effect with opcode 172 each casting. Then the newly added innate will be the only one, exactly as it should be. Like this: COPY_EXISTING ~SPCL922.SPL~ ~override~ //Tracking READ_LONG 0x6a eff_offset READ_SHORT 0x70 glob_eff_cnt INSERT_BYTES eff_offset 0x30 //fixing stockable Tracking innates WRITE_SHORT eff_offset 172 //Remove spell WRITE_BYTE eff_offset+2 1 WRITE_BYTE eff_offset+0x0c 1 WRITE_BYTE eff_offset+0x12 100 WRITE_ASCII eff_offset+0x14 ~SPCL922~ SET glob_eff_cnt = glob_eff_cnt + 1 WRITE_SHORT 0x70 glob_eff_cnt
  12. The problem is if one of your partymember died accidently having that key in inventory you will stuck there forever, without any chance for recovery. But if you just dropped it or forgot to pick it up you can return for it at any time. Is such reason Ok for you?
  13. Fixpack, Fixpack, Fixpack, Always use the Fixpack! That's a nice chanting...
  14. Just checked original BD once again - it was SoA/ToB issue workaround. Of course IPSION must be kept undroppable.
×
×
  • Create New...