Search results

I don't think a 6 year old server with probably a bunch of custom content is going to help you.... Every server's storage id pool is going to be different (unless its a default). If done well, the storages file in data/lib/miscellaneous is the bulk, and then make sure you factor in any source...

This will still execute the event callback for everyone. Register the event "blockRentalItemMove" (onLogin), and then inside the onMoveItem eventcallback, loop through the player's events and check for that event. If it doesn't exist, just return NOERROR so it doesn't execute the rest of the...

Just a few things from a brief look at the new code: 1) Move containsCustomOwner outside of the callback, there is no need to re-define this function everytime the event callback is executed. 2) This recursion now happens everytime someone moves any item in the game. As I suggested earlier, it's...

I agree, however, if this system were to go down the route of recursive search, it could be more efficient by limiting the moveItem event callback to only those who have rented (by checking for an event registered to the player) Still not an efficient solution i know, but at least it will...

Perhaps a database table for rental items is best (if Mateus Robeerto is willing to implement). This way all rentals can also be logged and a history maintained. You could then handle things on startup case of a crash or other unforeseen issues. Especially for cases where rental durations are...

I would also do a position check for renting, doesnt make sense to conduct a rental from half way across the map. I would also prevent a rental from happening if either player has pz lock.

Yeah... that's how the internet works. Old threads tend to have broken links.

Logic looks ok from a brief glance. It might not like using Position as a key. Try this(untested): local scheduledEvents = {} local function removeVortex(pos, key) local vortex = Tile(pos):getItemById(26394) or Tile(pos):getItemById(26395) or Tile(pos):getItemById(26396) if vortex then...

You can just do the same type of thing inside the ec.onDropLoot(monster, corpse) callback on line 96 of the autoloot script. Something like (untested): function ec.onDropLoot(monster, corpse) if not corpse:getType():isContainer() then return end local corpseOwner =...

You need to check src/luascript.cpp and search for the "createMonster" method in the game class. Make sure it has extended and force as parameter options. Like it does here: (https://github.com/otland/forgottenserver/blob/master/src/luascript.cpp#L5004) If the options do exist, try and pass...

Double check the new item has the "pickupable" flag in item editor.

What exactly isn't working? Your threads are very confusing. Once again, best thing to do is to log the response. After: success: function(response) { Add: console.log(response)

Just follow the code from where it's being displayed in the HTML to which table it's being picked up from. I always thought it was znote_accounts that they were stored.

It's because you put the check_username and check_email scripts in layout/subs/, therefore to include the init.php, you had to traverse back to the root directory first (adding ../../ before engine/init.php). If you kept them in the root directory it would have worked. Not sure why you had to...

Looks like a PHP error, which it's trying to deserialize JSON, therefore throwing an error. You need to log the response before its deserialized. After this line: .then(response => { add: console.log('Response:', response);

When the error happens, right click anywhere on the page, click Inspect, then click console on the top (There are various ways to get to the same place). Post anything that is logged in the console here.

fetch('check_username.php?username=' + encodeURIComponent(username)) ... fetch('check_email.php?email=' + encodeURIComponent(email)) Your php files do not match what are being called... Rename them to check_username.php and check_email.php or change the URL paths in the code...

(Note: The solution below will work best with an enclosed arena, with only one way in or out such as a teleport, otherwise it can get messy...) You can assign events to a player when they enter the arena, and unregister them when they leave (death or logout will ofc remove them by default). The...

By the looks of the screenshots, I assume he wants more emphasis on sticky threads for the dark theme. His "after" screenshot shows sticky threads with a much darker background.

Both options are variable. Some developers request payment per job, some request per hour.... It's impossible to say. Showing a video saying "I want this" isn't good enough. Does the map exist? Or will you want someone to create the map? What client features/modules do you want? What server...