More work on OP_Marquee. Should be enough to implement a function with it. Anyone wants to fiddle around with the unknowns and get them better documented they are free to.

2026-09-02 04:16:46 +00:00 · 2013-12-23 15:42:13 -08:00
parent ccf6b5ff68
commit a96f10b6aa
6 changed files with 27 additions and 70 deletions
@@ -5077,13 +5077,15 @@ struct ServerLootItem_Struct {
 //"Got a broadcast message for ... %s ...\n"
 struct ClientMarqueeMessage_Struct {
 	uint32 type;
-	uint32 unk04; // no idea, have seen 10 mostly, didn't notice a change when altering it
+	uint32 unk04; // no idea, didn't notice a change when altering it.
+	//According to asm the following are hard coded values: 2, 4, 5, 6, 7, 10, 12, 13, 14, 15, 16, 18, 20
+	//There is also a non-hardcoded fall through but to be honest i don't know enough about what it does yet
 	uint32 priority; //needs a better name but it does:
-	//opacity = priority / 255
-	//# of ending blinks = (int)((priority - 1) / 255)
+	//opacity = (priority / 255) - floor(priority / 255)
+	//# of fade in/out blinks = (int)((priority - 1) / 255)
 	//so 510 would have 100% opacity and 1 extra blink at end
-	uint32 unk12; //no idea, seen 0, 500, 1000.  
-	uint32 unk16; //no idea, seen 500, 1000
+	uint32 unk12; //no idea, seen 0, 500, 1000.  I'm assuming this has to do with the fade in/out.
+	uint32 unk16; //no idea, seen 500, 1000. I'm assuming this has to do with the fade in/out.
 	//Visually I couldn't tell a difference from these previous two, 
 	//but there's probably a reason for them that's more subtle than what i was looking for
 	uint32 duration; //in ms