The following varps were newely created instead of using an existing varp for server side only.

• 295=skill_clock
• 296=skill_anim
• 297=skill_sound
• 298=shop
• 299=shop_buy
• 300=shop_sell
• 301=shop_haggle
• 302=thread_used

Treasure trails needs to be rewritten to only use the following varp:

• 292=ring_of_forging_charges_used

The following varps need to be removed from current treasure trails:

• 275=trail_easy_steps_count
• 276=trail_medium_steps_count
• 277=trail_hard_steps_count
• 278=trail_easy_steps_completed
• 279=trail_medium_steps_completed
• 280=trail_hard_steps_completed

Please refer to: https://github.com/2004scape/Server/wiki/Varp-ID-Tracking

Works fine on the Java client.

Only quest reward screen is using this atm.

The Drawers have an Open action but nothing happens (no animation, no chatbox text).

The chatbox text in the screenshot is from Examine

May be all Drawers? Happens to the one in Seers' Village too:

There are many different dialogues on OSRS if you try to cook (anything) on the spit-roast too early in the quest. I have an RSProx capture for this.

We should commit package-lock.json and update the README to use npm ci.

https://docs.npmjs.com/cli/v9/configuring-npm/package-lock-json

The setup steps will be more simple and more easily guaranteed to work, plus it means that whatever version of Node/Java etc the user has installed locally (if at all) is irrelevant, and will be controlled through the image.

Considerations:

• Multi-step Docker image can be used to have effectively a "runtime" build (slimmer) with a "dev" step attached to the end in order to handle hot reloading etc.

Ladder down works, ladder back up doesn't

@ultraviolet-jordan notes that supporting a full 2k world won’t be ideal due to pf speed (note that in real world cases not every player is generating a path every tick). We’re not expecting more than double-digit players and local development, which runs without issue.

Napkin benchmark: 100k paths, 10 tiles away - ~3000ms in TS, ~434ms in reference Kotlin implementation.

I think we can figure out JS/TS-specific optimizations and/or move pathfinder to native code. Jagex did client-side pathfinding at the time and evaluated steps from those generated paths on the server instead.

clicking this chest with the door closed should result in "I can't reach that!", instead its allowing me to interact

Steps:

• Spawn two objs of the same id
• Drop them one at a time
• Pickup one of them
• You gain one and the other disappears.

Make players walk to varrock

I can deploy and run in localhost and host across my network. But what settings do I need to deploy with a login server so that I can host a server on my lan with users having login and passwords ?
once I know what im doing I will add an update to the docker compose file

thanks

Kill tracking still needs to be implemented

These aren't necessary and are probably the cause of the ts-node issues

I will look into this

https://discord.com/channels/953326730632904844/1126857340075905135/1127691117429796934

Sometimes when walking up to rocks to mine, my character faces the same direction I was walking and keeps that direction upon mining and continual mining (never rotates towards the rock)

On OSRS I recall sometimes having the mining animation start facing the walking direction if I was running to it, and then the character would rotate towards the rock upon mining it.

Spinning wheel can do it too:

And Ranges, but if I log-out facing that direction and use the Range immediately after log-in my character rotates towards it:

When using the in-browser client, music stops playing after a while:

• Sometimes it stops looping after a while (choosing a new song and going back to Auto works)
• Sometimes music (possibly all audio) stops working altogether (possibly main menu too); it comes back after a quick page refresh

I made a start on this but far from complete:

• Go through code in Player and check it belongs there
• Go through code in NetworkPlayer and check it belongs there

[opheld5,_]
if_close;
if (busy = true) return;
inv_dropslot(inv, coord, last_slot, 200);

uses if_close; which causes the entire script if currently active to drop.

    closeModal() {
        this.weakQueue = [];
        this.activeScript = null;

        if (this.modalState === 0) {
            return;
        }

example is going through the lumbridge toll gate and try to drop/wear/unwear/eat an item while currently delayed and going through the gate. this should be blocked from happening.

• was this in RS 2004?
• if so it needs implementing