Numba1stunna

What do you want it to do...

You should still add "return true" after the Cast API to avoid the rotation casting 2 spells simultaneously. Set the spell to 0 in PQR. Example: if API1 then CastSpellByName("Spell name one","target") --warning no return value! end if API2 then CastSpellByName("Spell name two","target") end -- if API1 and API2 are both true, PQR will try to cast spell 1 and spell 2 at the same time! -- time to fix if API1 then CastSpellByName("Spell name one","target") return true -- PQR will return true if API1 is true and will return to the start end if API2 then CastSpellByName("Spell name two","target") return true end -- example of a non-return value with a return value if API1 then if API2 then UseInventoryItem(13) -- use trinket, both API1 and API2 must be true end CastSpellByName("Spell name three","target") -- only API1 needs to be true end -- example to SKIP a spell in PQR if IsMounted() then -- if the player is mounted return false -- this will skip the spell and go to the next spell on the list else CastSpellByName("Spell name four","focus") -- we can cast at a focus target too end

There are different ways of scripting this. One is through events SPELL_CAST_START or SPELL_CAST_SUCCESS or through UnitCastingInfo() / UnitChannelInfo() functions. Learn lua, and you don't ever have to pay for scripts that noobs leech off others, anyways.

I learned there is something strange about the mesh files. They get corrupted by the Honorbuddy. If you're having problems with movement, check the navigation log. Redownload/backup an original mesh folder and replace the old folder.

