Page 2 of 3

Re: Uaseco : Unsupported Modescript

Posted: 15 May 2017, 17:52
by flood
pmed both files

Re: Uaseco : Unsupported Modescript

Posted: 15 May 2017, 18:10
by undef.de
I have checked both files and they seems to be in sync. The only thing I have to ask: Does the dedicated server really use that "dedicated_canyon.default.txt" file? Otherwise I'm out off ideas, sorry. :?

Re: Uaseco : Unsupported Modescript

Posted: 15 May 2017, 18:23
by flood
yep it does ahahaha.

Re: Uaseco : Unsupported Modescript

Posted: 15 May 2017, 18:26
by undef.de
flood wrote: 15 May 2017, 18:23 yep it does ahahaha.
Does that mean we found the problem or just "Yes, the dedicated is using that file"?

Re: Uaseco : Unsupported Modescript

Posted: 15 May 2017, 19:51
by flood
The dedicated uses that file. I double checked if the ports are forwarded and they are. It still doesnt run tho.

Re: Uaseco : Unsupported Modescript

Posted: 15 May 2017, 20:05
by undef.de
Well as I said, I'm out of suggesstions here, that never happend to me. Any many other UASECO installations are running fine. :?

The only thing you can try: Start from beginning with the minimal setup and don't reuse files. If that runs, you can try to replace the files and see what happens.

Re: Uaseco : Unsupported Modescript

Posted: 15 May 2017, 20:27
by flood
I think it has to do with the preset for time attack etc. I also have a nc1 hosted server but it also cant start and doesnt show a log file. I will also poke around in there.

Re: Uaseco : Unsupported Modescript

Posted: 15 May 2017, 21:22
by flood
update: just got home and it suddenly worked after i rebooted my pc. so that part magically got fixed by a reboot lel. next issue Uaseco shuts down because there is no dedimania connection.
edit:
after filling in a singel random number in the dedimania generated code it skipped the process and booted normally.

Re: Uaseco : Unsupported Modescript

Posted: 15 May 2017, 21:29
by undef.de

Re: Uaseco : Unsupported Modescript

Posted: 15 May 2017, 21:37
by flood
yeah i know thats why i needed to get past the check, but got that worked out. now i have a controller working. but it doesnt take commands? even /help doesn't work.

Code: Select all

Fatal error: Maximum execution time of 120 seconds exceeded in C:\Maniaplanetserver\uaseco\includes\core\webrequest.class.php on line 432
[PHP Fatal Error] Maximum execution time of 120 seconds exceeded on line 432 in file C:\Maniaplanetserver\uaseco\includes\core\webrequest.class.php
Press any key to continue . . .
i now get this error