Paltalk Bot

Viewing 15 posts - 61 through 75 (of 120 total)
  • Author
    Posts
  • #31204
    NVYE
    Administrator

    very good 🙂 I like that

    #31205
    Locohacker
    Administrator

    @usenet7 wrote:

    @autopilot wrote:

    @DoubleM wrote:

    the auto-redot-ing is not working anymore. I always get the nick not found message. Any thoughts on how to fix it? I believe that happened after updating my paltalk to the latest build

    Most likely reason is the name change of the syslistview control.

    I changed

    <code>    Public ReadOnly Property NicListClass() As String<br />
    Get<br />
    Return "ATL:00A2DFF0" 'fomerly "SysListView32" in 10.2<br />
    End Get<br />
    End Property</code>

    and it worked after that.

    Yeps that works 🙂 the bad news is that paltalk always changes that with every new Build 🙁
    And did they change the way they send whispers? cause with the /w command everyone can see it 😆
    here the updated version

    #31259
    Chike
    Administrator

    The /w does not work on build 474 as well this would require a seriouse ***k 🙂

    And what about users that do not want to use this s***y paltalk version and don’t have the old bot?

    #31260
    kane05
    Member

    loco it wont respnd to cammands in the room it wont bounce and wont red dot still

    #31258
    kane05
    Member

    ok i got it to respond to commands but auto red dot and auto bounce do not work at all

    #31242
    Chike
    Administrator

    @locohacker wrote:

    Yeps that works 🙂 the bad news is that paltalk always changes that with every new Build 🙁

    No that is the first time they changed the class

    #31257
    Locohacker
    Administrator

    they change it from build 491 to 492 I think 🙄 , but they do the same with the send text apis so i was thinking they will do the same now with the systemview

    kane i gonna check it for ya 🙂

    #31243
    Chike
    Administrator

    They changed the text conrolles class?
    Anyway I am quite confident control IDs did not change.

    #31244
    Locohacker
    Administrator

    I mean how they change the atl: thing every time they make a new build. The control ID’s Im thinking will be the way to go since like you say those might not have change 8)

    #31246
    Chike
    Administrator

    Control ID are the way to go because even if they change its easy to have a list of version+IDs in descending order and search for the apropriate IDs.

    #31262
    DoubleM
    Member

    @locohacker wrote:

    @usenet7 wrote:

    @autopilot wrote:

    @DoubleM wrote:

    the auto-redot-ing is not working anymore. I always get the nick not found message. Any thoughts on how to fix it? I believe that happened after updating my paltalk to the latest build

    Most likely reason is the name change of the syslistview control.

    I changed

    <code>    Public ReadOnly Property NicListClass() As String<br />
    Get<br />
    Return "ATL:00A2DFF0" 'fomerly "SysListView32" in 10.2<br />
    End Get<br />
    End Property</code>

    and it worked after that.

    Yeps that works 🙂 the bad news is that paltalk always changes that with every new Build 🙁
    And did they change the way they send whispers? cause with the /w command everyone can see it 😆
    here the updated version

    Thanks for highlighting what you changed. That is much better than just fixing it. I’ll try it tomorrow. thump up

    #31270
    kane05
    Member

    any luck loco???

    #31271
    Locohacker
    Administrator

    I will check it on monday again lol I forgot to check the auto rd and bc sorry 🙂 but on Monday I do it for ya

    #31263
    Locohacker
    Administrator

    Sorry for the delays lol work is kicking my asz and paltalk keeps updating the damn atls, now up to build 497 ehehhehe

    #31264
    kane05
    Member

    im still on 591 and wont be updatingand still having those issues i told you aboutloco hope work gets easier on you

Viewing 15 posts - 61 through 75 (of 120 total)
  • You must be logged in to reply to this topic.