UASECO 0.9.4 (2017-05-30) released

[undef.de]

salut
????????

Code: Select all

CHAT_PREFIX_REPLACEMENT on line 1265 in file /home/mania5/uasecofscanyon3/includes/core/helper.class.php

At the line 1265 there is nothing that could give that error... wrong copy?

Anyway, see changelog from 0.9.4:
* Added `<messages><chat_prefix_replacement>` in `newinstall/config/UASECO.xml`

[SSM.Speed...]

salut
????????

Code: Select all

CHAT_PREFIX_REPLACEMENT on line 1265 in file /home/mania5/uasecofscanyon3/includes/core/helper.class.php

At the line 1265 there is nothing that could give that error... wrong copy?

Anyway, see changelog from 0.9.4:
* Added `<messages><chat_prefix_replacement>` in `newinstall/config/UASECO.xml`

salut

merci

[rasmusdk]

At every Map change I get 1 notice and 1 warning. (server runs fine)
What could be the cause?
I think it has been in all Uaseco versions. (Current Github095)

Code: Select all

[2017-06-02 19:38:48] [Event] Loading Map
[2017-06-02 19:38:48] [LocalRecords] Current record on Map [The Chosen] is [0:36.408] and held by Player [rasmusdk]
[u][b][PHP Notice] Undefined index: message_new on line 125 in file H:\TM2Server\_uaseco\includes\core\locales.class.php[/b][/u]
[2017-06-02 19:38:49] [AutoTime] Setting new timelimit for Map [The Chosen] to [4:40], based upon gold time [0:37.098]
[u][b][PHP Warning] Invalid argument supplied for foreach() on line 180 in file H:\TM2Server\_uaseco\includes\core\message.class.php[/b][/u]
[2017-06-02 19:38:49] [Event] Begin Map

[undef.de]

At every Map change I get 1 notice and 1 warning. (server runs fine)
What could be the cause?

Could be the plugin/plugin.autotime.php and related locales/plugin.autotime.xml which are up-to-date at github, but maybe not at your install.

[rasmusdk]

Every thing is uptodate from Github 2017-06-01

But then i think it is this:

.......
</plugin_description>
<!--
<message_default>
.......
</message_maximum>
//-->
</locales>

('<display>0</display>' in autotime.xml do not work)

Thanks for help!

[Flighthigh]

At the 0.9.4 there is not adminpanel if i join the Server. In the chat "/admin panel 10" gives an Error with: No valid admin panel file.

Then i write "/admin panel list" and i got the list. Then i can click the 10 and the panel is there.
The same is if i wrote after the list in the Chat "/admin pane 10". Then comes the panel too.

Why it isnt possible that the panel is there if i join the server?

Is "10" an name of a panel or the index of a panel?

If you change your AdminPanel then this will be stored into the database, but only if you don't kill UASECO. You have to do a clean shutdown: "/admin shutdown", that will store the settings into the database.

Im sorry but a /admin shutdown has no effect. If i make this at the next Start of Uaseco it doesnt show the adminpanel.

Yes the 10 is a index for "RightCorner".

At the 0.9.3 i make only the cahtcommand "/admin panel 10" then the panel was there. At the 0.9.4 the only way is at first the Chat comm "/admin panel list" and then a click on the RightCorner or the chatcomm "/admin panel 10" or the chatcomm "/admin panel RightCorner". If i go out and come into the server the panel ist away. /admin shutdown has no effect.

[endbase]

Any body else got the problem that after a while the controller takes 2 minutes to load on the server ? (fresh install does not even work)

after every race i Get some errors

ps restart seems to work for an while. and here is my log file http://www.mediafire.com/file/i9wj68ovboydpyp/tm.zip

Greetz Base

[undef.de]

Every thing is uptodate from Github 2017-06-01

But then i think it is this:
</plugin_description>
<!--
<message_default>

</message_maximum>
//-->
</locales>

('<display>0</display>' in autotime.xml do not work)

The version on github is 8 month old and there is nothing commented, except the version comments.

Any body else got the problem that after a while the controller takes 2 minutes to load on the server ? (fresh install does not even work)

after every race i Get some errors

ps restart seems to work for an while. and here is my log file http://www.mediafire.com/file/i9wj68ovboydpyp/tm.zip

Yes, it was a mem leak, fixed at github:

Fixed a mem leak: placed wrong the mem freeing function of a sql resource at includes/core/player.class.php and includes/core/playerlist.class.php (maybe related to speedychris report)

And the other log entries has been fixed too.

[rasmusdk]

Every thing is uptodate from Github 2017-06-01

But then i think it is this:
</plugin_description>
<!--
<message_default>

</message_maximum>
//-->
</locales>

('<display>0</display>' in autotime.xml do not work)

The version on github is 8 month old and there is nothing commented, except the version comments.

I'm trying with a better explanation. ...

My point is:
'<Display>0</display>' in config\autotime.xml do not work. Messages are still in the chat. (Like '<display>1</display>')

Therefore I have added '<!--' and '//-->' to 'locales\plugin.autotime.xml' (which makes notice and warning in my logfile)

[undef.de]

At the 0.9.3 i make only the chat command "/admin panel 10" then the panel was there. At the 0.9.4 the only way is at first the chat command "/admin panel list" and then a click on the RightCorner or the chat command "/admin panel 10" or the chat command "/admin panel RightCorner". If i go out and come into the server the panel ist away. /admin shutdown has no effect.

A chat command "/admin panel 10" without a before "/admin panel list" can't work, because the list in where you can "jump" with "/admin panel 10" does not exists, only "/admin panel list" is building it. The function that handles it hasn't be changed since 0.9.0.

And to save the settings into the database you have to leave the server. I was thinking that "/admin shutdown" stores the data, but that wasn't the case... but now.

My point is:
'<Display>0</display>' in config\autotime.xml do not work. Messages are still in the chat. (Like '<display>1</display>')

Therefore I have added '<!--' and '//-->' to 'locales\plugin.autotime.xml' (which makes notice and warning in my logfile)

Ah... fixed.