PrismarineJS / PrismarineJS/node-minecraft-protocol
Proxy will just show the skin for other players and in the tablist, and not for myself
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 290
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 7
Description
So, i was coding a proxy, that allows you to join a server (e.g.: Hypixel) with another account, without having to relaunch the game. But, if i join the proxy, i get connected to the target server, but, for me, i don't have a skin. Other players can see me just fine, but i myself can't. Is this even possible? Here is my code, if that helps:
var mc = require( 'minecraft-protocol');
var server = mc.createServer({
'keepAlive': false,
'max-players': 1,
'motd': 'Proxy-Test',
'version': '1.8.8',
'online-mode': true,
'port': '25576'
});
server.on('login', client => {
const remote = mc.createClient({
keepAlive: false,
host: 'myserver.net',
port: '25565',
username: "obviouslynotareal@email.com",
password: "password!",
version: '1.8.8'
});
[remote, client].forEach((value, index, array) => {
const opposite = array[index === 0 ? 1 : 0];
value
.on('end', () => opposite.end('Disconnected'))
.on('raw', (buffer, metadata) => {
if (metadata.state === 'play') opposite.writeRaw(buffer);
});
});
}
});
console.log('Started proxy on port '+server.port);
Any help is appreciated! I just can't figure this out for my life.
Kind regards,
Tuxorials
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the JavaScript proxy code in the issue, especially the login handler and the raw packet forwarding between client and remote. Determine whether the relevant skin or tab-list packets are forwarded in both directions, then verify the behavior with a 1.8.8 client and target server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100