[Plugin] ManiaLive->Xaseco->ManiaLive freezone fix 0.34

[weerwolf]

Using ManiaLive and Xaseco at the same time breaks the freezone plugin (you can chat in forced spec)
This plugin is to prevent that problem.

Is it? I see plenty of servers with xaseco and this plugin, but still able to chat during spec.......
You know i feel about diabled chat but nevertheless ......

EDIT: I started manialive, started xaseco. When i was put to spec i was abel to chat.
Killed xaseco, killed manialive, restarted manialive only.
Next forced spec ia was still able to chat - no xaseco started.

[Knutselmaaster]

Yes, if you play on a "errored" server, it can happen that the next server you visit (or you fix that server) seems errored too.
Somehow there is something that is left over in your game client.
Try leaving and rejoining the server, this mostly resolves it, or restart the game.

Edit;
It is like when you stop a controller, and the manialinks (like widgets etc) will still stay on screen....

[w1lla]

In manialive when you kill and restart it. The widgets are still shown...

In xaseco the same but it still has everything enabled. So you first might need to start xaseco and then manialive to resort out the problems.

[Faster10x]

Hi All ! When a player connect to my server, my Aseco.bat didn't tell me disable chat for...

This is my plugins.xml:

Code: Select all

<?xml version="1.0" encoding="utf-8" ?>
<aseco_plugins>
	<plugin>plugin.localdatabase.php</plugin>
	<plugin>plugin.rounds.php</plugin>
	<plugin>chat.admin.php</plugin>
	<plugin>chat.help.php</plugin>
	<plugin>chat.records.php</plugin>
	<plugin>chat.records2.php</plugin>
	<plugin>chat.recrels.php</plugin>
	<plugin>chat.dedimania.php</plugin>
	<plugin>chat.players.php</plugin>
	<plugin>chat.players2.php</plugin>
	<plugin>chat.wins.php</plugin>
	<plugin>chat.laston.php</plugin>
	<plugin>chat.stats.php</plugin>
	<plugin>chat.server.php</plugin>
	<plugin>chat.songmod.php</plugin>
	<plugin>chat.me.php</plugin>
<!--	<plugin>plugin.muting.php</plugin> -->
	<plugin>plugin.tmxinfo.php</plugin>
	<plugin>plugin.track.php</plugin>
	<plugin>plugin.checkpoints.php</plugin>
	<plugin>plugin.dedimania.php</plugin>
	<plugin>plugin.rasp.php</plugin>
	<plugin>plugin.rasp_jukebox.php</plugin>
	<plugin>plugin.rasp_chat.php</plugin>
<!--	<plugin>plugin.rasp_karma.php</plugin> -->
	<plugin>plugin.rasp_nextmap.php</plugin>
	<plugin>plugin.rasp_nextrank.php</plugin>
	<plugin>plugin.rasp_votes.php</plugin>
	<plugin>plugin.chatlog.php</plugin>
<!--	<plugin>plugin.msglog.php</plugin> -->
	<plugin>plugin.style.php</plugin>
	<plugin>plugin.panels.php</plugin>
	<plugin>plugin.donate.php</plugin> 
	<plugin>plugin.musicserver.php</plugin> 
	<plugin>plugin.uptodate.php</plugin>
<!--	<plugin>plugin.rpoints.php</plugin> -->
<!--    <plugin>plugin.autotime.php</plugin> -->
<!--	<plugin>plugin.access.php</plugin> -->
	<plugin>jfreu.plugin.php</plugin>
<!--	<plugin>mistral.idlekick.php</plugin> -->
<!--	<plugin>plugin.fufi.widgets.php</plugin> -->
	<plugin>plugin.fufi.menu.php</plugin>
	<plugin>plugin.info_widget.php</plugin>
	<plugin>plugin.forceMods.php</plugin>
	<plugin>plugin.lotto.php</plugin>
	<plugin>plugin.bestcps.php</plugin>
	<plugin>plugin.records_eyepiece.php</plugin>
	<plugin>plugin.tm-karma-dot-com.php</plugin>
	<plugin>plugin.alternate_scoretable.php</plugin>
	<plugin>plugin.xrestart.php</plugin>
	<plugin>plugin.fufi.autoqueue.php</plugin>
    <plugin>plugin.MLintegration.php</plugin>
</aseco_plugins>

This is my config.ini:

Code: Select all

;------------------ 
; Plugins 
;------------------ 

; Add plugins to load. 
; plugins.load[] = 'Author\PluginName' 

plugins.load[] = 'Reaby\XasecoIntegration'
plugins.load[] = 'Freezone\Freezone'
 
plugins.Freezone\Freezone.wsPassword = '******'

[weerwolf]

Yes, if you play on a "errored" server, it can happen that the next server you visit (or you fix that server) seems errored too.
Somehow there is something that is left over in your game client.
Try leaving and rejoining the server, this mostly resolves it, or restart the game.

Edit;
It is like when you stop a controller, and the manialinks (like widgets etc) will still stay on screen....

Conclusion: either this plugin can only be used in testmode until its working 100%, or stop deactivating servers on chat rules bases until the plugin is finished i would say.

[Knutselmaaster]

Well, the problem only occurs when combining controllers, which is not supported by any means.
So i cannot agree with you.
Running only manialive with freezone plugin works perfectly as it should.

[weerwolf]

Well, the problem only occurs when combining controllers, which is not supported by any means.
So i cannot agree with you.
Running only manialive with freezone plugin works perfectly as it should.

You did not read my text well, that what i said. So if rules are not flexible, shoot down any freezone server you encounter with xaseco, cause they do not meet they requirements.
And that are a lot!

[Knutselmaaster]

This plugin is made by a member of the community, so if it doesn't work well in all cases, it is up to the serveradmins to try to get it to work well.
Nadeo has no responsability for it at all.

The rules are flexible enough, servers with the xaseco-mnialive combi do not react the same, but there are many of them that do meet requirements anyway.
Almost all servers that i have disabled because of conflicts between manialive and xaseco, that broke the chat rules, are now reenabled, mostly running xaseco and manialive again, and perfectly according to the rules.
And that is not one or two servers, i'm talking about at least 50 servers already.
So it is possible.
Serveradmins that don't want to (or simply cannot) invest time into making both work together, should just stick at running manialive without another controller, or stop running freezone.

[tmdunhill]

Hello,

Conducted integration and manialive Xaseco and left running on a test server and have not had problems, you could access the server and, if approved, give ok?

If you can access, follow the login server: tmtp: / / # join = fabiohamza2.

If the server does not conform to the rules, I will return erform of configurations.

Thanks.

Greetings.

Dunhill

[Paris]

i see that you are using records_eyepiece plugin, to solve your problem edit records_eyepiece.php here:
find

Code: Select all

$xml .= getCustomUIBlock();

and change to

Code: Select all

//$xml .= getCustomUIBlock();

it should work

it helps in my case, thank you.....