Quote:
Originally Posted by Uleat
From what I can see, you're dealing with 2 possible issues - and possibly suffering dilemmas from a cross between the two.
First is custom items.
Items are very finicky if you don't know exactly what the field data represent and how the data is used.
- `fvnodrop` always causes the client to crash
- non-existent charm files cause the server to crash
Second is level.
When SoF support was added to the server, the max supported level was 65.
While people have pushed that higher themselves, and now that we support a higher level by default, that doesn't mean that
older clients are 'handled' correctly. Unless an issue is obvious(, or reported with enough info to find the cause,) older clients
tend to suffer...
I played using SoF last night on a human monk. I started in tutorialb and went to crescent afterwards (by way of poknowledge.)
I managed to get to level 18 without any issues.
On keeping your custom items, it's not hard to export them.
The actual issue may not be either of these..just a guess based on behavior.
I, personally, would like to see 1-2 of the clients be dropped from support..but, as long as we do support them,
they need to be functional.
|
Hi Uleat,
I just verified that the items I custom made don't have the FVNODROP flag enabled, and none of them are charms (I haven't made any of them yet), so I am definitely leaning towards that not being the issue;
I had also wondered about the level thing, but not in the sense of the level cap; just with being over leveled for a level capped zone; but in the instance of what appears to be happening right now my theory doesn't even hold up, since the character that started having the issues hadn't level up any more than 1 level by using the gm command.
As for the client support, I completely understand what you are saying; but I also hope that if there is clients that get dropped, that some way is made for people to still run their own servers, or logon to other peoples servers; especially since the only versions that are still technically available are the legacy clients (Titanium, SoF
Looking at the server having the issues, Im noticing that sometime in the night, the queryserver lost connection to the database on the local machine; I have seen that happen only ever twice but am not sure why.
In the meantime, I am going to take that server down, back up its database and then run the updates for it.
If you think of anything else I can try, please let me know.
Also; I installed a fresh database on another computer, and it is having issues letting me connect to it across the local network. I am going to keep fighting with it and let you guys know the results of attempting NightStriders
suggestion