Bug #199: Admin value and character name requirements on warp
| ID | #199 |
|---|---|
| Submitter | Ducci |
| Product | EOSERV |
| Severity | Feature Request |
| Status | CLOSED, WONTFIX |
| Submitted | 10th Dec 2012 |
| Updated | 3rd May 2013 |
Associating levels above the highest achievable level with admin values and character names to limit access to buildings and maps.
Say, the highest achievable level is 250.
If only Light Guides should be able to enter a specific building, associate level 251 with the admin value for Light Guides (this would be 1 in the database, but could be 0 in the config file since a value for players is not needed) and set the level requirement flag on the warp tile to 251.
Example configuration:
lvlreq.251 = 0 (0 = LG, 1 = G, 2 = GM, 3 = HGM)
lvlreq.252 = ducci,sausage,rena
Comments
12 years, 3 weeks ago
That seems like a rather shoddy way to handle allowing staff into maps. Its also not a feature on the main endless online, so I doubt sausage will add it. I'm not trying to sound harsh though.
It is not handled in Endless Online at all. Instead, admins were level 100 and warp tiles of restricted areas had requirements of level 100. When you reached level 100, you could enter these areas. I don't see why this would be a shoddy fix. Levels would not go any higher than 252... So why not use these values? I mean, if you want to implement the functionality of limiting access, you would need to alter tile specs in the EMF format anyway. Instead of using an unknown value, we could simply use the unused ones we know. And it is not even visible on the outside; instead of showing a message (hint) stating that your level is not high enough to enter, you could simply ignore the character and not show anything, or show a message that says you cannot enter because you are not an admin. Believe me, this is more of a Vult-R-like solution than you think it is...
12 years, 3 weeks ago
Its not a sausage-like solution though. This would be fine if it were coded in a custom revision but eoserv is meant to be a base containing all of eo main's features. Its open source so people can add in all the other stuff they want. Also, I'm not sure the level requirement value is meant to go above that of an unsigned char so technically it wouldn't be able to go above the max possible level.
EOSERV does have a lot of features that EO itself doesn't have, though. Small things that Vult-R didn't think of (or didn't add, because he wasn't that far yet).
I think, although I'm not entirely sure, that it wasn't just an unsigned char that was used to set the warp tile level requirement flag. On several maps, Vult-R (or another mapper) used very high numbers (again, I'm not sure if they were higher than 252) to prevent people from 'walking off' tiles. I have no clue why they didn't just use some wall tiles for this.
Anyway, you could still make use of 251 and 252 to check whether someone is an admin or not if you set the maximum achievable level to 250. Well, if this is handled server-side anyway. Maybe it's the client that checks if you're allowed to warp. I'm not sure anymore...
Or make a never ending quest that warps you when you walk on a certain tile... But that IS kinda shoddy.
12 years, 3 weeks ago
The client blocks you from walking on a tile if you're below the level it requires, and the server checks it too so you cant hack your way in.
12 years, 3 weeks ago
I would use one of the misc. map types that the map editor isn't using. Actually, the two type values (one handles PK flag, the other is drains/quakes) can go up to at least 255 so that allows a total of 510 map type possibilities. You could simply set map types for minimal admin rank entry. Ducci is right about quests though, you should be able to check admin ranks and simply warp that way too.
That's even better, setting map types for minimal admin rank entry. Is there an example code snippet that reads unknown/unused values from the map file?
11 years, 35 weeks ago
Too weird. Better off using map-bound quests to implement conditional warps freely.
Updated Status to CLOSED, WONTFIX
Add Comment
Please don't post unless you have something relevant to the bug to say.
Do not comment to say "thanks" or "fix this please".
Please log in to add comments. EOSERV Bug Tracker > Bug #199: Admin value and character name requirements on warp