R21 Patch server issues.

[Specialist]

FYI, it looks like the YELL option is working now.

[marrr]

marrr, we'll update it early tomorrow morning. It's too late in the day to do a non-emergency global update today. R22 does not revert the official server change.

Agreed. Thanks for the update.

[Edge100x]

FYI, it looks like the YELL option is working now.

It seems to mostly work but I have heard a complaint that it may crash the server, so be careful. (I do not know if the complaint is substantiated; the crash may have been unrelated.)

[Clumppy]

Weird thing with the /yell command is if you use it the stupid thing is stuck on your screen until a new map is done.

[marrr]

Weird thing with the /yell command is if you use it the stupid thing is stuck on your screen until a new map is done.

Thats because the ingame admin plugin needs to be updated. I think if u send another yell via procon it will clear it out. This post lets you know how to fix it.
https://forum.myrcon.com/showthread.php ... #post94639

[Edge100x]

This shouldn't affect the NFO admin daemon (which offers !yell as a command and also allows it to be used for server messages), as it is designed to handle it as with BF3, and BF3 uses a second count instead of millisecond count.

[markym]

I can confirm the Yell command gets stuck on the screen and doesn't got away unless the game issues a message center screen like "last man in squad" ..I'm running the admin dameon from NFO

John ...I think the command might need a time limit in the code ...I recall seeing something on that where the yell command needed to include a time to display???

[Cris]

Anyone getting this error after committing changes on your server?

"The command vars.vehicleSpawnDelay could not be executed on the server. It returned: 'ExecutedOnNextRound"

[Edge100x]

I can confirm the Yell command gets stuck on the screen and doesn't got away unless the game issues a message center screen like "last man in squad" ..I'm running the admin dameon from NFO

John ...I think the command might need a time limit in the code ...I recall seeing something on that where the yell command needed to include a time to display???

We do specify a time for it to stay on the screen (in seconds). I haven't seen documentation on the new version of the command, but it works in BF3. I will have to check into it further.

[markym]

I can confirm the Yell command gets stuck on the screen and doesn't got away unless the game issues a message center screen like "last man in squad" ..I'm running the admin dameon from NFO

John ...I think the command might need a time limit in the code ...I recall seeing something on that where the yell command needed to include a time to display???

We do specify a time for it to stay on the screen (in seconds). I haven't seen documentation on the new version of the command, but it works in BF3. I will have to check into it further.

Thank you sir -- I sent some info to Andrew this morning -- the default according to older documentation is supposed to be on screen display for 10 seconds. I tested it out this morning and it's still locking the yell message center screen -- default timer does not appear to be working so the message just locks center screen and only clears when another center screen message appears. They need to fix this pronto as it's annoying as heck big yellow message center of the screen all the time. I can't believe they didn't test this before pushing it out. Oh wait, yes I can believe it considering they didn't test half the game before they issued it!

[wihgaming]

are you by chance using @yell via Procon in-game admin commands?

[XDE4TH]

I can confirm the Yell command gets stuck on the screen and doesn't got away unless the game issues a message center screen like "last man in squad" ..I'm running the admin dameon from NFO

John ...I think the command might need a time limit in the code ...I recall seeing something on that where the yell command needed to include a time to display???

You can fix the in game admin plugin from Procon(myrcon) by editing the files manually. [HERE] is a thread at myrcon forums from the developer on how to fix this. Other plugins might still need to be updated/fixed individually.

[fantasygirl]

I'm still taken back by everyone who is upset that this is going on. It was known from the beginning that they wanted official servers to be run a certain way.

Why are people surprised by this?

Trust me I'm on the side of "let admins run their servers the way they want" and always have been and it sucks that we don't get people joining the servers through the play now or whatever the heck it is. BUT I also said from the beginning that they will want official servers run how they want them. And that's exactly why I'm not running any.

It's completely frustrating that they are doing "Official" Servers, but nothing has changed from release. We all knew they wanted them run how they wanted. We should focus on asking for them to send people to non official servers instead of trying to change official servers to how we want them to be run.

I agree with this 100%. We all knew from the get go that there was to be NO control with official settings. They have always said this and I'm not even sure why anyone who is going to pay for a server would want no control over their own server. Its why I've always went with ranked despite how hard it was to get going.

[FAST]

This link that was provided
https://forum.myrcon.com/showthread.php ... #post94639

Does that fix the yell issue with NFO server messages? I don't think it does but you never know.


Thanks

[Rogerdoger45]

Anyone getting this error after committing changes on your server?

"The command vars.vehicleSpawnDelay could not be executed on the server. It returned: 'ExecutedOnNextRound"

I am getting these errors.