Yeah, as Decicus mentioned (and I forgot), the links on there are for SVN downloading of our git repository- the link to Github itself is shown in the text underneath it.
So, I have quite a few troubleshooting steps you can try and answer to make sure I understand the problem fully: (reaally wish I had my computer set up at home lol)
1) While your server is running normally (and the motd works):
1a. Enter "ulx showMotd" in BOTH your client and server consoles. These *should* display the correct URL, and should be the same on both.
1b. What does the "ulx showMotd" line look like in your server's config.txt file?
1c. Does the motd work when you say "!motd"?
1d. Does the motd display when you join your server with at least one other player on?
1e. Does the motd display when you join your server as the first player? (Possibly irrelevant, nice to have the info just in case).
2) After a server stop/restart/crash, before setting the MOTD parameter again:
2a. Did the default MOTD show up on join?
2b. Enter "ulx showMotd" in BOTH your client and server consoles, and compare the values.
2c. Does the default MOTD still show if you say "!motd" (after waiting a minute or so)?
2d. What does the "ulx showMotd" line look like in your server's config.txt file? Is it the same as before?
2e. If 2d is the correct URL, does the regular MOTD show up after rejoining, or after a mapchange?
3) Change the MOTD value to "
www.google.com".
3a. Check the "ulx showMotd" value in your server's config.txt file. Was it properly changed to "
www.google.com"?
3b. Does the MOTD properly show Google when saying "!motd", even after rejoining?
4) (Optional) Turn off the server.
4a. Check the server's config.txt file for the MOTD value to see if it saved.
4b. After enabling the server, does the MOTD value change once the server has started?
Hopefully that will help us to pinpoint where exactly the problem is occurring.
If you have lots of free time and want to help us determine which exact commit caused the issue,
check our commit log here.If you're absolutely sure that the 3.61 Release version worked fine, then any commits ON OR AFTER Aug 31, 2014 may have caused the issue. Reverting to a specific commit can be done via SVN revisions, but it's a tidbit tricky to tie specific git commits with a SVN revision Github created. (TortoiseSVN's show log feature should help). Looking briefly at the commits myself, I can't see anything that stands out as being the culprit. But, you can always do the binary search method of finding the problem- start halfway between the earliest and the latest commit, see if it works, then jump either ahead or behind by half the remaining commits to start narrowing it down.
Hope this is helpful!