BYOND 4.0 Version 413.978 Release Notes

Fixes

The compiler was producing bogus "too many vars in program" errors when a project had >=65535 lines of code. Although, frankly, that's way too much code! (zackla21)

Movement was not working while the ALT button was down in the default skin. (Yakuto)

client/Command() was not resetting client.inactivity to zero. (Tiberath)

world/Topic() could intermittently crash for child servers created via startup(). The master argument may also correctly read as 1 now in some cases (possibly not all) where it was incorrectly set to 0.

BYOND limited background procs, including any proc waiting for results from input(), alert(), winset(), winget(), etc., to just over 65000 and did not account for the procs being finished. This caused behavior like no new input() or alert() boxes popping up.

When using multiple lines (not merely wrapping text) in a label control, the background color would appear over the background image within the rectangle where text is drawn. (Foomer)

When using a background image larger than the label itself, the image could overdraw other parts of the window.

Non-repeating key macros would cause focus to shift to the default input control if the key was held down. (ACWraith)

Key-up macros were still handled while an input control had focus even if the input control should normally handle them instead. (ACWraith)

Key-up macros could be received more than once in certain cases.

Commands received within a short time of each other, which commonly happened when receiving key-down and key-up macros close together, could sometimes cause the parser to ignore the second command. (Foomer)

Objects in statpanels and grids would always face south if object was not on map or in HUD. (ExAdv1)

Objects fitting the above criteria would also face south if their actual direction was the default for that obj type and did not get manually changed: (Crispy)

obj/wrong dir = WEST mob var/obj/wrong/OW Stat() if(!OW) OW = new stat(OW)

Moving or resizing controls in a minimized window (often triggered by browse() in older games) would cause the interface to resize elements incorrectly when restored.

In software rendering mode, icons that had been loaded were not properly cleared, so they would randomly replace other icons when drawn on the map. This problem became noticeable and got worse after successive reboots.

Software-mode wasn't rendering alpha values correctly (eg, in the map-editor or on the client, when hardware-mode was disabled).

Software-mode wasn't displaying icons with transparency or alpha on 16-bit displays.

The Options & Messages box would not pop up the first time a new error message came in, even if the checkbox telling it to do so was checked. If closed, subsequent messages would make it pop up normally.

The Options & Messages box would resize when new messages came in.

Users would occasionally get a bogus "visa expired" message.

Features

Updated some outdated pager & client links to the old website.

The 5-minute garbage collection cycle has been removed. Garbage collection due to reference counting should still work normally, so this cycle was probably redundant and eating processor time for no good reason.

The client command queue behaves more intelligently for repeating keys. Practically speaking, the major difference here is that you can now use key-up macros with any key-down macro regardless of whether the macro is set to repeat. The old, somewhat annoying behavior of "overshooting" a desired tile when holding down movement keys (due to the repeating movement commands being received late) is also gone.

The client now respects world.tick_lag, so you'll get faster client refreshes when using a lower tick_lag (like 0.5). Good for single-player games.

Error messages now also appear in the default output control, if any. Please note: The default skin now has a style for the output control:
```
.system {color:#FF0000;}
```
If you want error messages to appear in red like in older BYOND versions, add this or something like it to the default output on your game's skin.

Setting a control's new flash parameter can make it flash. Currently this is only implemented for window elements. Example:

By popular request, there are now client.pixel_x and client.pixel_y vars, for pixel-level adjustments to the player's view. Example:

Dantom.DB can now be access MySQL databases on windows (or unix). On windows, libmysql.dll must be available to system programs (eg, in C:\WINDOWS\system).

call() can now be used to access third-party libraries (.DLL files on windows, .SO files on unix), as long as the server is run in -trusted mode or permission is granted at runtime. These functions must be prototyped in the DLL as:
```
extern "C" char *func(int argc, char *argv[]) // argc = #arguments, argv[] = array of arguments
```
The call() function works the same way as the proc/obj call(), with the first two arguments being the library name and the function name. Example:
[test.dll, a win32 C++ library compiled in VC++]: #include <string.h> // This is an example of an exported function. // windows requires __declspec(dllexport) to be used to // declare public symbols extern "C" __declspec(dllexport) char *merge(int n, char *v[]) { static char buf[100]; *buf=0; for(int i=0;i<n;i++) { strcat(buf,v[i]); } return buf; } DM code to use test.dll: mob/verb/test() usr << call("test.dll","merge")("fee","fi","foe") As with the other call() versions, arglist() may be used to do runtime arguments: mob/verb/argtest() var/L = list("fee","fi","foe") usr << call("test.dll","func")(arglist(L)) As the library prototype is char**, the call() arguments must be strings. Other types (like numbers) will be passed as the empty string ("") into the library function.

412 Release Notes | View All