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
Warning [2] count(): Parameter must be an array or an object that implements Countable - Line: 786 - File: showthread.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/showthread.php 786 errorHandler->error






Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Combat engine / Targetted Hit
Author Message
Coruja
Sphere Developer
*****

Posts: 987
Likes Given: 5
Likes Received: 226 in 187 posts
Joined: Jul 2012
Reputation: 7

Dimension Shard

Post: #1
Combat engine / Targetted Hit
This week I'm taking a look on sphere internal combat engine to make many optimizations/improvements, and for my surprise, I found an reasonable big code about some features that honestly I think it must be done by scripts and not hardcoded:
  1. the COMBAT_TARGETTEDHIT setting on sphere.ini, which will force the char hit an targetted region of the body (head/foot/...)
  2. the internal "hit location" messages, which are just messages like "You hit someone on the head/foot/..." and doesn't make any difference on the real damage
  3. the old [Physical/Fire/...]DAMAGE behavior which add an aditional damage for each *DAMAGE used. Note that we already have a new DAM[Physical/Fire/...] which this one works correctly as it should be, it will split the base damage into different types and use RES[Physical/Fire/...] to resist each one. The idea is remove the old *DAMAGE and use only the new DAM*

I think these 3 features can be removed from the internal source, it will make the combat code much more clean and optimized (in other words: lightweight / fast), and if someone still want these features, it can be done on script-side without any problem. The main idea is optimize the code making it lightweight, and if someone want aditional damages, formulas, etc, it can be done using scripts

so the question is: someone still using these features? If yes, there's any problem to move it from hardcoded to scripts?
(This post was last modified: 01-21-2015 11:20 AM by Coruja.)
01-19-2015 11:39 AM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Messages In This Thread
Combat engine / Targetted Hit - Coruja - 01-19-2015 11:39 AM
RE: Combat engine / Targetted Hit - Coruja - 01-20-2015, 03:27 AM
RE: Combat engine / Targetted Hit - Coruja - 01-20-2015, 08:37 AM
RE: Combat engine / Targetted Hit - Coruja - 01-20-2015, 11:58 AM
RE: Combat engine / Targetted Hit - Coruja - 01-21-2015, 11:18 AM
RE: Combat engine / Targetted Hit - XuN - 03-21-2015, 06:00 PM

Forum Jump:


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