| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001756 | SphereServer | executable - generic | public | 22-05-10 18:25 | 25-05-10 01:00 |
|
| Reporter | alex | |
| Assigned To | MrSugarCube | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | 20-09-2009, 0.56b Prerelease | |
| Target Version | | Fixed in Version | 0.56c Nightly | |
|
| Summary | 0001756: sphere sends "reagents ammount" packets to everybody on each cast |
| Description | - player "Mage" casts himself Greater Heal
- player "Witness" watches player "Mage" cast
Sphere sends "Witness" packets about the reagents that were used on the cast (it tells the name of the reagent and the amount left of the that reagent on the container).
* see the uploaded file for a packet capture of such example, the "witness" captured the packets, and there was a mage casting 2 times a greater heal *
if you put 30 players on screen and someone casts a spell, every one of those 30 players will receive the packets from sphere telling the name and amount of reagents used... this leads to an unnecesary higher bandwidth usage (and increased lag) we run a huge shard and had to use ridiculous high value on "max packets per tick" to avoid lag, this bug is one of the main reasons: everybody complains about lag on PVP, specifically when mages start casting.
|
| Tags | No tags attached. |
|
| Nightly Version | 20-09-2009 |
| Experimental Flags | None |
| Option Flags | None |
| Internal Build Number | |
|
| Attached Files |  Packets.txt (Attachment missing) |
|
Relationships 
Relationships 