Let me try and help. Unfortunately I was not sure what I was doing wrong and so did not have specific questions to ask. I have highlighted the key indicators in the text, hopefully that will shed some light on it.
Quote:
I am having issues building a packet and sending it to a Minecraft RCon server.
Now this first line tends to suggest that this is the area I need help with. If we break it down into its components, it could give us an idea of what im trying to do. A quick google of those topic areas could shed some more light.
and then when you mix it with these...
Quote:
1. The documentation say's that the packet components are 32bit littleendian integers, I have no idea how to do that. I think because im on linux they are littleendian but how do I make them 32bit.
Ok, so breaking this part down tends to suggest that there is documentation on the topic in question which is a good thing. This means we can google it and get more relevant information. It also looks like im having issues converting the packets to 32bit form, perhaps something you could help me with. A quick read of my code below may indicate where im going wrong and then you could make some suggestions.
Quote:
2. The payload must be byte[] form, I am not sure how to do that either.
Another clue, this looks like a simple one as the payload is probably a part of the packet and is most likely stored in a variable. We can examine the code below to make sure and then maybe provide some helpful insights.
3. Still also trying to find a way to get a response from the server.[/QUOTE]
Not really very helpful as the server probably wouldn't respond if im sending bad data to it but a quick look at my code might reveal if im doing any thing wrong.
Admittedly, it would have been better if I actually added some links as reference so you could know what I was on about. Which is probably why I added this line.
Quote:
As I have less than 5 posts it said I had to remove the links you will need to help so good luck!
Next time I will try to ask more specific questions like on stackexchange to make it easier for you. Oh wait, was that another clue...