in expressions in a return statement could sometimes cause the entire return to be optimized out. A subtle bug with string concatenation in the compiler caused some complex projects, particularly when Unicode was involved, to get stuck during compilation.Some memory leaks were discovered with the handling of filters, especially in mutable appearances and animation.Saving a filter that used aliases for some of its var names caused a crash.Regression: Plane masters with blend modes other than the default did not display correctly.Dividing a matrix by a numerical constant at compile time compiled the result incorrectly as the number 0.gradient() could compile incorrectly when given a bad set of arguments, resulting in proc stack underflow at runtime.The problem appeared in build 514.1586 when the old cruft masking the issue was taken out.
Byond dream seeker out of date code#
This was caused by a fix to an earlier bug but was still being masked by old code that should have been removed. or ?: operators on the left-hand side of an assignment, or with any other side-effect operator like ++, did not compile correctly and caused the null check not to work as it should.
Turfs in images' visual contents on a different Z level showed a turf from the player's current Z level at the same XY coordinates.
/image in lists defined at compile time for vars could cause a crash in the map editor.The server could hang if it received a profile request from Dream Seeker (only using the profiler window, not the browser-based version), if the server had more than 64K procs defined.Calling an external library would not decrease the refcount of the arguments that were sent, except when the call()() used an arglist.BYOND 5.0 Version 514 Release Notes BYOND 5.0 Version 514 Release Notes Build 514.1589
0 kommentar(er)
