Angelix

Please don't tag specific people in your threads, if someone sees your threads and wants to help, they will. Tagging someone doesn't ensure they will help you. Also again, take a look at my guide, you have to make a new trigger per item.

First of this is not correct, this type of condition is only for monster killing quests. MisResultCondition(HasFlag, 2005, 29) Please look again ay my guide, specifically "Part I" of it. Instead of that, just straight out put this: MisResultCondition(HasItem, <ITEMINFO_ID>, <AMOUNT_NEEDED>) In your case it would be this: MisResultCondition(HasItem, 2604, 20) Note: I don't know why you were placing "2005" at all, since that's not the item you were asking for. Second of all, you're just handing out gold, why does a player need 20 free inventory slots? Just remove this. MisResultBagNeed(20)

Basically your own mod, but on a bigger scale. Some games lay out a "Battle Pass" where you can buy it and then gain experience towards a temporary level that resets on a seasonal of monthly basis. Some games either do 50 rewards or 100, whereas when you obtain a new level, you can claim said reward from that specific level. I kind of like "Destiny 2"'s approach as for a MMO game, where the battle pass has 100 rewards, resets each season and reward within the pass contain glimmer (gold equivalent), experience boosters (solo and team), apparels, minor equipment and other game specific cosmetic.

There's an issue on quests if you use IDs over 6K if I remember correctly, so your ID of "64411" might probably cause an issue as well.

So @V3ct0r, why are threads like this allowed?

What do you need help with?

Adding onto what @V3ct0r said using hooks, this is a somewhat better version of his which allows more simplistic usage without adding more conditions within the function, just new variables. BossKillNotice = {} BossKillNotice[789] = '[&MONSTER&] was killed by [&PLAYER&]!' OriginalGetExp_PKM = GetExp_PKM GetExp_PKM = function(Monster, Player) OriginalGetExp_PKM(Monster, Player) -- Call original function GetExp_PKM() local MonsterID = GetChaID(Monster) -- Get ID of the killed monster. local MonsterName = GetChaDefaultName(Monster) -- Get monster name. local PlayerName = GetChaDefaultName(Player) -- Get player name. if not BossKillNotice[MonsterID] then return -- No point in continuing function if a notice is not declared for this ID. end local Message = BossKillNotice[MonsterID] Message = Message:gsub('&MONSTER&', MonsterName) -- Replace placeholder with actual monster name. Message = Message:gsub('&PLAYER&', PlayerName) -- Replace placeholder with actual player name. Notice(Message) end Essentially just add a new variable under "BossKillNotice" as the example shown. The "&MONSTER&" and "&PLAYER&" are placeholders, meaning you can move them aroiund for more creative notices at your liking. For example, this shows the monster was killed by the player: BossKillNotice[789] = '[&MONSTER&] was killed by [&PLAYER&]!' You can also do the player killed the monster: BossKillNotice[789] = '[&PLAYER&] killed [&MONSTER&]!' And the "[789]" correspond to the monster ID, so to add a new notice, just change the ID. Like this: BossKillNotice[989] = '[&MONSTER&] was killed by [&PLAYER&]!' This should be compatible with all lua versions I think.

Yes, they are saved on variables which removed upon server closing. You must find a way to keep those variables permanently or store all of that information within SQL (or alternatively in text files, but not recommended I guess).

If your GameServer has the function, then within your files look for a file called HandleChat or something similar.

That's on your gameplay, not the actual stuff going within server/client. Even if you change the actual item's price to zero, if it has any value (usage), they'll sell it for a set price onto other players if your server has an economy. If the characters are being deleted at 41, then they most likely do that to farm reputation, the gold from newbie chest, amplifiers and sell equipment. You can probably make reputation useless or only be given above level 50 (for example), remove gold bonus on newbie chests and make those specific amplifier non-tradeable.

Is that "skill point guide" correct? If so, I think it's badly planned. A soft cap limit of 69 points by leveling up. Really? Why 69? If a player only wanted to specialize in low amount of skills, they can't even maximize 7 skills, they'd be left at 6 full skills and 1 skill at level 9. "Skill Crystal". So you're taking regular progression where a player can be on even terms with others and putting it behind a RNG wall. Your explanation: "This limitation is to allow players to put more thoughts into which skills should they increase their levels and which skills should they get. Thus, the skill build for each players will vary depending on their respective builds." The skill crystal defeats that entire purpose. Putting the crystal a chest with low rate and then putting that chest into maze bosses gives more power to dominating guilds/players and even they will have low chance of getting it. Putting the crystal behind a quest that tasks players on boss kills will also just benefit dominating guilds/players. Just a few of my thoughts.

Yes, you just have to identify how it was disabled. If it was just removed from NPC, just add the lines again. If it was removed from files, you have to add the scripts again.

Yes, you can increase limit of ItemInfo by using hex, there should be like 2 threads about it in the forum. Yes, but that's mostly doable by source. For hex, it would be much harder to find all the instances for it and I'm guessing the person asking isn't really knowledgeable if he's asking for this.

Whatever you placed above ID 240 will not work, even if you increased the limit. So remove it or make place for it on another ID below 240.

Does anything show up when you're opening GameServer?

You changed something and messed up, whatever you changed is blocking a chunk of files from being loaded in GameServer. You should check your console if any errors pop up when initiating the server or check "lua_err.log" and track your error from there.

Yes, unless you get ahold of different exes with those functions working. You can probably find around here some GameServer with "GMNotice" working or ask someone to add it to yours.

No. What Wolfen didn't explain is that GMNotice and ScrollNotice are not lua functions by default. The function "GMNotice" is within all servers by default since it's bound to the client command "Alt+P" (if I remember correctly), but it's not bound to any lua function, so you cannot call it from lua scripts. The function "ScrollNotice" is only present on v2.4 servers and those servers that use custom source-built exes. It has no client command, but it does have a lua command which is used like "ScrollNotice(Text, Number)". The function "Notice" is coded into all servers by default within client command and also lua function, so it can be used in lua scripts with "Notice(Text)". None of these functions (if implemented) need a requirement, prior or post, to the call of the function.

You have to add a check on the gem combine condition function so you avoid players having higher level than intended gems and probably another condition on the forge condition function to check they can't forge a higher level than intended gem in case they somehow got it elsewhere from combining.

From what I remember correctly, it's defined via AreaSet.txt with the specific location, fourth column.

Get your MusicInfo.bin and decompile it by using Heandel's Gemini Decompiler or deguix's decompiler. Both are available within this forum and should be easy to use.

Are you refreshing the character within the fusion function? If I remember, by default, files have "RefreshCha" at the end of the function to avoid that issue.

Yes, I know that, that's why I asked if the person was able to get them to work.

You're wrong. It's not GameServer if you're just swapping out lua files to make it work. If you make a change and it doesn't work, it means you're doing something wrong. Instead of just changing files, try going back, track every change you made and figure out what's wrong. Why not try something simple? I think most of the files by default have the level 85 ring plus unseal 75 armor glow/effect. So get that, change a few variables to see if you can make it work and then go from there. Good luck.

Yes, you changed your SkillEff limit, but do those limits actually work? Like try placing a new effect in those added lines, does the effect show up?