![]() |
tiletype/onwater/we else bug (not good)
I had a bug reported to me just recently with players getting hit on the edge of water. Classic sets gani based on tiletype clientside and uses an onwater check for damage serverside. I thought there may have been an inconsistency.
However, I find the onwater check to be consistent with the tiletype check both serverside and clientside. However, onwater and tiletype are not being consistent between the server and the client. I haven't tested onwall though, mainly because the movement system on Classic doesn't even use onwall. I also have a lot of people complaining to me about ctrl+z, but that's a different story. |
| All times are GMT +2. The time now is 08:47 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
Copyright (C) 1998-2019 Toonslab All Rights Reserved.