The following warnings occurred:
Warning [2] Use of undefined constant SAPI_NAME - assumed 'SAPI_NAME' (this will throw an Error in a future version of PHP) - Line: 3388 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3388 errorHandler->error
/showthread.php 116 build_archive_link
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/inc/functions.php 3324 build_forum_breadcrumb
/showthread.php 195 build_forum_breadcrumb
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/showthread.php 195 build_forum_breadcrumb






Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Spell fields problem
Author Message
Rizz
Master
**

Posts: 396
Likes Given: 21
Likes Received: 14 in 9 posts
Joined: Oct 2012
Reputation: 0



Post: #1
Spell fields problem
If you cast one spell field on another one, only the last one will be effective.
For example: if you cast a firefield and then cast a paralyze field on it, the firefield stops suddendly to work (you still can see the animation but you'll get no effect at all).

The same if you cast a firefield, then paralyze field and then the poison field: only the poison field will work, you will get no effects from the preavious two.

Is that normal?
(This post was last modified: 08-08-2014 06:51 PM by Rizz.)
08-08-2014 06:50 PM
Find all posts by this user Like Post Quote this message in a reply
XuN
Sphere Developer
*****

Posts: 852
Likes Given: 102
Likes Received: 156 in 119 posts
Joined: Jul 2013
Reputation: 30



Post: #2
RE: Spell fields problem
Will be fixed in my next commit. However ... take in count that using both ... will automatically remove the paralyze as you are receiving damage.

EDIT: I'll leave as exception T_TELEPAD and T_MOONGATE as you are leaving the place in the moment you 'reach' the item ( in other words you step it ) so the rest of the items under it will not be virtualy step. I will place,however, a check for paralyze flag to do not move characters in the case they have this flag, seems the more logic.

T_SHRINE will have the return removed too, so placing fields or something over them will make players die again when resurrecting, be carefull.


All of this is just ... default behaviour, @Step is being fired before all of this so a simple check with a return will get rid of what I've just wrote.
(This post was last modified: 08-08-2014 07:22 PM by XuN.)
08-08-2014 07:14 PM
Find all posts by this user Like Post Quote this message in a reply
amonvangrell
Banned

Posts: 337
Likes Given: 17
Likes Received: 32 in 20 posts
Joined: Aug 2012

britannia shard

Post: #3
RE: Spell fields problem
Thx XuN
08-08-2014 09:46 PM
Visit this user's website Find all posts by this user Like Post Quote this message in a reply
Rizz
Master
**

Posts: 396
Likes Given: 21
Likes Received: 14 in 9 posts
Joined: Oct 2012
Reputation: 0



Post: #4
RE: Spell fields problem
(08-08-2014 07:14 PM)XuN Wrote:  take in count that using both ... will automatically remove the paralyze as you are receiving damage.

That is what i want Tongue
08-10-2014 07:15 PM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 3 Guest(s)