[Help]Error in GS

[Lineal]

Hey guys i started creating a pack  , and i pass many j codes but i didnt test them...so i decided to start testing!

When i start GS i have this error .. ->      

 

Can anyone help me?And please do not start the "teasing"

I have no errors in eclipse as i saw .I thought all will working properly but , ..

[Tryskell]

It's probably a missing handler, or more accurately an handler which got no content/miss contents so you can initialize it but when it comes time to load -poof-.

 

In AdminCommandHandler, search the line 67, and correct content of the handler.

 

Post both line and eventually the file itself :P.

[Lineal]

It's probably a missing handler, or more accurately an handler which got no content/miss contents so you can initialize it but when it comes time to load -poof-.

 

In AdminCommandHandler, search the line 67, and correct content of the handler.

 

Post both line and eventually the file itself :P.

i didnt undestand what i have to do to fix it -.-'

[Tryskell]

In AdminCommandHandler, search the line 67, and correct content of the handler.

 

It was a 3 lines answer, hard to miss it :P.

 

A tip you surely won't follow, but don't begin a pack if you fail correcting that already. I know it's "cool" to be the leader of a project, making it private you can make a lot of $$$ selling crap... Well, the last argument doesn't deserve my speech.

 

Bha.

 

---

 

PS : a forum is a forum. If solution (or at least the "logic approach of the problem") can be seen by all, it helps the community. Fixing your error via TeamViewer will lead to 2 things : this topic will be useless for community, as solution won't never be given ; and second is if I correct, you won't be able to correct things by your own, and finally ask help anytime you're blocked.

 

I'm blocked too deving my own stuff, but I manage to find solutions by my own. Thinking another way will lead to the death of your project. That doesn't mean I can't help you. But try to think one, two or more times and don't hesitate to re-read what people write.

 

Tk.

[Lineal]

Mate i cant find any error at line 67 -.-'

[Lineal]

bump

[SweeTs]

Well, Tryskell said you already what to do...

 

In AdminCommandHandler, search the line 67, and correct content of the handler.

 

And if you can't handle it by yourself..

 

Post both line and eventually the file itself :P.

[Lineal]

 

and no errors

[Tryskell]

Ofc there is, you got no handlers to load but engine try to load. So null error as there is nothing to load.

 

Make something load or delete the whole adminCommandHandler if you don't need it anymore.

 

---

 

It's not because it compiles fine that you didn't break your whole server. You can delete a whole thing on eclipse, with some luck it can compile fine directly, but ingame or at server loading, you will cry all tears out of your body.

 

I was right saying that :

 

It's probably a missing handler, [...] so you can initialize it but when it comes time to load -poof-.

[Lineal]

Ofc there is, you got no handlers to load but engine try to load. So null error as there is nothing to load.

 

Make something load or delete the whole adminCommandHandler if you don't need it anymore.

 

---

 

It's not because it compiles fine that you didn't break your whole server. You can delete a whole thing on eclipse, with some luck it can compile fine directly, but ingame or at server loading, you will cry all tears out of your body.

 

I was right saying that :

 

Can you give me a solution?-/-'

Explain the " Make something load " like what and how?

[Xanderॐ]

O boy. Show us line 68. You pasted the code but did not highlight the line that has the bug.

[Agelos_DSF]

why dont you take again the default handler and try to put again your code there ^^ ?

[Tryskell]

I finally corrected it for him on TV6 2 days ago (I asked him to make an answer but he made nothing), it was a non-existing handler who was called on Gameserver.java (as you perhaps don't know, IL got its handlers on Gameserver.java).

 

So basically he was calling a handler which wasn't existing/imported (was for event engine).

 

-----

 

The funny/sad part (depending of pov) is he got between 2-4 others bugs, not related to this one, and before to be able to logon (so, possible more once logged).