![]() |
The Black Wyrm's Lair Terms of Use |
![]() ![]() ![]() ![]() |
![]() |
![]()
Post
#1
|
|
![]() The Tactician ![]() Distinguished Developer Posts: 7793 Joined: 1-December 05 ![]() |
This tutorial contains a false comment inside one of its codes:
QUOTE This is a technique used to account for the pause between spellcasting. It cuts off spellcasting actions when they cannot be performed,[...] So, you might have the following block: IF !GlobalTimerNotExpired("castnattack","LOCALS") HaveSpellRES("spwi999",Myself) THEN RESPONSE #100 SetGlobalTimer("castnattack","LOCALS",6) // Timer always set to 6, as that is the duration of the pause SpellRES("spwi999",LastSeenBy(Myself)) END Well, this is wrong! As I have mentioned elsewhere the duration of the pause is NOT 6. I don't know how many modders might have been misled by the fasle comment inside the code which says "as that is the duration of the pause", but it's now perhaps the time to let people know that it is false. The duration of the pause varies from spell to spell (it's not 6 for every spell). I know the exact duration of the pause for each and every spell, but the easiest way to implement the correct duration of the pause is to use "SpellNoDec" instead of "ForceSpell" as it is implemented in Improved Anvil. -------------------- Improved Anvil
![]() Cheating is not confined to using external software or the console commands. Abusing the flaws and limitations of the game engine to do something that a human Dungeon Master would not accept or allow is cheating. |
|
|
![]() |
![]()
Post
#2
|
|
![]() Master of energies ![]() Council Member Posts: 3324 Joined: 9-July 04 From: Magyarország ![]() |
QUOTE I couldn't recollect now exact flow of my study, but one thing is certain: I was never, ever, having any problems with interpretation of cast'n'attack concept or mechanics, including delay between spells. That wasn't the point. The question (one of the questions, actually) was whether it's unclear or explicitly wrong. In my previous post, I pointed out that in case of technical problems, unclear/ambigious descriptions may result in malfunctioning in the practice.In this concrete case, there won't be any malfunctioning probably, as most modders just copy & paste the code, and this is not a very severe issue anyway. However, making accurate statements/explanations is a must in technical descriptions. It's a principle, regardless the actual effects in practice. It's okay not to make a big problem from such a minor issue, however, defending it i.e. introducing it as something insignificant is not okay. -------------------- Mental harmony dispels the darkness.
|
|
|
![]() ![]() |
![]() |
Lo-Fi Version | Time is now: 20th April 2025 - 01:42 PM |