New plugin welcome?

[suntong]

I'm planing to write a new plugin for your excellent package.
Would you accept PR for it?

I can provide more details if interested.

thx

[songtianyi]

Sure, any contributions would be appreciated.

[suntong]

Thanks I'll see...

[suntong]

Done -- it is at https://github.com/suntong/wx-go/tree/master/plugins/gamer24

I figure I'd better to keep it in a separated repo than submitting PR each time I need to amend it.
and that idea turns out to be useful as I'm having problem make my first wechat-go application work.

I found that whenever I get that specific command "3824", immediately I'll get [I] trying re-login with cache from the console log. Tried many time and it is always the same.

So I added logging in my plugin, but none of the loggings are printed to the console, so I suspect that something else is wrong.

Would you look into my simple wechat-go application and see what went wrong please?

Thanks a lot!

[songtianyi]

Nice plugin!
I will check the code when i'm free.

[songtianyi]

Again, it works for my account :(

5 4
 8 8
-!!
:(5 - 8 / 4) * 8

 6 8
 8 9
-!!
:8 * 9 - 6 * 8
 3 8
 6 5
-!!
:3 * 8 * (6 - 5)

 1 4
 1 6
-!!
:(1 + 4 - 1) * 6

[songtianyi]

How to play this game in wechat?

[suntong]

• just scroll back and reveal only the first four cards on the mobile device
• If you don't think there is an answer, scroll one more line to reveal the hint.
  • -!! means there is a solution.
  • -XX means there is indeed no solution.
• The solution given is the fist one found, not mean to cover all cases.

[suntong]

So you just build and run my wx-go as is, or you added the plugin to your own code?

[songtianyi]

So you just build and run my wx-go as is, or you added the plugin to your own code?

run your wx-go as it is.

[suntong]

k. thx. will try again.

[suntong]

Hey, sorry to get back late to you.

I think I know what's wrong -- I've always been scanning-in on the second attempt. I.e., after I saw the following time out error in my console.

2017/12/20 19:32:01 [W] login response, window.code=408;
2017/12/20 19:32:01 [E] session exit, login response, window.code=408;

whereas you must have been always scan-in right away. Today I did that, and everything works out for me this time. I'm opening another thread to talk about it in details -- #39.