Author Topic: AoC bot issue with parsing text after Funcom patch 1.04.6 (Read 5097 times)

Organizer · « **on:** March 31, 2009, 02:06:17 pm »

I just noticed that our bot is messing something up after todays patch. Basically we use a guides.php module share here at one point to read .txt files and show them in-game.

This have worked fine forever, and I believe it uses Bebots built in-code to do the job, but I might be wrong, though I can't see any code in the file that would do it directly.

In any case the patch today should just have been some DX10 and exploit fixes, so that something like this suddenly don't work is suspect as no changes has been done to the bot, why it is done and if its a deliberate change or bug is also unknown.

The bot in essence do no longer parse line breaks in the .txt files, so all the content shows as one big bunch of text now without breaks. If the .txt file got a forced it works as normal.

Some members also think he noticed that the whole log-on member message spam changed. It is now all blue except text for the charver level being in another cyan blue. And I guess he might be right, as I think there used to be another colour as well to better split the different parts aside, if so again it is likely linked to whatever goes wrong with some html code in the parser (presuming its called that).

Hope I have managed to at least explain the issue reasonably enough, as done in a hurry from work atm

Maybe someone else can confirm as well?

Organizer

Monk4y · « **Reply #1 on:** March 31, 2009, 06:29:47 pm »

I have the problem with scripts not being parsed correctly as well. works to move to the next line but does not give you a gap in the text as it should. in php modules the \n\n does not dive you a gap like it used to it only drops dow to the next text line.

its all very annoying.

I didnt notice any changes in colour yet though.

Organizer · « **Reply #2 on:** March 31, 2009, 07:48:34 pm »

Yeah, maybe I am dreaming with the logon spam msg color, hehe. In any case something happened, would be nice to figure out what as if not I need to change the formatting of all the text files we got...

Organizer · « **Reply #3 on:** April 02, 2009, 02:10:06 am »

I guess its just impatience but presuming all bebot versions are affected it would be nice to know if its possible to do workaround or if we need to wait for Funcom (and report it to them) to make this issue go away. Temar, Alreadythere? pleeeease

Rekkx · « **Reply #4 on:** April 02, 2009, 01:18:13 pm »

I noticed this also.

For my scripts, I included something like:

Code: [Select]

."\n   \n".
to get my line break.... dirty hack, but works for now.

Alreadythere · « **Reply #5 on:** April 02, 2009, 05:35:02 pm »

What's the actual problem? Are only line-breaks read from file no longer working correctly, while \n as well as do still work correctly? Or is only still working?

On a side note, FC usually doesn't announce changes to the chat server.

Rekkx · « **Reply #6 on:** April 02, 2009, 06:21:23 pm »

The problem is lying with multiple or \n tags together not creating the extra line.

 or \n\n do not line feed and then line feed again right now.

The non breaking space between the or \n however works at the present time.

Organizer · « **Reply #7 on:** April 02, 2009, 08:22:32 pm »

As Rekkx says, multiple \n and tags create only one line break even if there are two or more. In addition any module reading .txt files (like the guides module) that normally read this files and require neither nor \p tags gets output as one big chunk of text...

If you need any more info let us know, happy to test and get this resolved somehow as it destroy layout of tons of output.

Alreadythere · « **Reply #8 on:** April 04, 2009, 06:56:46 pm »

Quote from: Rekkx on April 02, 2009, 01:18:13 pm

Code: [Select]
."\n   \n".

Does this work? Putting a   before every \n and would be pretty easy to accomplish. And it shouldn't influence the look of the output in any noticeable way.

Solldara · « **Reply #9 on:** April 05, 2009, 09:28:17 am »

Mine are mushed too

Which bearing in mind that we use over 60 guides and use the guides to do the updated raid lists (7 per week) this is a real pain.

A manual solution is to put at the end of each text line, as others have already said does not work so at the moment I've simply used a full stop as text ie

fvujfvfvjufv 
. 
fhjfhfuffgfg 

which displays correctly.

Incidently the guides list which lists all the text files with links has also got the same problem - which again can be solved atm by using the fix.

It would be really nice to know if this will resolve itself or whether I will have to manually update all the guides - pasting doesn't take too long for 1 guide - but for 60.......

Organizer · « **Reply #10 on:** April 06, 2009, 03:19:22 pm »

Quote from: Alreadythere on April 04, 2009, 06:56:46 pm

Quote from: Rekkx on April 02, 2009, 01:18:13 pm
Code: [Select]
."\n   \n".
Does this work? Putting a   before every \n and would be pretty easy to accomplish. And it shouldn't influence the look of the output in any noticeable way.

Unless I'm crazy, could happen,   and likely \n   \n should work indeed (edited first response)