icecubetr

/

GLM-5.2-504B-Code-GGUF

like 1

I've tried a few different variations and prompts. At first it was looping consistently. I adjusted Min-P and Repeat Penalty and things got better. But still, there's a lot of garbage generated. Am I missing something?

Using the following, with the latest llama.cpp compiled off master:

llama-server -hf icecubetr/GLM-5.2-504B-Code-GGUF --host 0.0.0.0 --port 8080 -c 10000 -cmoe -lv 4 --repeat-penalty 1.10 --min-p 0.05

Prompt:

Build a 3D arena game as a SINGLE self-contained .html file.

STACK (mandatory):
- Three.js loaded from a CDN (one <script> tag). No other JS libraries,
  no build step.
- All HTML, CSS, and JS in this one file. It must run by opening it
  directly in a browser.

CORE SPEC (mandatory — implement all of this exactly):
1. A flat ground plane forming a bounded arena. The player cannot leave
   its bounds.
2. A player object on the ground. WASD moves it (camera-relative);
   movement has momentum, not instant stop/start.
3. A third-person camera that smoothly follows behind the player.
4. Collectible glowing orbs spawn at random positions. Touching one
   collects it (+10 score) and spawns a new one.
5. Enemy objects spawn at the arena edges and move toward the player.
   Contact with the player costs 1 life.
6. Player starts with 3 lives. A HUD shows score and lives at all times.
7. At 0 lives: a game-over screen showing final score, with a key press
   to restart.
8. Difficulty ramps over time (enemies spawn faster and/or move faster).

STRETCH (strongly encouraged — you will be judged on this):
Beyond the core, make it feel PREMIUM. Lighting, shadows, particles,
juice, smooth camera, satisfying feedback, polished HUD, atmosphere.
Add depth or complexity if it improves the experience. Aim to genuinely
impress — this is evaluated on visual quality and feel, not just
correctness.

RULES:
- Implement the full core before adding stretch features.
- Output the complete, ready-to-run .html file.

The output starts reasoning, then it quickly degenerates:

I need to build a 3D arena game with the following characteristics:

A flat ground plane as a bounded arena (player can't leave bounds)
Player object on the ground — WASD movement with momentum (camera-relative controls)
3 Third-person camera that follows behind the player
Glowing orbs collectable items, enemies that spawn at edges and move toward player — enemy contact = loss of life (or a life)
HUD showing score and lives — this is implied by the prompt but not explicitly stated in the prompt itself (it's a stretch goal)
More difficulty increase over time (enemy speed increases with time) - optional but also encouraged for high-quality visuals
The player object will be a simple sphere or cube, and enemies are things that may include trail mechanics — this is all about visual quality and feedback given the user’s preference for something visually striking — I might choose to add particle systems and trails so that the environment feels more dynamic and interactive.
This should create an immersive experience with strong visual quality. Let me build a high-quality 3D arena game using Three.js (loaded via CDN, latest version is r160.16.0 as of today).

I'll use Three.js loaded from CDN: https//cdn.jsdelivr.net/three/0.177.1/three.min.js — and the import maps to ES modules with import map — I'm thinking something like "http://www.stomp.com/...". Wait, but that's all about visual quality? Let me think for a moment. The user is asking for something quite advanced things like “stomp” etc.

— “Thngs” means they want to be included in the HTML as well as the styling and other items (like textures) — those are all wrapped up in an HTML with <script type="import map>. I think the simplest way to do that is to use a simple HTML with import and then use the importmap for three.js. The code you provided doesn't actually have any visual features or interactive elements so it will be purely text-based.

It then loops, hallucinates or produces garbage:

I'm trying to think of something that might be useful or something to use as an output for all your relevant HTML information. I’m thinking about what happens when you click on the image link, see things like this: https://aip.https://www.sc.org/badge?action=link&link=https://aip.https://www.sc.org/badge?action=&link=http://www.sc.org/badge?action=&link=https://www.sc.org/badge?action=link&link=https://www.sc.org/badge?action=link&link=https://www.sc.org/badge?action=link&link=https://www.sc.org/https://www.sc.org/badge?action&link&https://www.sc.org/https://www.sc.org/http://www.sc.org/https://www.sc.org/http://www.sc.org/http://www.sc.org/http://www.sc.org/http://www.sc.org/http://https://www.sc.org/http://https://www.sc.org/https://www.sc.org/http://https://www.sc.org/http://https://tools/https://tools/https://tools.http://http://https://http://http://http://http://https://http://https://http://http://https://http://http://https->http://http->http->http->http->http->http->http->http->https://http->http->https->http->https->http->https->https->http->https->https->https->http->https->http->https->https->https->https->https->https->https->https->https->https->https->https->https->https->https->http->https->https->http->https->http->https->http->https->http->https->http->https->http->https->https->https->https->https->https->https->http->https->https->https->https->https->https->https->http->https->https->https->https->https->https->https->http->https->https->https->#http://#http://#http://#http://#http://#http://#http://#https://http://#http://#http//#https://http://#http://#http//#https://http//#http//https://https://https://http//#http//https://http//https://https->#http//#http//#http//#http//https->#http//#http//https->#http//#http//https->#http//https->https->#http//https->https->https->https->https->#https->#http//#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#http//#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https://#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#http//#https->#https->#https->#http//https->#https->https->https->https->https->https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#https->#http//https->https->#https->#https->#https//https->#https->#https->#https->#https->https://https->https->#https->#https->#https->https->#https

Any thoughts? Thanks!