[EN/PT-BR] Horizon Forge: Updates and definition of version v1.0, plus the next focus.
Chatgpt
This is a compilation of the last few days. The post was supposed to be made yesterday, but I had a complicated problem to solve and ended up not being able to post it, so here's the summary.
Improvements:
Modification of internal files to Vite + React, complete restructuring of the files. The idea is to facilitate maintenance, instead of leaving everything fixed in pure HTML and CSS.
Creation and addition of the game icon, that icon that appears next to the page name at the top in the tabs. I liked this image, it may change in the future, but for now it's this one.
- Modification of the training tab, removing the icons/emojis and replacing them with hero portraits. This slightly changed how the information is displayed in that area. The functionalities are the same, only the visual aspect is modified.
Old:
New:
- Added the correct version count. We'll start at v1.0 and now it's supposed to be incremental. For now, 2 numbers, maybe I'll add 3 in the future. Also, I added the link to the official Horizon Forge Discord server in the Config > About section.
Difficulties:
Yesterday I had some problems using Vite + React. I was generating the versions and uploading them to the server, but there were problems with the backend server located on Railway, and because of that, the improvements weren't going to production.
The complicated thing was that nowhere showed the error, not even VS Code or anything like that, because the game worked without problems on localhost. So when I went to test the changes in the mobile version, I saw that the layout wasn't updating, and I realized there was a problem somewhere.
After investigating, I saw that it was Railway, the backend server. Anyway, I had to do some rollbacks, lost some things, and had to fix it again, but now everything is fine!
The browser version is all OK:
https://horizonforge-production.up.railway.app/
Now, I'm going to focus on the mobile version; I need to analyze and fit each component correctly and effectively for use on mobile phones. The biggest challenge is the battlefield file, but things are progressing. I hope you enjoy these updates, see you next time!
Chatgpt
Esse é um compilado dos últimos dias, a postagem era para ter sido feita ontem, mas tive um problema complicado para resolver e acabou que não consegui postar, então aqui vai o resumo.
Melhorias:
- Modificação dos arquivos internos para vite + react, reestruturação completa dos arquivos. A ideia é que isso facilite na manutenção, no lugar de deixar tudo fixo em HTML e CSS puro.
- Criação e adição do ícone para o jogo, aquele ícone que fica do lado do nome da página lá em cima nas abas. Gostei dessa imagem, pode ser que mude no futuro, mas por enquanto é ela mesmo.
- Modificação da aba de formação, removido os ícones/emojis pelo portrait dos heróis, com isso mudei um pouco a forma como mostra as informações daquele lugar. As funcionalidades são as mesmas, apenas a parte visual mesmo modificada.
Antigo:
Novo:
- Adicionado a contagem de versão correta. Vamos começar em v1.0 e agora é para ser incremental. Por enquanto 2 números, talvez coloque 3 futuramente. Além disso, adicionei o link para o discord oficial do Horizon Forge na seção de Config > About
Dificuldades:
Ontem tive alguns problemas em relação ao uso de vite + react, estava gerando as versões e subindo para o servidor, mas estava com problemas no servidor de backend que fica no railway e com isso, as melhorias não estavam indo para produção.
O complicado foi que nenhum lugar mostrava o erro, nem o VS Code ou coisa do tipo, porque em localhost o jogo funcionava sem problemas. Então quando fui testar as alterações da versão mobile, vi que o layout não estava atualizando, ai percebi que tinha um problema em algum lugar.
Após investigar, vi que era o railway, o servidor de backend. Enfim, tive que fazer alguns rollbacks, perdi algumas coisas e tive que arrumar novamente, mas agora está tudo certo!
Versão para navegador está tudo OK:
https://horizonforge-production.up.railway.app/
Agora, vou focar na versão mobile, preciso analisar e encaixar cada componente de uma forma correta e eficaz para o uso em celulares. O maior desafio é o arquivo referente ao campo de batalha, mas as coisas estão encaminhando. Espero que gostem dessas novidades, até a próxima!
Enter in the Horizon Forge >>Discord<<
🔥Please, consider helping by using my reference links🔥
| Post To Earn | DePIN | Win SATS | Win SATS | Have Fun To Earn |
| Publish0x | Honeygain | Slice | ZBD | Rumble Arcade |
Hey, lots of new information! I'd like to try the game, but tell me about the security when logging in with the passwords?
Thanks for the question Angeluxx! I had already noted it down to review the security with the keychain login. Since you log in using the keychain extension, it's mandatory, but you can never be too careful, so I asked Claude Code to review the code and we implemented another layer of security:
Problem fixed:
The Keychain signature was being discarded — anyone could forge a session in sessionStorage and impersonate any player.
Implemented solution (4 files):
api/server.js:
POST /api/auth/verify — receives {username, memo, signature}, retrieves the public key from the account on the Hive blockchain, cryptographically verifies that the signature matches the memo using @hiveio/dhive, and issues an HMAC-SHA256 token valid for 24 hours. Middleware Socket.io (io.use) — validates the token in the handshake of each connection and populates socket.data.username. join_queue and rejoin_match — now use socket.data.username (defined by the middleware), completely ignoring the username sent by the client.
public/js/index.js:
After the Keychain signs, it POSTs to /api/auth/verify with {username, memo, signature: resp.result}. Only saves the session in sessionStorage if the server confirms — and includes the returned token. public/js/lobby.js:
Pass auth: { token: session.token } in the socket connection. Remove username from the join_queue payload (the server no longer accepts it).
public/js/battle.js:
Pass auth: { token: window._HF_SESSION?.token } in the PvP socket connection. Remove username from the rejoin_match payload.
What to add to the .env file:
XXXXXX=a_long_random_string_here
Without this, the server generates an ephemeral secret—it works, but tokens are invalidated upon restart. With AUTH_SECRET defined, sessions survive restarts.
Nossa, não entendi nada, mas hehehe, se você diz que é seguro, é importante saber, porque segurança é super importante no Hive. Vou dar uma olhada.
via Apps from