@thefaroe Learn some basic XML format and honorbuddy namespaces (they're like objects you can use for the bot). Use some profiles which are already made as reference. For you specific problem, use "if player has quest and is quest complete, then move XYZ interact with unit and turn in quest". You NEED to write a different profile for PRIVATE servers because RETAIL is different. You either clean the retail profiles or start from scratch.

Oh sorry, what I meant by questing bot was a questing profile. This is for Honorbuddy 3.3.5a. It's in primitive namespaces, so some quests are not possible to write.

Hello, I am currently working on a questing profile for 3.3.5a. Looking for people who know how to write 3.3.5 questing profiles. It's not hard, it's all XML, and if more people can join in, it will make a huge difference. Keep in mind, most likely you will have to make overrides for most quests, Honorbuddy has made quests for retail and usually the quests will take longer or not function correctly at all. You don't even have to make new characters. All that is required is if you enter a ZONE WITH NO QUESTS COMPLETED, create a quest order specifying the area and your level from start to finish OF ONE SPECIFIC AREA. Format goes as follow: <!-- PUT THE AREA OF WHICH YOU ARE LEVELING, YOUR LEVEL YOU'RE DOING THIS --> <!-- DO NOT SKIP THIS STEP OR ELSE I WILL NOT ADD IT TO A COMMUNITY PROFILE --> <Blackspots> <!-- BLACKSPOTS HERE --> </Blackspots> <!-- Quest Overrides here --> <QuestOrder> <Checkpoint Level="" /> <!-- PUT THE LEVEL REQUIRED TO DO THESE QUESTS HERE --> <!-- FORMAT: Pickup, Objective, turn-in --> <!-- QUEST ORDERS GO HERE --> <!-- DO NOT ADD CLASS SPECIFIC QUESTS --> <!-- Keep in mind, you don't necessarily have to do "pickup, objective, turn in" in that order You may pick up 3 quests, do 3 objectives at once, then turn in 3 quests Use the Honorbuddy Profile tab --> <!-- ONCE THE QUEST ORDER IS DONE, YOU MAY PUT A GRINDING AREA HERE --> <SetGrindArea> <GrindArea> <TargetMinLevel></TargetMinLevel> <TargetMaxLevel></TargetMaxLevel> <Factions></Factions> <Hotspots> <Hotspot /> <Hotspot /> <Hotspot /> <Hotspot /> </Hotspots> </GrindArea> </SetGrindArea> <GrindTo Level="" /> </QuestOrder> Quest orders must be tested before posting. If nobody inputs for this profile, then I will slowly but surely complete this. Started yesterday and completed 1-20. EDIT: Forgot to mention, this is for alliance.

I will probably make a guide on PQR for 3.3.5, but PQR is just learning lua and wow API (mostly using if...then statements and wow API for filters / execution). PQR is a Rotation bot. Rogue stealth needs more filters like damaging dots. Those can be added by iterating a table of enemy dots using a combat log and an API function to check debuffs. This is a little more complicated and shouldn't be done unless you know what you're doing, as it may cause FPS lag. But this is the difference between a mediocre profile and an excellent one.

Glad to hear that. If anyone needs offsets, just PM me, but please make sure the offsets are not the same as retail offsets or the one I posted.

It seems that Panda WoW uses the same offsets as retail. Try this one, and if it doesn't work, I can double check all the offsets: <?xml version="1.0" encoding="UTF-8"?> <Offsets> <CurrentWoWVersion>18414</CurrentWoWVersion> <WoWVersionOffset>0xC7B20F</WoWVersionOffset> <PlayerName>0xEC4180</PlayerName> <PlayerClass>0xEC4309</PlayerClass> <GetCurrentKeyBoardFocus>0xBB244C</GetCurrentKeyBoardFocus> <GameState>0xD65626</GameState> <Lua_DoStringAddress>0x50236</Lua_DoStringAddress> <Lua_GetLocalizedTextAddress>0x414C74</Lua_GetLocalizedTextAddress> <CVarBaseMgr>0xBA5908</CVarBaseMgr> <CVarArraySize>0x400</CVarArraySize> <ObjMgr>0xEC4140</ObjMgr> <CurMgr>0x462C</CurMgr> <ClntObjMgrGetActivePlayerObjAddress>0x4FC6</ClntObjMgrGetActivePlayerObjAddress> <LocalGUID>0xE8</LocalGUID> <FirstObject>0xCC</FirstObject> <NextObject>0x34</NextObject> <Descriptors>0x4</Descriptors> <Obj_TypeOffset>0xC</Obj_TypeOffset> <Obj_X>0x838</Obj_X> <Obj_TargetGUID>0x16</Obj_TargetGUID> <ClickTerrain>0</ClickTerrain> </Offsets>

Sorry for the late response. I am working on the offsets right now. Thank you for the link. If anyone else needs offsets, PROVIDE A LINK OF THE DOWNLOAD TO THE EXE OF YOUR SERVER. Too many people ask for offsets for "wow v3.3.5" etc but I don't know for what server.

Wow, I actually had it, somehow I didn't add it to the list. Got it now, thanks. <?xml version="1.0" encoding="UTF-8"?> <Offsets> <CurrentWoWVersion>18414</CurrentWoWVersion> <WoWVersionOffset>0xC7B6EF</WoWVersionOffset> <PlayerName>0xEC4668</PlayerName> <PlayerClass>0xEC47F1</PlayerClass> <GetCurrentKeyBoardFocus>0xBB292C</GetCurrentKeyBoardFocus> <GameState>0xD65B16</GameState> <Lua_DoStringAddress>0x4FD12</Lua_DoStringAddress> <Lua_GetLocalizedTextAddress>0x414267</Lua_GetLocalizedTextAddress> <CVarBaseMgr>0xBA5DE8</CVarBaseMgr> <CVarArraySize>0x400</CVarArraySize> <ObjMgr>0xEC4628</ObjMgr> <CurMgr>0x462C</CurMgr> <ClntObjMgrGetActivePlayerObjAddress>0x4F84</ClntObjMgrGetActivePlayerObjAddress> <LocalGUID>0xE8</LocalGUID> <FirstObject>0xCC</FirstObject> <NextObject>0x34</NextObject> <Descriptors>0x4</Descriptors> <Obj_TypeOffset>0xC</Obj_TypeOffset> <Obj_X>0x838</Obj_X> <Obj_TargetGUID>0x16</Obj_TargetGUID> <ClickTerrain>0</ClickTerrain> </Offsets> Is the working offset. Edit: Made the code smaller and removed "-" so that people don't errors

<?xml version="1.0" encoding="UTF-8"?> <Offsets> <CurrentWoWVersion>18414</CurrentWoWVersion> <WoWVersionOffset>0xC7B6EF</WoWVersionOffset> <PlayerName>0xEC4668</PlayerName> <PlayerClass>0xEC47F1</PlayerClass> <GetCurrentKeyBoardFocus>0xBB292C</GetCurrentKeyBoardFocus> <GameState>0xD65B16</GameState> <Lua_DoStringAddress>0x4FD12</Lua_DoStringAddress> <Lua_GetLocalizedTextAddress>0x414267</Lua_GetLocalizedTextAddress> <CVarBaseMgr>0xBA5DE8</CVarBaseMgr> <CVarArraySize>0x400</CVarArraySize> <ObjMgr>0xEC4628</ObjMgr> <CurMgr>0x462C</CurMgr> <ClntObjMgrGetActivePlayerObjAddress>0x4FC6</ClntObjMgrGetActivePlayerObjAddress> <LocalGUID>0xE8</LocalGUID> <FirstObject>0xCC</FirstObject> <NextObject>0x34</NextObject> <Descriptors>0x4</Descriptors> <Obj_TypeOffset>0xC</Obj_TypeOffset> <Obj_X>0x838</Obj_X> <Obj_TargetGUID>0x16</Obj_TargetGUID> <ClickTerrain>0</ClickTerrain> </Offsets> I got pretty close, no idea what I am missing.

I tried a lot of things: I tried lateral comparison to retail (how I obtained it for retail), I tried searching all strings related to the offset (the offset usually has a string). I did notice the you can't just simply follow that guide, even for retail, because retail offsets were not obtained that way, and there are probably more things to find not mentioned in that guide. I need someone with experience in reverse engineering and testing.

How do I test each offset one at a time? Is there a program to easily test these offsets?