This release brings a lot of simplifications. The scripts
are now part of SunUO, which means that the RunUO binary
distribution isn't required anymore. This allowed me to fix
a lot of script bugs. download

2006/08/24

Defiance now powered by SunUO

Yesterday, a long evaluation period at the Defiance headquarters
ended. The biggest european freeshard switched over to
SunUO!

The switch required only one simple change to the shard:
run SunUO.exe instead of RunUO's old Server.exe.

It looks like SunUO manages the same shard with 30% less
memory, and world load/save have been accelerated by a few
seconds. Plus, SunUO offers portability on both Windows x64
(.NET 2.0) and Unix (Mono).

2006/02/09

DoS by the RunUO team

This night, the RunUO team unsuccessfully tried to perform a
Denial of Service attack on the SunUO server. The attacks
came from 67.15.136.5, which happens to be www.runuo.com.
How childish. Background
information here and here.

I have published my RunUO 1.0.0 exploit, it's written in C
and runs on Linux. Get the source
here.

2005/11/29

SunUO 0.2.0

The new SunUO version 0.2.0 is released! There are two
important reasons for upgrading: first, this release fixes a
serious
remote vulnerability present in RunUO 1.0.0, though
SunUO caught these attacks with its exception handlers
(which were insulted by many in the past) - this release
brings a "real" fix. Second, version 0.2.0 supports encrypted
clients (thanks to Sebastian Hartte).

2005/09/29

about RunUO forks

I'd like to respond to news on runuo.com, but unfortunately,
I am perma-banned on their website.

"The entire rationale of releasing RunUO
as an open source project was to allow people to fork the
core" - funny, I remember how they attacked me for
forking RunUO, how I was insulted by RunUO team members
(they censored the forum thread meanwhile)

"[...] forks of The RunUO project like to
attack the RunUO team as if we have done something wrong to
them" - in the SunUO case, I wanted to submit patches
instead of forking, but I was insulted and kicked from their
servers. How is this not wrong?

"The problem we have is with people who
make-believe they are superior to us because they modify a
few lines of the core" - wrong, not the people
(including me) are superior, but the modified code is - of
course, in my opinion, SunUO is superior to RunUO. If I
didn't think that, the SunUO project would be pointless.
For what reason should I fork an existing project, if not
for improving it? Improving naturally leads to a "superior"
product. I fail to understand how this is a problem for
Ryan.

SunUO makes script compilation optional; a fresh install
starts in about 3 seconds, including world load

SunUO supports multiple script libraries; this helps keeping
tidiness

SunUO introduces a configuration file; having to edit source
code to configure a shard sucks (ever upgraded to a new RunUO
version? Then you know what I mean)

SunUO is not vulnerable to the directory
entry order faction bug, which may break all
faction memberships and town ownerships in some cases. The
RunUO team refuses to accept this as a bug, stating that
.NET automatically sorts directory entries (which is plain
wrong).

Most of RunUO's design flaws are deep
within the Scripts directory. The scripts are not free software,
therefore I cannot provide corrected versions. I am trying hard
to keep compatibility with these flawed scripts, while improving
the core.

RUOSI cooperation

I have recently joined to RUOSI team (formerly known as
RunUO Russian Edition). They are a group of nice Russians who
made the first RunUO fork ever, and they integrated Samurai
Empire support (and more). All SunUO improvements have been
merged to RUOSI.

The SunUO project will be continued; it will stay for people who
prefer a RunUO clone which stays closer to the original code
base, for people who who want a stable RunUO replacement, and
nothing more. SunUO will stay in sync with future RunUO
releases.