Post: #15

Crashes are usually caused by poorly written scripts in sphere. But only crash i get without writing any script is network threads. It is pretty buggy, someone has written and put it in sources like a spaghetti code. Till that time, I had no crashes except infinite loops caused by me.

Sphereserver doesn't need advertisement, almost everyone in uo knows sphere. There are billions of platforms for it. but as i know in my country, nobody uses last nightly builds. Because they are nightly builds, so simple. almost until 5 years ago, everyone was using 0.55i in turkey. Because it was simply stable. the people i know, ran 100-150 player shards with 2009 release.

Devs usually want us to code our own features but It is not "healthy" to code vital, core things using sphere scripting. Because it is not something compiled to binary, it is simply interpreted by sphereserver. That's why i always report those. For example, osi-like stamina check system. I had created an item with timerd=1 to make it a global timer, so every second, every player is checked 10 times. It is not something wise to do with sphere scripting. Another example that I wanted to code osi-like item stack system. But hardcoded LOS checks blocked me in @dropon, @pickup triggers, i directly edited drop pickup packets but that really costed so expensive in performance. Another example, I tried to code custom Notoriety flags. But we can't override them. I wanted some people to be seen "orange". Yeah I would make those people join some enemy guilds but what about other players ? Not wise. Another example, I wanted to make osi-like criminal system. "Attacking is a crime". I personally suggested this to shiryux, and he added, thanks to him. But It has magically disappeared in some builds ?! I don't want to code this with sphere scripting because there may be some hardcoded checks, memory flags etc. I didn't want to deal with bugs. Another, still present bug is Walkcheck code. You can get stuck in shores or can't pass many areas in t2a lands, which are normally past. Since we can't code a walkcheck system..

It is always to make core things in binary. Emulators usually provide options for it, I mean sphere.ini. Because you can't compile your sphere scripts, unlike in c# - runuo. If you can't, then it is wiser to add things internally then provide options for it. Scripting is only needed when the system is too much flexible that you can't provide options for each, like guildstone system.


----

I once wanted to help fixing those things 2 years ago, by sending developer application. Because i had adressed many bug fixes using my old 0.99f sphere sources, which still present. so i thought i could fix them easily. I was accepted but i was 16 and couldn't sign that thing, so shiryux was accepted, thanks to god someone was finally hired to development staff after years. I am now on my "legal" age and I can sign that contract but development staff doesn't seem to have empty slot. poor luck I will send application again as soon as there is an empty slot. Even i criticize many things, Sphereserver is vital for my programming education like every uo emulators are, for me.