Reporting bugs with the PSO server

[Radkin]

I've noticed the past few months when you're typing to someone not all the letters appear.

[pcwzrd13]

Do you mean the battle quests aren't working, or all quests?

I believe none of the quests are working. I only tried one, Endless Nightmare 2 (v2) , but Aleron Ives mentioned that none of them were working on VEGA. This was the Saturday before last BTW.

[brourke228]

I've noticed the past few months when you're typing to someone not all the letters appear.

Is that only happening on Vega or all the ships?

Do you mean the battle quests aren't working, or all quests?

I believe none of the quests are working. I only tried one, Endless Nightmare 2 (v2) , but Aleron Ives mentioned that none of them were working on VEGA. This was the Saturday before last BTW.

Ok I'll look into this.


Thanks for reporting this. We updated our version of sylverant at the end of last month for the first time in awhile and also did a server overhaul a couple months prior to that, so there could be some issues.

[Aleron Ives]

The fixed Battle quests are definitely not up, as Battle 1 still crashes cross platform. The quest descriptions might also be linked to the wrong quests. I wasn't leading at the time, so I can't be sure, but the leader was having trouble finding the right rule. He selected the quest with the description to Battle 6, and we ended up playing Battle 1, instead. I think DC Live was going on at the same time we tried this, and everyone in that team got disconnected when trying to start a quest.

[BlueCrab]

I've noticed the past few months when you're typing to someone not all the letters appear.

Is that only happening on Vega or all the ships?

I'd be interested in knowing that too, as I know I haven't touched any code relating to sending messages lately.

[Radkin]

No idea. I only play on Vega. I know myself, Dobbs, my brother and my boyfriend all have this issue though. When I get home after work I will log onto the other servers and test this out. I'll let you know by the end of tonight.

[BlueCrab]

No idea. I only play on Vega. I know myself, Dobbs, my brother and my boyfriend all have this issue though. When I get home after work I will log onto the other servers and test this out. I'll let you know by the end of tonight.

Is it a client-side issue (i.e, are the characters just not showing up when you type them -- before you send the message), or is it a server-side issue (the characters show up but when you send the message they don't show up in the bubble).

Also, what version of the game are we talking about?

[brourke228]

Pcwzrd, does the error you're getting occur only when you're in a party? I just tried loading Endless Nightmare 2 on psov2 three times and had no issues. I tried twice on normal mode and once on ultimate not that it should matter. If you are getting the error regardless can you tell me which method you are using to connect.

The new battle quests might not be up yet, Impulse was going to set that up because I'm not sure how to convert the quest files to dat/bin format. I'll check into the battle quest descriptions, I need another DC player to test that though.

[BlueCrab]

The new battle quests might not be up yet, Impulse was going to set that up because I'm not sure how to convert the quest files to dat/bin format. I'll check into the battle quest descriptions, I need another DC player to test that though.

You don't need to convert them at all. You can mix and match the different types in the config. There's a flag on each quest for what format it is in. Not to mention that .qst is a bit less work on the server to deal with.

[pcwzrd13]

Pcwzrd, does the error you're getting occur only when you're in a party? I just tried loading Endless Nightmare 2 on psov2 three times and had no issues. I tried twice on normal mode and once on ultimate not that it should matter. If you are getting the error regardless can you tell me which method you are using to connect.

I don't know. I'm currently away from home and can't test it but I know LukeAkAscooter had the same issue last Saturday. See his post here (sixth post down).