Jump to content

Braxy

Member
  • Content Count

    128
  • Joined

  • Last visited

  • Days Won

    7

Braxy last won the day on July 12 2019

Braxy had the most liked content!

Community Reputation

71 Excellent

3 Followers

About Braxy

  • Rank
    Friendly
  • Birthday 11/24/1999

Metin2

  • Chunjo

Informations

  • Gender
    Male
  • Location
    Romania

Social Networks

  • Skype
    facetoface1212
  • Discord
    Braxy#9583

Recent Profile Visitors

1492 profile views
  1. Hi, https://pastebin.com/HKVVuQy1 Should work like this. The problem was that it was always calling the info event, leave the button behind. Anyway if it's working, it won't make up for the fact that the code is poorly written. Also it may affect people in long term use.
  2. Hi, your problem might be caused by multiple reasons: 1. Monsters are set to drop a specific item in mob_proto, that specific item can be find on the drop_item row from each monster. (0 is default) Now, it would make no sense for you to look over each monster to remove that item, anyway this is not the case. The item drops with one condition, if etc_drop_item.txt is filled has that vnum, that's where the item get's it's chance to drop and it's the same for every monster that has that vnum. So one possible way to fix it is to remove what items you don't want from there. 2.
  3. Hi, i would suggest to look over: (Assuming the lag is a client issue) 1. If there is any fault in code that might lag players, like loops that loop too many elements (maybe per killing monsters) 2. If the client has the proper visual models, maybe your models have wrong data inside them. (You can check both monsters and map elements) (Assuming the lag is a server issue) If the server is lagging and it specially lagging when entering that level, then it's for sure a code fault issue and you have to check it out.
  4. Hi, i took a look into your quest and there are multiple faults in your code. One of them and the one that is the worse is the fact that you are using timers. The problem is not that you are using timers, the problem is that you are using them wrong. Beside that you are also adding re-enter option to the dungeon, fact that has no sense. So let me be a bit more specific: If the leader of the group (or other party players) will leave/logout and they will have timers active, those timers are erased by the server, that means whenever they will re-join the dungeon those timers will be erased since
  5. You dont have to change it to PID. You can simply update the messenger_list by changing the last name with the new one both on account and companion rows.
  6. There was no intention to attack you in any way what so ever so don't take it that personally. I just resumed to the fact that my quest was written like (3 years ago >> released 2y ago) and yea, it was poorly written, can't lie about that. Even tho, i don't have the time nor the mood to update all my releases. Anyway, back to the Duplicate bug, i was refering to the update packet part of the func, i said that since the update is made through SQL and you actually have to wait until the DB is updating your player account data there won't be any issue what so ever. I d
  7. Eh old stuff, can be improved so much but i don't quite have the time to improve all my releases for now. @Syreldar Not sure what you want to say but i guess we both know LUA's syntax is not that complex lol Whatever, Syreldar version is alright but i would avoid that retarded loop anyway so: https://pastebin.com/ngi4ZXvB (Regarding Duplicate bug, that bug only exists if you use pc.change_name function, since the function that changes name is based on SQL there won't be any Duplicate Bugs)
  8. So, what are you saying does not even make logic. The quest does exactly what it's supposed to. What you need is the "enter" event, with that, the quest know it must execute the code below. So you dont have to change a thing in the first state, the second state with the informations must be changed, from when letter begin into when login or enter begin, when you set_state(information) in the first state it means that you enter a new state and that triggers the event and execute your things without need of teleport. (This is from what im remembering, i might be wrong tho, i did
  9. This would make a real good weapon set and armor set if you ask me
  10. Well then move "main_quest's" over to /quest folder.
  11. The error indicates that the "quest compiler" does not exists, not that you cannot compile your main_quest. The "quest compiler" is usualy find in ../quest path, so if you want to access it just go through the right path.
  12. I'm not talking about this in special, i'm generalizing it.
  13. Properly clearing memory after using it it's a must.
  14. Hi, this is a common issue. Maybe is because at login is set to a null pointer but im not sure (didn't check actually) Anyway, if you are trying to write "rejoin func" into dungeons keep in mind that each time someone leaves the dungeon and it has timers on him, timers will be removed. Therefore i suggest you to take a better look on this function because it can be messy af
  15. Hi, since i have never released anything here, i tought it would be a great start releasing this quest. As you well know i have a LUA Service topic here and even tho this quest is not much about LUA because of course its based on Metin2 functions it's quite alright for you to take a first impresion. Link: https://github.com/braxy122/editableMission Best regards, Braxy.
×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.