For some reason the auto response returned by the bot does not work. I type "Hey" but get no 'answer' from the bot.
I have read all topics.
My heroku is properly pointing to the url.
The email notifications are coming through.
The whispers are working properly
I replaced the script.js file with the original one (used by EstherBot)
Yet nothing happens...
anybody a clue?
thanks
Wouter
Right - fixed it.
I went back to earlier versions - but in vain.
I then killed all whispers - but no result.
I then replace all code manually with the original code - but no result.
Basically I just went back to the drawing board and reinstalled it (as was suggested already by #AndrewLavers).
It only means I actually have not been able to figure out the why.... which is a pitty.
CLOSED
Related
So my discord bot that I host on repl.it for free (so that might be the problem) works fine most of the time but sometimes, it will just randomly stop working. Even when I restart it, the client.on("ready") function won't trigger and nothing works. This problem just fixes it self after some time but it is really anoying and it keeps happening. It has nothing to do with my code as it works and there is nothing chance based in my code that may break it, and even then it would trow an error, this just doesn't work and doesn't give any errors. If you would like to take a look at my code it is on repl.it here. Thanks in advance!
Replit is a free hosting platform but if I remember well, if no one get into the page for a certain time, the program will stop. It is probably that that stops your bot.
(sorry if you don't understand well my English)
heyy, you can fork your repl, if you're token is in the process.env you must add it, else if your token is in a config.json file, it's ok, just fork it and it's done
I am trying to build a JavaScript Minecraft bot. I tried Mineflayer, but they do not support version 1.17.1. That's when I found out about node-minecraft-protocol, the library which mineflayer is based out of. They support version 1.17.1! I have been trying to make my bot move for the past three days, but I'm not able to figure it out from the docs. I even tried looking into mineflayer's code! Connecting to the server, sending chat messages, reading chat messages, and reading current position are all fine! It's moving the bot that gives me trouble. Or for that matter, flying, looking or anything similar (that takes f64/f32 values as input). To give you an idea of what I'm trying to achieve, here is something that I have tried running (-181.52092902441308, 84, and 134.53013736121238 are the spawn coordinates):
client.write('position', {
x: -182.52092902441308,
y: 84,
z: 134.53013736121238
})
I fixed it, for anyone who's looking for an answer! The problem was with the 1.17.1 update in the Minecraft protocol. You need to send 'teleport_confirm' with the 'teleportId' sent with the position update in order to actually move the bot.
NOTE: Here is an example repo with the problem.
When I run ./gulp js, the process works (creates the expected files on the file system), but the task never completes... just hangs indefinitely:
ss http://zc.d.pr/4C9U/3GG90rpz+
I figure I'm not returning something somewhere, or invoking a callback correctly, but after hours of tinkering, head-banging, and Googling, I haven't found a solution.
Can someone help me out here?
If it makes a difference, I'm currently using node v4.1.0. All other dependencies and versions are in the example repo linked above.
EDIT: Original inspiration for this gulp recipe came from https://truongtx.me/2015/06/07/gulp-with-browserify-and-watchify-updated/
However, I couldn't get transform to work as that author suggested, which led me to https://github.com/substack/node-browserify/issues/1198#issuecomment-89948202
Of course—as it always happens—I think of something new to try just after I post to SO and it appears to work.
doh http://zc.d.pr/11uMa/5gghjbCx+
You can see my full changeset here: https://github.com/neezer/gulp-browserify-hanging-task/commit/8156e182c04c2e76c5739e31f5a6e417dda01b70
TL;DR Basically I tried the suggestion in the last comment on the aforementioned issue from my question, where I pass the file object itself to browserify instead of the file path, and lo-and-behold, the task finishes now.
I don't pretend to know why that fixed the issue, so if anyone would like to explain, I'd love to learn. ;)
I have problem with me51n. I have an include in EXIT_SAPLMEREQ_010 that has a bunch of codes which we use it to receive errors. The problem of mine is;
-When i run me51n with required datas(mat. number, quantity, etc.) I get some errors which also includes the error that I'm expecting on the first time, however when i terminate me51n and run it again with the same exact data, i dont get my error. I have debugged it and put a break point on my include in EXIT_SAPLMEREQ_010 and it never gets to my breakpoint on the second run. (It gets to the breakpoint on the first run but not the second one).
I dont know how but with the same material it works fine later again at the first time but still on the second time i cant get the error again.
Can anyone please help me on this?
Basically problem was the developement system from the beginning (sigh -_-). While having other errors rather than my errors, i assume my error gets stuck sometimes and never pop up because of the standard SAP procedure. So in test system (QA) me51n works perfectly when I'm just trying to have only my error.
Thanks for anyone who actually tried to help and I hope this might be useful sometime for someone in future.
Talha
This suddenly stopped working, it was working, but now its not:
If I use the twitter UI and go to:
https://twitter.com/#!/search/%22social%20snap%22%20OR%20%22socialsnap%22%20OR%20%22socialsnap.com%22
I get 7 results.
If I use the api with the same call:
http://search.twitter.com/search.json?q="social snap" OR "socialsnap" OR "socialsnap.com"
I get zero results (ran in browser to simplify test)
Im sure im being an idiot or there is some encoding issue, but im stuck...any ideas?
Well I finally figured it out, I have no idea why, but this works:
http://search.twitter.com/search.json?q=/"social snap" OR "socialsnap" OR "socialsnap.com"
adding the slash after the q= makes it work...