damencs / spawn-predictor Goto Github PK

It was working earlier and I haven't changed any settings. In the last 2 runs it hasn't worked (I don't see the white/green tiles anywhere).
I can't just restart and re-enter since I'm on a slayer task that would get lost on leaving.

This was on a leagues world if it matters.

I was told this would fix it but it still does not work :)

disregard

I didn't notice any issues while using the plugin, but I did get a lot of this in my logs:

2023-01-14 22:28:16 [Client] WARN  n.r.c.ui.overlay.OverlayRenderer - Error during overlay rendering
java.lang.IndexOutOfBoundsException: Index 63 out of bounds for length 63
	at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
	at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
	at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
	at java.base/java.util.Objects.checkIndex(Objects.java:372)
	at java.base/java.util.ArrayList.get(ArrayList.java:459)
	at com.spawnpredictor.overlays.DisplayModeOverlay.render(DisplayModeOverlay.java:94)
	at net.runelite.client.ui.overlay.OverlayRenderer.safeRender(OverlayRenderer.java:735)
	at net.runelite.client.ui.overlay.OverlayRenderer.renderOverlays(OverlayRenderer.java:328)
	at net.runelite.client.ui.overlay.OverlayRenderer.renderOverlayLayer(OverlayRenderer.java:235)
	at net.runelite.client.callback.Hooks.drawScene(Hooks.java:480)
	at hc.af(hc.java:13486)
	at bj.hb(bj.java:4626)
	at ay.kv(ay.java:10421)
	at ay.kv(ay.java:10452)
	at ay.kv(ay.java:10452)
	at ay.kv(ay.java:10452)
	at ce.ke(ce.java:10310)
	at client.hq(client.java:4330)
	at client.ab(client.java:1126)
	at an.am(an.java:416)
	at an.run(an.java:370)
	at java.base/java.lang.Thread.run(Thread.java:829)

As a user of the FC Spawn Predictor plugin, I would like to request the ability to manually set the rotation and wave in case the plugin is started after entering the fight caves. Currently, the plugin automatically detects the rotation and wave upon entering the fight caves, but there are situations where this automatic detection may not be accurate or desirable.

Use Case:

Scenario: A user enters the fight caves without starting the FC Spawn Predictor plugin. After realizing the importance of using the plugin, they start it up, but the plugin is not aware of the current rotation and wave, leading to inaccurate predictions.

Desired Outcome: The user should be able to manually input the current rotation and wave to align the predictions with the actual state of the fight caves.
Scenario: A user accidentally resets the plugin while inside the fight caves due to a technical issue or an accidental key press. As a result, the plugin loses the information about the current rotation and wave.

Desired Outcome: The user should have the option to manually specify the rotation and wave again to continue using the plugin without interruption.
Expected Features:

Manual Input: Provide a user interface option to allow users to manually enter the rotation and wave information.
Validation: Implement validation checks to ensure that the entered rotation and wave values are within the correct range and correspond to valid configurations.
Persistence: Save the manually entered rotation and wave values, so they can be used until explicitly changed by the user or until the end of the fight caves session.
User Feedback: Provide clear and concise feedback to users when they enter the rotation and wave values to confirm that the values have been successfully updated.
Additional Information:

If you're clock is slightly out on the computer, that causes the wrong wave to be predicted. Correct game UTC time can be seen in the clan panel for example.

Not sure if there's anything you can actually do about this, I checked the code for the built in report button plugin and they're using the same built in java time tools. I can't see any plugin making use of the time from the clan panel.